Splunk Updated SPLK-5002 Exam Questions and Answers by dulcie

EventCode 4104 represents PowerShell Script Block Logging , making it the relevant telemetry for inspecting PowerShell code executed in an environment. The question specifically ties the detection requirement to PowerShell Script Block Logging and therefore directly points to 4104.

Script Block Logging provides visibility into PowerShell script content after PowerShell has processed the command or script block. From a detection-engineering perspective, this can expose suspicious commands, modules, functions, credential-access behavior, encoded or obfuscated PowerShell content, and scripts associated with offensive frameworks. An engineer can search this telemetry for characteristics associated with the behavior discovered during the red-team exercise and subsequently operationalize reliable indicators into a detection.

EventCode 4624 , by comparison, represents a successful Windows logon and can be useful in authentication and lateral-movement analysis, but it is not the PowerShell Script Block Logging event explicitly requested. The remaining distractor event codes do not represent the logging mechanism identified in the question.

The distinction matters because endpoint detections depend on selecting telemetry that observes the relevant layer of attacker behavior. Here, PowerShell execution content—not merely authentication—is the required visibility source.

Study Guide topics: PowerShell logging, EventCode 4104, endpoint telemetry, behavioral detection, red-team findings, Windows security monitoring.

An Input playbook is the appropriate playbook type when the workflow must be invoked directly from Splunk Mission Control or Enterprise Security. Input playbooks are designed with an externally supplied input interface so that another Splunk security product can provide the data required by the playbook at invocation time.

This distinction matters because externally initiated playbooks need a defined contract describing what values the calling system passes into the workflow. Mission Control or Enterprise Security may provide information associated with the finding, event, entity, indicator, or investigation. The Input playbook can then use those supplied values for enrichment, investigation, containment, or other automated actions.

A generic Automation playbook is focused on orchestration logic but does not represent the specific external invocation model being tested. “Process” and “Response” are distractors in this context and do not identify the required playbook type.

Architecturally, Input playbooks help decouple the upstream detection platform from SOAR implementation details: Enterprise Security identifies the security condition and passes structured information, while SOAR executes the automated workflow.

Study Guide topics: Splunk SOAR playbook types; Input playbooks; Mission Control integration; Enterprise Security integration; external playbook invocation.

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.

When automation can disable a user account or system, the engineer should coordinate and communicate that behavior to the IT Help Desk . Such containment actions directly affect users and business services and can immediately generate support calls, login failures, access-loss complaints, or outage reports.

The Help Desk therefore needs to understand what automated security actions may occur, how to recognize them, where to verify that security automation initiated the action, and how to escalate the case appropriately. Without this coordination, support personnel might unknowingly reverse a legitimate containment action—for example, re-enabling an account that SOAR disabled because of confirmed malicious activity.

Option C is a useful technical guardrail but does not answer the question ' s emphasis on an external support consideration . Playbook logging is important for auditability but does not establish coordination with another operational team. Adding a generic support tag does not provide the necessary organizational process.

The supplied course material supports this broader automation-safety principle through its OODA automation discussion, particularly the requirement to perform checks before consequential automated actions.

Study Guide topics: SOAR automation, containment, cross-functional coordination, Help Desk procedures, automation guardrails, operational support.