Objective 2.1
Cybersecurity Defense ArchitectExplain how to develop and implement integration strategies for data-driven security operations
Objective 2.1 sits in Security Data Management, which carries 20% of the Cybersecurity Defense Architect exam. The questions below are original, written from the official objective title above, and each explanation cites the Splunk page it rests on.
Objective title verbatim from the official objectives. Splunk exam page ↗
A worked example
Shown solved, with the whole explanation open: this is what every question here carries.
An engineer asks what log management covers as a process. Which set does NIST document?
Correct.
Checked against nvlpubs.nist.gov, August 2026Concept
Naming the whole chain is what stops a design that collects well and disposes badly. Every stage is somewhere a requirement can be missed.
Why B
NIST documents log management as the process for generating, transmitting, storing, accessing and disposing of log data.
Source
NIST SP 800-92r1 (initial public draft): Cybersecurity Log Management Planning Guide, checked August 2026Log management is the process for generating, transmitting, storing, accessing, and disposing of log data.
Now you: objective 2.1 questions
No account needed. The explanation opens when you answer.
Sample question 1 of 2
An engineer asks what NIST says log management facilitates beyond security. Which purpose is documented?
Sample question 2 of 2
An engineer asks how NIST defines a log for planning purposes. Which definition is documented?
Full Cybersecurity Defense Architect question bank coming
We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.
Read the sources
These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.
More objectives in Security Data Management
- 2.2 Identify data sources critical to cybersecurity operations, such as event sources, identity directories, asset management systems, and vulnerability - assessments. This can include non-security data sources, eg. observability tools
- 2.3 Identify high value / high signal / high noise data sources (e.g. Windows process vs EDR process flow, or network/VPC flow vs packet capture) and how they support security operations use cases
- 2.4 Identify strategies to monitor an environment that requires nonstandard or out-of-band instrumentation and sensors, e.g. legacy data sources, OT/IC infrastructure environments
- 2.5 Develop a data lifecycle management strategy, including retention, storage tiering, summarization, data residency, and access control
- 2.6 Describe the value of data normalization in order to support integration into cybersecurity defense programs, such as security monitoring and threat hunting, e.g. with CIM, CEF
- 2.7 Implement security analytics strategies beyond traditional SIEM such as advanced techniques like data science, machine learning, behavioral analysis, and AI
- 2.8 Explain how cybersecurity defense data architectures scale using technologies and capabilities such as data mesh, data lakes, message bus, message routing, and federated search