SPLK-5002 Splunk Certified Cybersecurity Defense Engineer Questions and Answers

A playbook is Splunk SOAR ' s automation construct for processing container data through a defined sequence of actions. Playbooks can inspect artifacts, evaluate conditions, invoke applications, enrich indicators, perform containment actions, update records, and make workflow decisions.

A SOAR container stores the event or case-related data being processed. It can contain artifacts such as IP addresses, domains, file hashes, usernames, URLs, and other observables. The playbook operates on that data by passing values into configured assets and applications. For example, a playbook might retrieve a URL from a container, submit it to a sandbox, check reputation services, evaluate the resulting scores, and then determine whether escalation or blocking is required.

A workbook provides structured analyst tasks and procedural guidance rather than executing the automated sequence itself. Cases organize investigative work, while containers represent the underlying records and artifacts. Neither performs the automated orchestration described in the question.

Playbooks therefore form the execution layer of Splunk SOAR automation, translating SOP logic into repeatable machine-driven actions while allowing human decision points where required.

Study Guide topics: Splunk SOAR playbooks, containers, artifacts, orchestration, automated actions, response workflows.

Correlation search throttling is specifically intended to suppress repeated results that represent the same or substantially equivalent detection condition within a defined period. It is therefore the appropriate setting when a correlation search generates multiple findings for what analysts consider one potential incident.

Throttling is generally based on one or more result fields and a suppression period. For example, if repeated executions identify the same user and dest, the search can suppress additional findings matching that combination during the configured interval. This reduces redundant analyst workload while allowing materially different entities or events to generate new findings.

The engineering requirement is to select throttling fields carefully. Overly broad suppression can conceal genuinely distinct security events, while overly narrow suppression may fail to reduce duplicate findings. The suppression period likewise should reflect the behavior being detected and the expected recurrence pattern.

Correlation search priority affects prioritization rather than duplication. An adaptive risk modifier adds or modifies risk-related information but does not directly solve repeated notable generation. Adaptive response actions control downstream outcomes rather than the duplicate-suppression behavior requested.

Study Guide topics: correlation-search throttling, duplicate findings, notable suppression, detection tuning, analyst workload, false-positive reduction.

A common ESCU methodology calculates risk as:

Risk Score = Impact × Confidence / 100

Impact represents the potential significance or consequence of the detected behavior, while confidence represents how strongly the analytic supports the conclusion that the activity is security-relevant. Dividing by 100 normalizes the confidence percentage when combining the two values.

For example, if a detection has an impact value of 80 and confidence of 75%, the resulting score is:

80 × 75 / 100 = 60

This methodology prevents a high-impact but low-confidence analytic from automatically producing the same risk contribution as a high-impact, high-confidence detection. It therefore supports Risk-Based Alerting by allowing individual detections to contribute proportional evidence to a user, host, or other risk object.

Risk-object priority or severity can still influence downstream prioritization through contextual enrichment and Risk Factors, but those concepts are distinct from this ESCU risk-score calculation. The supplied Cybersecurity Defense Engineer material separately reinforces the role of risk scores, Risk Factors, and contextual prioritization in Enterprise Security.

Study Guide topics: ESCU, Risk Analysis adaptive response action, risk score, impact, confidence, Risk-Based Alerting, risk objects.

The primary purpose of indexing in Splunk is to store incoming event data in a searchable structure and enable efficient retrieval during searches . Splunk processes incoming machine data, organizes it into indexes, preserves the event data, and creates index structures that allow searches to locate relevant events efficiently without treating the entire dataset as an unstructured file collection.

Indexing should be distinguished from normalization . CIM normalization generally occurs through knowledge objects, field extractions, aliases, event types, tags, and data-model mappings rather than being the fundamental purpose of indexing itself. Likewise, access controls can secure indexed data, but security is not the primary reason the indexing process exists. Dashboards consume search results and provide visualization; they are downstream of indexing and searching.

This distinction is important for detection engineers because search performance depends substantially on how data is indexed and how searches use indexed metadata. The supplied study material reinforces this through questions on tstats, metadata, visible indexes, sourcetypes, and accelerated data models, all of which rely on efficient indexed data structures.

Study Guide topics: Splunk indexing, searchable event storage, indexed metadata, tstats, sourcetypes, search performance, data engineering.

Triage generally provides the lowest-friction opportunity for replacing manual SOC work with automation because much of triage consists of deterministic, repetitive information-gathering and enrichment tasks.

A SOAR playbook can automatically retrieve reputation information, collect endpoint details, query identity context, check threat intelligence, detonate suspicious files or URLs, deduplicate findings, and assemble evidence before an analyst reviews the incident. These activities are generally reversible and low impact compared with active response operations. The supplied material demonstrates this principle through automation scenarios where SOAR handles repetitive Attack Analyzer submission and data-collection steps before presenting the information to an analyst.

Containment introduces greater friction because actions such as disabling an account or isolating a production endpoint can disrupt business operations. Remediation may involve deleting files, changing configurations, resetting credentials, or restoring systems and therefore generally requires stronger controls. Rendering a verdict frequently requires contextual human judgment, particularly where evidence is ambiguous.

Automating triage first therefore provides high efficiency gains while maintaining relatively low operational risk.

Study Guide topics: SOAR automation, triage, enrichment, incident-response lifecycle, automation guardrails, containment, remediation.

The correct REST endpoint is:

| rest /servicesNS/admin/-/alerts/alert_actions

| table title, eai:acl.app, label, payload_format, command

The path component alerts/alert_actions is the key indicator. It queries Splunk ' s alert-action resources, allowing the search to enumerate configured alert actions and expose metadata describing each action.

The namespace syntax is also significant. servicesNS/admin/-/ requests resources in the admin user namespace across applications, while eai:acl.app identifies the app context associated with the returned object. The subsequent table command limits the output to useful fields including the alert-action title, application, label, payload format, and underlying command.

Options C and D use the incorrect path actions/alert_actions. Option B uses a literal user namespace rather than the administrative namespace represented by the expected command.

The uploaded study guide covers REST usage, alert/adaptive-response concepts, and API interaction, but it does not expose this exact REST endpoint verbatim in its parsed text. The answer above follows the Splunk REST resource structure tested by the question.

Study Guide topics: Splunk REST API, | rest, alert actions, namespaces, eai:acl.app, adaptive response, administrative inspection.

The affected metrics are Mean Time to Respond and Mean Time to Resolve because both can depend on the expected lifecycle of a notable beginning in the default New state and progressing through subsequent analyst-handling states.

If Testing is accidentally configured as the default, newly generated notables no longer begin with the status value expected by searches or reports that identify sequences such as:

New → In Progress

or

New → ... → Resolved

As a result, the timestamp used to establish the beginning of the response or resolution interval may be missing from the expected status-change sequence, producing inaccurate, incomplete, or excluded metric calculations.

Dwell Time is different. It measures how long malicious activity remains present or undetected in the environment and is not fundamentally calculated from Enterprise Security notable-status transitions. That eliminates options C and D. Option B is also incorrect because changing a status value relied upon by existing SOC metric searches can directly alter their results.

The supplied guide explicitly emphasizes notable status and ownership as operational SOC measurement fields , supporting the importance of preserving lifecycle-state consistency.

Study Guide topics: notable-event lifecycle, status transitions, Mean Time to Respond, Mean Time to Resolve, SOC metrics, reporting consistency.

An HTTP 403 Forbidden response indicates that the server understood the request but refuses to authorize the requested operation. In a SOAR asset integration, this strongly points to an authorization or permissions problem involving the credentials configured for that asset. Therefore, asset credentials lacking adequate permissions is the appropriate answer.

This should be distinguished from authentication failures. Incorrect credentials commonly result in an HTTP 401 Unauthorized response, while a nonexistent REST resource more commonly produces 404 Not Found . A requirement for a different authentication mechanism, such as an API token, can ultimately cause authentication problems, but the question specifically associates the observed response with permissions.

For SOAR integrations, the service account should have the minimum privileges required for the actions performed by playbooks. For example, a read-only account may successfully retrieve endpoint information but receive 403 when a playbook attempts an administrative operation such as quarantining a host or blocking an indicator.

Study Guide topics: SOAR assets, REST APIs, HTTP status codes, authentication versus authorization, integration troubleshooting, least privilege.

Workbooks provide the appropriate mechanism for standardizing repeatable analyst procedures. In Splunk SOAR, a workbook can organize response activities into defined phases, tasks, and analyst actions, effectively representing an operational Standard Operating Procedure (SOP) for handling a particular type of security event.

This is especially valuable when a SOC wants analysts to follow consistent processes for scenarios such as phishing, malware, credential compromise, ransomware, or suspicious endpoint activity. Instead of relying on each analyst ' s individual memory, a workbook can explicitly identify required investigation and response tasks. This improves consistency, auditability, onboarding, and measurement of response-process execution.

Events, cases, and incidents are operational objects used to represent or manage security activity; they do not themselves provide the structured procedural checklist capability requested by the question. A workbook, by contrast, describes what analysts should do as the incident progresses.

Standardization also supports automation engineering. Tasks that are deterministic can eventually be delegated to playbooks, while judgment-intensive tasks remain assigned to human analysts. The workbook therefore bridges documented process and operational execution.

Study Guide topics: Splunk SOAR Workbooks, SOPs, analyst workflow standardization, response processes, phases and tasks, SOC operational maturity.

The correct field is risk_message . In Splunk Enterprise Security Risk-Based Alerting, risk_message provides a human-readable description of the suspicious activity represented by a risk event. It gives analysts contextual information explaining what happened and why the risk contribution was generated.

This should be distinguished from risk_object , which identifies the entity receiving risk—for example, a username, host, system, or other security-relevant object. A typical risk event therefore combines fields conceptually such as:

risk_object= " jsmith "

risk_object_type= " user "

risk_score=40

risk_message= " User executed suspicious PowerShell command "

The risk object answers who or what is accumulating risk , while risk_message explains the activity responsible for that risk . risk_description and risk_reason are distractors and are not the standard field requested.

The uploaded guide strongly covers Risk Framework concepts, including risk objects, risk scores, Risk Factors, and Risk Analysis, although this exact field-name question is not presented verbatim in the supplied 60-question set.

Study Guide topics: Risk Framework, risk index, risk_message, risk objects, Risk-Based Alerting, contextual findings.

The correct REST endpoint is:

| rest /services/alerts/alert_actions

The alert_actions endpoint exposes the alert-action resources available to Splunk, allowing an engineer to enumerate configured actions and inspect associated metadata. In practical administrative searches, the returned results can be further reduced with commands such as:

| rest /services/alerts/alert_actions

| table title, eai:acl.app, label, payload_format, command

Option A references adaptive_response_action, which is not the general endpoint used to enumerate the alert-action collection. Option B points toward correlation-search resources rather than alert actions. Option C is incorrect both because the resource path is malformed (alert actions instead of alert_actions) and because /_acl concerns access-control metadata for a resource rather than listing the alert actions themselves.

The supplied study guide covers related REST/API, adaptive-response, and automation concepts, but it does not show this exact endpoint verbatim.

Study Guide topics: Splunk REST API, | rest, alert actions, Adaptive Response Actions, REST resource paths, administrative inspection.

The correct field is user , because Splunk ' s Common Information Model provides normalized fields that allow heterogeneous security data sources to be queried consistently. Authentication, endpoint, identity, operating-system, and application logs frequently use different native names for the same concept—for example, username, account_name, UserName, or src_user. CIM mappings normalize the appropriate value into the canonical user field.

This becomes particularly important when a detection performs aggregation such as:

| stats count by user

If contributing sources fail to populate user consistently, activity belonging to the same account can be fragmented, omitted, or incorrectly represented in the detection results. action identifies the result or nature of activity rather than the account responsible for it. user_id may occur in individual schemas but is not the general CIM field being tested here. identity represents a different conceptual object and is not the standard aggregation field for this use case.

The question appears on page 1 of the supplied certification material.

Study Guide topics: Common Information Model, CIM normalization, normalized fields, data-model consistency, user attribution, detection data preparation.

A Sysmon Process Create event is identified by Event ID 1 , making EventCode=1 the correct selection. This event type is among the most important endpoint telemetry sources for detection engineering because it records process execution and provides fields useful for reconstructing process relationships and identifying suspicious command execution.

Typical Process Create telemetry can contain attributes such as the process image, command line, process identifier, parent process, parent command line, user context, hashes, integrity level, and process GUID. These fields support detections for suspicious scripting interpreters, unusual parent-child relationships, LOLBins, encoded commands, malware execution, and other endpoint behaviors.

The remaining event IDs represent different Sysmon activities. Event ID 2 concerns changes to file creation time, while Event ID 3 represents network connections when that telemetry is enabled. Event ID 4 records changes in the Sysmon service state. None of those describes the process-creation record shown in the question.

Correct event-type interpretation is fundamental to building accurate SPL because filtering on the wrong EventCode can completely change the semantic meaning of a detection.

Study Guide topics: Sysmon telemetry, Event ID 1, process creation, Windows endpoint data, process analytics, event normalization.

Splunk uses Analytic Stories to organize related detections around a common threat scenario, adversary behavior, or security use case. Ransomware is an ideal example because no single detection fully characterizes the attack. Instead, defenders may observe multiple behaviors representing different stages or consequences of the intrusion.

One analytic could detect registry modifications associated with persistence or configuration changes. Another could identify mass creation of ransom-note files. A separate detection could monitor wallpaper modification or account manipulation. An Analytic Story groups these related analytics into a coherent defensive narrative so engineers and analysts can understand how individual detections collectively provide coverage of the broader threat.

A data model normalizes telemetry and enables consistent searching but does not conceptually group detections by attack scenario. The Threat Intelligence Framework handles indicators and intelligence enrichment, while the Assets & Identities Framework adds contextual information about entities. Neither serves as the security-content grouping mechanism described.

Analytic Stories also help communicate detection coverage, supporting searches, data requirements, and related adversary techniques in a structured way.

Study Guide topics: Analytic Stories, ransomware detection, security-content organization, detection coverage, behavioral analytics, MITRE ATT & CK alignment.

Zero Trust is the methodology among these choices that directly supports reducing and preventing malicious lateral movement. Zero Trust architectures reject implicit trust based solely on network location and instead continuously evaluate identities, devices, applications, permissions, and access conditions.

Lateral movement occurs when an adversary who has gained an initial foothold attempts to access additional systems, credentials, services, or network segments. Zero Trust limits this ability through principles such as least privilege, strong identity verification, access segmentation, constrained authorization, device posture evaluation, and continuous monitoring. An attacker compromising one endpoint should therefore not automatically gain trusted access to adjacent resources.

The Lockheed Martin Cyber Kill Chain models stages of adversary activity and can help defenders understand attack progression, but it is not itself an access-control methodology designed to prevent lateral movement. MITRE ATT & CK catalogs adversary tactics and techniques, including lateral-movement techniques, but primarily provides a knowledge framework rather than the preventive architecture requested. A breakglass mechanism provides emergency privileged access and must itself be tightly governed.

Zero Trust therefore most directly addresses the architectural conditions that enable lateral movement.

Study Guide topics: Zero Trust; lateral movement; least privilege; segmentation; identity-centric security; access control; adversary containment.

The required combination must satisfy two independent requirements : restrict the dataset to failed Azure Active Directory authentication activity and represent the origin of those events geographically. Option D provides that combination by selecting the failure-oriented Azure AD sign-in data and using geographic-coordinate information with a Cluster Map .

A geographic cluster visualization is appropriate when individual events contain point locations such as latitude and longitude. Multiple sign-in failures originating from the same geographic area can then be grouped visually, making concentrations outside the expected operating region—here, North America—immediately apparent. This is particularly useful for authentication monitoring because a raw table of IP addresses does not provide the same rapid geographic interpretation.

The search must also distinguish failures from successful authentication. Merely plotting all sign-ins would allow large quantities of legitimate activity to obscure the specific anomalous behavior being investigated. Conversely, choosing an inappropriate geographic visualization for point-coordinate data would not provide the intended presentation.

Study Guide topics: Azure AD authentication data, failed-login filtering, geospatial enrichment, geographic dashboards, Cluster Map visualization, security analytics.

Splunk dashboards use tokens to capture and pass contextual values between dashboard elements, user interactions, and drilldown destinations. Therefore, tokens are the mechanism an engineer can use when a user selects a visualization element and the resulting value must be inserted into another search.

A token can represent contextual information derived from an interaction—for example, a selected host, username, source IP, destination, process, or time range. A drilldown can then use that value to construct a more focused search. Conceptually, a dashboard could capture a selected src value and pass it to a destination search so the analyst moves directly from an aggregate visualization to events associated with that source.

This design improves investigation efficiency because the analyst does not need to manually copy values from one interface into another search. It also preserves analytical context as the user moves from summary information to detailed evidence.

Aliases concern alternate representations of fields; environment variables are not the standard dashboard mechanism for passing selected visualization context; and JSON may define dashboard structures but is not itself the contextual-value mechanism being tested.

Study Guide topics: dashboard tokens, drilldowns, contextual searches, analyst workflow, dashboard interactivity, investigation efficiency.

A Risk Incident Rule evaluates accumulated events in the risk index and determines when the combined risk associated with a particular risk object warrants escalation into an analyst-facing finding or notable.

This is a core component of Risk-Based Alerting. Individual detections can create risk events rather than immediately generating separate findings. Each event can contain a risk score, risk object, risk object type, annotations, and contextual information. A Risk Incident Rule then analyzes those events collectively. For example, a user may accumulate several moderate-risk behaviors—an unusual authentication, suspicious process activity, and anomalous access. Individually, each event may be insufficient for escalation; together, they can exceed the aggregation logic defined by the Risk Incident Rule.

This architecture significantly reduces alert fatigue because the SOC evaluates meaningful combinations of evidence rather than every low-confidence event independently.

“Risk Category” is not the correlation-search mechanism performing this aggregation. A generic “Risk Rule” does not identify the specific Enterprise Security construct being tested, and “Risk Incident Notable” describes an outcome rather than the rule evaluating risk-index activity.

Study Guide topics: Risk-Based Alerting, Risk Incident Rules, risk index, risk objects, risk aggregation, finding generation.

The relevant parameter is the Backfill range . It determines how far backward Splunk should build accelerated summary information when establishing or updating the accelerated CIM data model. The value is expressed using a relative-time specification, allowing administrators to define how much historical data should be represented in the accelerated column-store structures.

Backfilling is important because enabling acceleration today does not automatically imply that unlimited historical data should be summarized. A cyber defense team may require enough historical coverage to support detection baselines, investigations, dashboards, and retrospective searches while also controlling computational and storage cost.

For example, increasing the backfill interval gives tstats-based searches access to a larger historical period of summarized data but requires Splunk to perform more summarization work. An interval that is too short may prevent analysts from efficiently reviewing older events through accelerated searches.

Max summarization search time controls summarization execution behavior rather than the historical horizon. “Accelerate until maximum time” is not the requested setting. Although summary-range terminology is conceptually related to accelerated coverage, the question specifically describes the relative-time parameter controlling how far backward the column stores are initially generated: Backfill range .

Study Guide topics: CIM acceleration, backfill range, accelerated summaries, column stores, tstats, data-model performance.

Splunk macros make SPL shorter and reusable by encapsulating frequently used search fragments and allowing them to be inserted into other searches. A macro can contain filters, field calculations, constraints, or larger portions of SPL that would otherwise need to be duplicated across multiple detections, reports, and dashboards.

Macros are typically invoked using backticks, conceptually:

search index=security | security_filter``

The macro is resolved at search execution time into the SPL definition associated with it. Parameterized macros can also accept arguments, allowing common search logic to be reused with different values.

This is particularly important for detection engineering because centralized reusable logic reduces duplication. If ten correlation searches rely on the same constraint, a macro allows the engineer to maintain that logic centrally rather than changing all ten searches independently.

Although macros are themselves Splunk knowledge objects, Knowledge objects is too broad for the question. Lookups add external or maintained contextual data to events, while commands such as stats, eval, or tstats perform specific SPL operations rather than serving as reusable search substitutions.

Study Guide topics: SPL macros, reusable searches, search maintainability, knowledge objects, detection engineering efficiency.

The correct component is SA-ThreatIntelligence . Within Splunk Enterprise Security, this supporting add-on is associated with the threat-intelligence framework and the processing of threat indicators used for matching, enrichment, and security analytics.

Threat intelligence may contain observables such as malicious IP addresses, domains, URLs, email indicators, certificate information, file hashes, or other intelligence objects. The framework must normalize and process these indicators so that Enterprise Security searches can compare them with telemetry observed in the environment.

The SA- prefix is significant in the Splunk application ecosystem because supporting add-ons frequently provide underlying searches, knowledge objects, configurations, or framework functionality that other Splunk applications consume. The other names shown in the question are distractors and are not the designated Enterprise Security supporting add-on requested.

Threat intelligence ingestion is more than simply indexing a feed. The resulting indicators must be structured into appropriate collections and made usable by matching processes so that detections can identify interactions between internal activity and known threat objects.

Question 9 is displayed on page 3 of the supplied certification material.

Study Guide topics: SA-ThreatIntelligence, Threat Intelligence Framework, indicator ingestion, threat matching, intelligence normalization, Enterprise Security architecture.

A raw count of firewall blocks measures an output or result , not whether the security capability itself is performing effectively. Under the terminology used by the supplied course material, this makes the measurement a Key Result Indicator rather than a Key Performance Indicator .

For example, a perimeter firewall could block ten million connection attempts because the public-facing address space is being heavily scanned. A second firewall might block only one million. Those numbers alone do not establish that the first firewall is ten times more effective. External scanning volume, Internet exposure, business architecture, and traffic characteristics can change the count independently of firewall performance.

A useful KPI should instead measure performance against a defined operational objective—for example, response latency, policy deployment accuracy, control availability, processing performance, or another measurable objective tied to effectiveness. The total-block count can still provide useful operational context, but it should not automatically be interpreted as evidence that the firewall program is improving.

Option D captures precisely this distinction between activity/result volume and control performance .

Study Guide topics: security metrics, KPIs, result indicators, control effectiveness, SOC reporting, meaningful measurement.

The search retrieves Windows Security events with EventCode 4688 , which represents process creation, and then aggregates the results by parent_process_name. The stats clause calculates a count and uses values(process) to return the distinct child process values associated with each parent process. Of the supplied choices, this is best described as displaying processes and their parent processes .

The decisive SPL is:

stats count, values(process) as process by parent_process_name

The by parent_process_name clause creates result groups based on each parent process. Within every group, values(process) builds the set of process values associated with that parent. count additionally records how many qualifying events occurred within the group.

The search does not group by user, so options A and B do not describe its result structure. Option C reverses the relationship: the grouping key is the parent rather than the child process.

This type of aggregation can help detection engineers identify unusual parent-child process relationships—for example, a normally benign application unexpectedly spawning a command interpreter.

Study Guide topics: SPL stats, values(), Windows EventCode 4688, parent-child process analysis, endpoint detections.

A Business Continuity Plan (BCP) or Disaster Recovery (DR) plan is particularly useful for determining the relative importance of organizational entities because these documents identify business-critical services, recovery priorities, dependencies, and acceptable disruption thresholds . Those characteristics translate directly into security risk prioritization.

For example, two servers may exhibit identical suspicious authentication behavior, but one may support a Tier-1 payment-processing application while the other supports a low-impact internal service. A BCP/DR plan typically identifies which system requires faster recovery, has stricter Recovery Time Objectives (RTOs), or supports critical business functions. Detection engineers can use that context when designing Risk-Based Alerting , asset priority, and Risk Factors.

Infrastructure and application architecture diagrams are valuable for identifying dependencies and communication paths, but they do not necessarily document business priority . An organization chart identifies reporting relationships rather than the criticality of technical entities.

The uploaded study material supports the broader principle that risk should be contextualized using asset criticality and business impact, although this exact question is not included verbatim in the supplied 60-question set.

Study Guide topics: asset criticality, business impact, risk prioritization, Risk Factors, BCP/DR, contextual security engineering.

Status and Owner are the operational fields most directly associated with determining whether a finding has entered active analyst handling. Mean Time to Acknowledge (MTTA) measures the elapsed time between creation of a security finding and the point at which the SOC acknowledges and assumes responsibility for it.

Within an incident-management workflow, assigning an owner indicates analyst responsibility, while a status transition records progression through the handling lifecycle. These changes can therefore be used as workflow evidence when constructing SOC service-level measurements and determining whether findings are being acknowledged within the organization ' s expected response interval.

Urgency and severity describe prioritization characteristics rather than whether an analyst has actually taken ownership. Likewise, user normally describes an entity involved in the underlying security activity and does not represent the analyst responsible for the finding.

From a program-management perspective, MTTA should be distinguished from detection time, investigation duration, containment time, and Mean Time to Resolve/Respond. Each measures a different operational stage. Reliable status and ownership data therefore become important for SOC performance reporting and SLA/SLO auditing.

Question 10 appears on page 3 of the supplied material.

Study Guide topics: SOC metrics, MTTA, finding/notable management, status, ownership, service-level objectives, security-program reporting.

The correct collection is service_intel . Splunk Enterprise Security ' s Threat Intelligence Framework separates indicators into intelligence collections according to the type of observable being represented. Fully Qualified Domain Names are service-oriented network identifiers and are handled through the service intelligence collection in the context tested by this question.

This classification matters because the Threat Intelligence Framework must know which event fields and indicator types can be meaningfully compared. A domain such as malicious.example.com is semantically different from a raw IPv4/IPv6 address, a certificate fingerprint, or a complete HTTP URL. The ip_intel collection is intended for IP-oriented indicators, while certificate_intel deals with certificate-related intelligence. http_intel is associated with HTTP-oriented indicators such as URLs and related HTTP observables rather than the standalone FQDN type being asked about here.

Detection engineering depends on this normalization because matching searches must compare compatible indicator types. Correct placement also supports deduplication, expiration, weighting, threat matching, and downstream enrichment of security findings.

Study Guide topics: Threat Intelligence Framework, KV Store collections, indicator normalization, FQDN intelligence, threat matching, intelligence enrichment.

Assets are not one of the metadata types returned by Splunk ' s metadata command. The command supports indexed metadata categories including hosts, sources, and sourcetypes , making option C the exception.

Typical examples include:

| metadata type=hosts

| metadata type=sources

| metadata type=sourcetypes

The command provides summarized information about indexed data and can expose attributes such as event counts and first or last observed times without requiring analysts to perform a broad raw-event search. This makes it useful when validating data availability, determining whether a particular host or sourcetype is still reporting, and performing general data-source inventory work.

An asset , by contrast, is an enriched security entity within the broader Enterprise Security context. Asset information can be maintained through Assets and Identities mechanisms and associated lookup structures, but it is not a metadata command type.

The distinction is important in security data engineering. Indexed metadata describes how Splunk stores and categorizes incoming event data; asset context describes organizational entities and their attributes. Confusing those layers can result in inefficient searches or incorrect assumptions about where contextual information resides.

Study Guide topics: metadata, hosts, sources, sourcetypes, indexed metadata, data-source inventory, Assets and Identities.

The configuration shown contains two separate Risk Modifiers , so a single detection result will generate two risk events .

The first Risk Modifier assigns:

Risk Score: 10

Risk Object Field: src

Risk Object Type: system

The second Risk Modifier assigns:

Risk Score: 10

Risk Object Field: user

Risk Object Type: user

Splunk Enterprise Security creates a separate risk event for each configured risk modifier because each modifier applies risk to a distinct risk object . In this example, one event attributes risk to the source system represented by src, while another attributes risk to the account represented by user.

The two scores are not added together to determine the number of events . Therefore, option A (20) confuses total numerical risk contribution with event count, while option C (10) represents the score assigned to each individual risk event rather than the number created. Option B is incorrect because there are two configured risk objects.

This configuration is a common Risk-Based Alerting pattern: one suspicious action can simultaneously contribute risk to multiple entities involved in the activity.

Study Guide topics: Risk Analysis Adaptive Response Action, Risk Modifiers, risk objects, risk object types, risk scores, Risk-Based Alerting.