10 free sample questions from a bank of 172, with the correct answers and explanations. No signup required — start practising right now.
1What makes a playbook appear for a Security Incident if using Flow Designer?
Actions defined to create tasks
Trigger set to conditions that match the security incident
Runbook property set to true
Service Criticality set to High
Answer: B
The short version
B — Trigger set to conditions that match the security incident. A Flow Designer playbook only appears when its trigger evaluates true for that incident, so matching conditions are the deciding factor.
Key concepts in this question
Playbook trigger: the record-based condition that tells Flow Designer when a flow should be offered or auto-run for a security incident.
Flow Designer flows: reusable trigger plus action sequences used in SIR to drive response tasks and playbook tabs.
Security incident table: the sn_si_incident record whose field values are evaluated against the trigger.
Playbook tab rendering: the UI shows only flows whose trigger matches, keeping analysts focused on relevant response paths.
Why B is correct
Vancouver guidance states that for a playbook to be invoked automatically the trigger condition must be met and then the playbook tab is rendered. Flow Designer evaluates the trigger against the current security incident fields such as category, priority, or observables. When those conditions match, the platform surfaces that specific playbook for the analyst to run.
Why the others are wrong
A. Actions that create tasks are steps inside the flow, they do not control whether the playbook appears in the first place.
C. There is no runbook property set to true that gates playbook visibility in Flow Designer.
D. Service criticality may inform priority or risk but it alone does not bind a playbook trigger to an incident.
CIS-SIR exam tip
Think trigger first: if the question asks when a playbook appears, look for the matching trigger condition.
2Select the one capability that retrieves a list of running processes on a CI from a host or endpoint.
Get Network Statistics
Isolate Host
Get Running Processes
Publish Watchlist
Block Action
Sightings Search
Answer: C
The short version
C — Get Running Processes lists processes on a CI host. This single capability queries the endpoint agent and returns the live process inventory for investigation.
Key concepts in this question
Security orchestration capabilities: prebuilt actions that run against a CI through an integration such as endpoint protection.
Get Running Processes: the capability that returns process name, PID, path, and owner from the target host.
CI-centric enrichment: results attach to the incident or CI to support scoping and containment decisions.
Host versus network actions: process listing is distinct from network stats, isolation, or sightings search.
Why C is correct
ServiceNow docs define Get Running Processes as the capability that retrieves the list of running processes from a host or endpoint CI. The analyst runs it against the affected CI during triage to spot malware, suspicious parents, or unusual executables. No other listed capability performs that host process enumeration.
Why the others are wrong
A. Get Network Statistics returns active connections, not the process table.
B. Isolate Host quarantines the endpoint by restricting connectivity, it does not list processes.
D. Publish Watchlist pushes indicators for monitoring, it does not query the host.
E. Block Action blocks a hash, IP, or domain at the tool, it does not enumerate processes.
F. Sightings Search looks for indicator sightings across tools, it does not pull the live process list.
CIS-SIR exam tip
Map verb to capability: retrieves processes equals Get Running Processes, retrieves connections equals Get Network Statistics.
3Actions packaged in Scoped applications are called:
Action Groups
Categories
Spokes
Subflows
Answer: C
The short version
C — Scoped packaged actions are called Spokes. A spoke bundles related actions into a scoped app so Flow Designer authors can reuse them without coding.
Key concepts in this question
Flow Designer actions: reusable operations that take inputs and return outputs inside flows and subflows.
Scoped applications: application scope packaging that protects code and namespaces integrations.
Spokes: the product term for a set of actions and related components shipped as a scoped app.
Categories: logical groupings of actions inside the designer, not the packaging unit itself.
Why C is correct
Ebook p267 states that actions are organized into categories, while actions packaged into a scoped application and made available as a set are called spokes. The Security Operations spoke is the SIR example, exposing SIR actions to Flow Designer. That packaging lets admins install, version, and permission the set as one unit.
Why the others are wrong
A. Action Groups is not the platform term for scoped packaged actions.
B. Categories organize actions for browsing, they are not the scoped deployable package.
D. Subflows are reusable flow fragments, not the packaging name for scoped actions.
CIS-SIR exam tip
Remember scope equals spoke: if it says scoped app with a set of actions, answer Spokes.
4When testing a flow, the action outcomes can be found where?
Configuration Details
System Log
Execution Details
Content Record
Answer: C
The short version
C — Action outcomes appear in Execution Details. Test runs log each step inputs, outputs, and status there for tracing and debugging.
Key concepts in this question
Flow testing: running a flow with test data to validate logic before activation.
Execution Details: the run viewer showing step-by-step start, status, inputs, outputs, and errors.
Action outcomes: the data pills and return values produced by each action for downstream use.
Operational logs: system logs record platform events but not the structured flow trace.
Why C is correct
Ebook p270 notes the Flow Designer Execution Details view displays everything required to trace and analyze execution. After a test, opening Execution Details reveals each action outcome, making it possible to confirm mappings and find failures. This is the designed debugging surface for authors.
Why the others are wrong
A. Configuration Details show setup of the flow or action, not live run outcomes.
B. System Log captures platform messages, not the per-action outcome pills.
D. Content Record stores static content, not dynamic test execution results.
CIS-SIR exam tip
Testing a flow means opening Execution Details to see outcomes and trace the run. For revision, trace the path in a lab instance from trigger to action to response task, noting which table stores each stage and which role can configure it. Compare the correct wording with nearby distractors that swap tables, actions, or roles, since the exam often tests those swaps. Lock the core pairing by reciting the trigger plus table plus outcome once more before moving on.
5Flow Logic in the baseline includes: (Choose two.)
For Each Loops
Interrupts
If Then conditions
Function Calls
Wait until
Answer: A, C
The short version
AC — Baseline flow logic is For Each and If Then. These two cover looping over records and conditional branching without custom code.
Key concepts in this question
Flow logic: control structures that direct how a flow iterates or branches.
For Each Loops: iterate the same actions over each record in a list, such as affected CIs.
If Then conditions: evaluate a condition to choose which branch or actions run next.
Extended logic: parallel branches, do-until, and decision tables build on these baseline patterns.
Why AC is correct
Product docs list If, Else, and Else If for conditional actions and For Each for applying actions to multiple records as core flow logic. Both ship baseline in Flow Designer and appear in every SIR playbook discussion. The other choices are either nonstandard names or advanced patterns not counted as the two baseline items here.
Why the others are wrong
B. Interrupts is not a baseline Flow Designer logic element.
D. Function Calls is a coding concept, not the named baseline flow logic control.
E. Wait until style pauses are not one of the two asked-for baseline logic items in this key.
CIS-SIR exam tip
Pair loops with conditions: For Each plus If Then is the classic baseline logic duo. For revision, trace the path in a lab instance from trigger to action to response task, noting which table stores each stage and which role can configure it. Compare the correct wording with nearby distractors that swap tables, actions, or roles, since the exam often tests those swaps. Lock the core pairing by reciting the trigger plus table plus outcome once more before moving on.
6What contains a set of reusable operations that are designed to be used in multiple playbooks?
Flows
Actions
Trigger
Subflows
Answer: D
The short version
D — Subflows hold reusable operations for multiple playbooks. Playbook design in Security Incident Response favors building once and reusing often. Subflows provide that shared building block, so consistent logic runs across many playbooks without duplication.
Key concepts in this question
Playbook: an orchestrated sequence built in Flow Designer that guides analyst response for a security incident category
Subflow: a reusable flow segment that packages operations, inputs and outputs for calling from multiple parent flows or playbooks
Flow: a top-level automation that has its own trigger, while a subflow has no independent trigger and must be called
Action: a single reusable operation step, whereas a subflow groups several actions and logic into a larger reusable unit
Trigger: the event that starts a flow, such as record creation or update, distinct from reusable logic itself
Why D is correct
Subflows are explicitly defined in SIR training as a set of reusable operations designed to be used in multiple playbooks. They accept inputs, run a defined sequence, and return outputs to each calling playbook. This design lets teams maintain shared enrichment, containment, or notification logic in one place. Updating the subflow then fixes behavior everywhere it is used.
Why the others are wrong
A. Flows run independently with their own triggers and are not designed as callable shared fragments for playbooks
B. Actions are atomic steps, useful for reuse, but they do not package a full set of multi-step operations the way the question describes
C. Trigger only initiates execution and contains no reusable operational logic for sharing across playbooks
CIS-SIR exam tip
Think sub equals shared subroutine: if the stem says set of reusable operations across playbooks, choose Subflow every time.
7What automates processes and supports triggers with a sequence of reusable actions?
Subflows
Actions
Flows
Activities
Answer: C
The short version
C — Flows automate processes with triggers plus reusable actions. A flow binds an event trigger to an ordered action sequence analysts can rerun.
Key concepts in this question
Flows: top-level Flow Designer automations started by a trigger.
Triggers: record, schedule, or application events that start the flow.
Reusable actions: modular steps with inputs and outputs shared across flows.
Subflows and activities: related building blocks, but only flows pair triggers with full sequences.
Why C is correct
Ebook p265 under Flows describes a sequence of actions that includes triggers. That trigger-plus-actions pairing is the definition tested here. SIR playbooks are implemented as such flows, so selecting Flows matches both the platform model and the security use case.
Why the others are wrong
A. Subflows are triggerless reusable fragments called by flows, they do not start from a trigger themselves.
B. Actions are single steps, they need a flow to provide trigger and order.
D. Activities belong to legacy workflow engine terminology, not Flow Designer trigger sequences.
CIS-SIR exam tip
Hear triggers with a sequence of reusable actions and pick Flows. For revision, trace the path in a lab instance from trigger to action to response task, noting which table stores each stage and which role can configure it. Compare the correct wording with nearby distractors that swap tables, actions, or roles, since the exam often tests those swaps. Lock the core pairing by reciting the trigger plus table plus outcome once more before moving on.
8Once a Phishing Email record is created, which Flow creates a new Security Incident record?
Security Incident - Phishing Manual
Security Incident - Automated Phishing Playbook
Child Incident Automated Flow
Transform Phishing Email to Security Incident
Answer: D
The short version
D — Transform Phishing Email to Security Incident creates the incident. Once a phishing email record exists, this flow converts it into a proper SIR incident.
Key concepts in this question
User reported phishing: inbound emails stored first as phishing email records for validation.
Transform flow: the orchestrated conversion that creates the sn_si_incident and links context.
Phishing playbooks: manual or automated follow-on handling after the incident exists.
Aggregation logic: the transform decides new incident versus merge with an existing phishing campaign.
Why D is correct
Docs state the Transform Phishing Email to Security Incident flow converts phishing email records to security incidents. It runs after creation of the phishing record, evaluates duplication, and generates the incident with email context carried over. The other flows handle later response, not initial creation.
Why the others are wrong
A. Security Incident Phishing Manual is a response path, not the creation flow.
B. Automated Phishing Playbook acts after the incident exists, it does not create it.
C. Child Incident Automated Flow manages child linkage, not phishing-to-incident transformation.
CIS-SIR exam tip
Phishing email becomes incident only through the Transform Phishing Email to Security Incident flow.
9When an inbound email is processed and identified as a phishing email what table is it stored in for URP v2?
Security Incident Alert
Security Incident Phishing Email
Security Incident
Incident
Answer: B
The short version
B — Inbound phishing mail lands in Security Incident Phishing Email. URP v2 stages raw reports there before any incident is created.
Key concepts in this question
URP v2 pipeline: inbound action plus ingestion rules plus transform flow for user reported phishing.
Security Incident table: created only after transform and dedup decisions.
Alert versus incident: alerts are tool signals, phishing emails are user reported messages with distinct handling.
Why B is correct
Ebook p312 explains that once the Security Incident Phishing Email record is created it triggers the transform flow, which then creates the security incident and decides new versus aggregate. Staging first allows parsing, observable extraction, and duplicate checks without polluting the incident table. That two-stage design is core to URP v2.
Why the others are wrong
A. Security Incident Alert is for integrated tool alerts, not user reported phishing mail.
C. Security Incident is the downstream output, not the initial landing table.
D. Incident is the generic IT table, not the SIR phishing staging table.
CIS-SIR exam tip
URP mail first hits Phishing Email table, then transform makes the incident.
10In order to use User Reported Phishing v2, what must occur in Flow Designer?
Transform Flow must be published
Transform Flow must be activated
Transform Action must be activated
Phishing Email Aggregation Subflow must be activated
Transform Flow must be copied and activated
Answer: E
The short version
E — Copy and activate the baseline Transform Flow to use User Reported Phishing v2. The shipped flow is a template that must not be edited directly. Duplicating it creates an editable copy, and activation makes it executable for phishing mail.
Key concepts in this question
User Reported Phishing v2: the SIR mechanism that ingests employee-forwarded suspect mail and builds phishing email and incident records
Transform Flow: Flow Designer logic that maps fields from the phishing email staging record into a security incident
Copy operation: duplicating a baseline flow so customizations survive upgrades and baseline remains intact
Activation: publishing and enabling a flow version so the runtime will actually execute it on trigger
Flow Designer: the low-code automation studio where flows, subflows, actions, and data pills are assembled
Why E is correct
Baseline SIR content ships inactive as a template customers must copy before use. The phishing transform flow must therefore be copied and then activated to create the runnable copy. Without a copy edits are lost on upgrade, and without activation the logic never fires. That copy-plus-activate pattern is the documented prerequisite for User Reported Phishing v2.
Why the others are wrong
A. Publishing alone without copying would modify baseline and still leaves upgrade and ownership problems unresolved
B. Activating the baseline directly is discouraged because baseline should remain a template, not the live execution
C. Transform Action activation confuses a single step with the full mapping flow that must run end to end
D. Phishing Email Aggregation Subflow handles aggregation logic, not the initial transform mapping required for ingestion
CIS-SIR exam tip
Remember copy then activate for baseline transforms: if the question mentions Flow Designer prerequisite for phishing v2, pick the copy-and-activate choice.