Question 210
The team has responded to Windows audit log cleared using this measure: Preserve collector copies and open a tampering investigation. Which post-action evidence would justify declaring the measure effective?
- Synthetic bad-password attempts appear in the SIEM with expected host and user fields
- A benign test process appears with expected ancestry and command-line detail
- Known authorized run-as operations remain distinguishable from unexplained credential use
- A test remote logon is correctly linked to user, host and source in analysis
- Collector retention remains intact and new clearing attempts are detected
Explanation
Correct Answer
E:Validating immutable external records is more meaningful than a fresh local log file. That verification specifically tests whether the intervention to preserve collector copies and open a tampering investigation corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:Testing the full logging path confirms more than local event creation, which would be relevant to Windows failed logons, but not the Windows audit log cleared scenario that requires collector retention remains intact and new clearing attempts are detected.
B:An event ID without the required fields cannot support the planned analytic; applied to this Windows audit log cleared case, it addresses Windows process start instead of the required step: collector retention remains intact and new clearing attempts are detected.
C:This relates to Windows explicit credentials: the rule should retain actor and target identity rather than merely counting events; the Windows audit log cleared question instead requires demonstrating that the remediation or control took effect, specifically collector retention remains intact and new clearing attempts are detected.
D:The pipeline must retain fields used to distinguish benign and risky access; prioritizing that Windows successful logons mechanism would leave this Windows audit log cleared decision unresolved because collector retention remains intact and new clearing attempts are detected is the direct fit.
Question 211
A responder investigating domain admin group change has corroborated this finding: Unexpected membership change grants high-impact directory privileges. What action belongs next in the approved workflow?
- Correlate elevated process starts with approved mechanisms and suspicious parents
- Monitor security-relevant autorun keys and assess new launch targets
- Escalate unauthorized membership and monitor subsequent privileged logons
- Build per-principal SPN and host baselines with targeted anomaly rules
Explanation
Correct Answer
C:An account lock alone may not remove privilege granted to other identities. Operational success is not assumed until group membership matches the approved baseline and actor activity is reviewed, the relevant outcome for this response.
Incorrect Answers
A:Detecting only logon failures would miss abuse after authentication; this evidence or action is associated with privilege token misuse, whereas the case concerns domain admin group change and calls for escalate unauthorized membership and monitor subsequent privileged logons.
B:Blocking all registry edits is infeasible and would not identify persistence intent; that is suited to investigating run key persistence, whereas the domain admin group change case requires escalate unauthorized membership and monitor subsequent privileged logons for choosing the immediate operational response.
D:Counting all Kerberos traffic globally will produce weak, noisy alerts, which would be relevant to Kerberos ticket anomaly, but not the domain admin group change scenario that requires escalate unauthorized membership and monitor subsequent privileged logons.
Question 212
The SOC has completed this action: Build role-specific baselines and investigate deviations within the proper group. Which result provides the strongest assurance that the specific problem was addressed?
- A test API call becomes observable before the hunt is repeated
- The hunt records evidence for or against the hypothesis and creates detection improvements
- Test outliers are detected without flagging expected high-volume service traffic
- A controlled simulation demonstrates the defensive mechanism prevents or detects abuse
Explanation
Correct Answer
C:Good hunt quality depends on discriminating abnormal from merely uncommon. That verification specifically tests whether the intervention to build role-specific baselines and investigate deviations within the proper group corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:Measurable telemetry readiness precedes defensible negative conclusions; this evidence or action is associated with hunt data gap, whereas the case concerns hunt peer baselines and calls for test outliers are detected without flagging expected high-volume service traffic.
B:A zero-findings hunt can still be useful if coverage was verified; that is suited to investigating hypothesis-driven hunt, whereas the hunt peer baselines case requires test outliers are detected without flagging expected high-volume service traffic for demonstrating that the remediation or control took effect.
D:For MITRE D3FEND application, documentation tags alone cannot prove implemented control effectiveness; here the narrower objective is demonstrating that the remediation or control took effect in hunt peer baselines, best addressed by test outliers are detected without flagging expected high-volume service traffic.
Question 213
Ransomware operators delete recent restore points before encrypting production systems. Supporting evidence includes: Backup audit events, management logons and immutable copy status. Which next step most directly reduces the described risk?
- Isolate compromised hosts and interrupt affected share access promptly
- Restore into isolated validated infrastructure after containment and secret rotation
- Restrict compromised backup administrators and protect offline or immutable copies
- Apply the root-cause fix and update detections and runbooks
Explanation
Correct Answer
C:A new scheduled backup is not safe if the attacker retains admin access. For safe case progression, preserve the evidence and later verify an isolated restore test succeeds and attacker credentials no longer manage backups.
Incorrect Answers
A:This relates to ransomware early containment: waiting for a ransom note before response increases impact; the compromised backup repository question instead requires choosing the immediate operational response, specifically restrict compromised backup administrators and protect offline or immutable copies.
B:Recovering straight into an exposed segment can undo restoration work; that is suited to investigating ransomware recovery staging, whereas the compromised backup repository case requires restrict compromised backup administrators and protect offline or immutable copies for choosing the immediate operational response.
D:A retrospective report without assigned remediations does not reduce risk; this evidence or action is associated with ransomware lessons learned, whereas the case concerns compromised backup repository and calls for restrict compromised backup administrators and protect offline or immutable copies.
Question 214
A SOC wants to programmatically retrieve standardized intelligence collections from a partner. Supporting evidence includes: TAXII collection metadata, authentication and poll cursor behavior. Which next step most directly reduces the described risk?
- Build role-specific baselines and investigate deviations within the proper group
- Normalize and deduplicate intelligence before publishing to SIEM detections
- Route the intelligence only to authorized recipients and systems
- Connect the authorized TAXII collection with appropriate polling and deduplication
Explanation
Correct Answer
D:Using STIX formatting alone does not specify an exchange endpoint. For safe case progression, preserve the evidence and later verify new objects arrive once with source provenance and no skipped updates.
Incorrect Answers
A:The alternative concerns hunt peer baselines: a one-size-fits-all global rate misses context and drives false positives; however, the described TAXII feed transport situation calls for connect the authorized TAXII collection with appropriate polling and deduplication.
B:For threat intelligence platform, directly pushing every feed entry can multiply noisy matches; here the narrower objective is choosing the immediate operational response in TAXII feed transport, best addressed by connect the authorized TAXII collection with appropriate polling and deduplication.
C:A useful IOC is not automatically public information, which would be relevant to TLP handling, but not the TAXII feed transport scenario that requires connect the authorized TAXII collection with appropriate polling and deduplication.
Question 215
Responders suspect incident trend analysis based on this observation: A collection-scope increase explains part of the apparent incident increase. Which artifact should be examined first?
- Sensor onboarding dates, comparable asset population and severity trends
- Source events with identity, origin and failure reason fields
- Service Control Manager events, service binary path and remote logon evidence
- Ticket timestamps for detection, acknowledgment, escalation and enforcement
Explanation
Correct Answer
A:Normalizing by coverage makes before-and-after comparisons fairer. Linking these records back to a collection-scope increase explains part of the apparent incident increase reduces reliance on an isolated indicator.
Incorrect Answers
B:Those attributes support root-cause and targeted triage, which would be relevant to SOC dashboard drilldown, but not the incident trend analysis scenario that requires sensor onboarding dates, comparable asset population and severity trends.
C:Temporal sequence identifies who created and started the service, which would be relevant to service-based execution, but not the incident trend analysis scenario that requires sensor onboarding dates, comparable asset population and severity trends.
D:The timeline must separate workflow touches from effective mitigation; this evidence or action is associated with SOC SLA breach, whereas the case concerns incident trend analysis and calls for sensor onboarding dates, comparable asset population and severity trends.
Question 216
During an investigation of encoded PowerShell, the SOC validates this finding: An encoded PowerShell invocation from an untrusted parent process. What should the response owner do next?
- Alert on suspicious office process ancestry with signer and policy context
- Decode and inspect the script before deciding containment and detection tuning
- Correlate WMI launches with management allowlists and suspicious process trees
- Verify both sessions and elevate risk if distinct devices cannot be explained
- Build behavior-focused detection for the specific binary and suspicious arguments
Explanation
Correct Answer
B:Blocking all encoded parameters without context may disrupt legitimate management. For safe case progression, preserve the evidence and later verify test payloads are detected using parent and script behavior rather than encoding alone.
Incorrect Answers
A:A global shell-block rule could break legitimate administration unrelated to Office; that is suited to investigating office child process, whereas the encoded PowerShell case requires decode and inspect the script before deciding containment and detection tuning for choosing the immediate operational response.
C:Network port observations alone cannot reliably classify intent, which would be relevant to WMI remote execution, but not the encoded PowerShell scenario that requires decode and inspect the script before deciding containment and detection tuning.
D:This relates to impossible travel triage: an automatic suspension based solely on IP geography can disrupt valid users; the encoded PowerShell question instead requires choosing the immediate operational response, specifically decode and inspect the script before deciding containment and detection tuning.
E:For living-off-the-land binaries, a blocklist of unsigned executables would miss native-tool misuse; here the narrower objective is choosing the immediate operational response in encoded PowerShell, best addressed by decode and inspect the script before deciding containment and detection tuning.
Question 217
A contractor continues using a VPN account two days after their contract ends. Which finding best distinguishes this activity from a routine operational change?
- High-volume sensitive reads may breach the user's documented business need
- Break-glass access occurs outside an approved emergency with unusual origin
- Authentication succeeds after the identity's approved expiry date
- Bulk access to confidential code exceeds usual repository activity
Explanation
Correct Answer
C:Offboarding failure exposes resources even if no malicious action is yet proved. Investigators should still corroborate it with contract end, identity status, VPN sessions and accessed systems before assigning definitive scope or attribution.
Incorrect Answers
A:Access permission alone does not prove an action was authorized for the task; this evidence or action is associated with insider database extraction, whereas the case concerns departing contractor access and calls for authentication succeeds after the identity's approved expiry date.
B:Exceptional privileges need stronger accountability than routine admin use; prioritizing that misuse of break-glass account mechanism would leave this departing contractor access decision unresolved because authentication succeeds after the identity's approved expiry date is the direct fit.
D:This relates to suspicious source-code export: repository access must be assessed against job role and authorized work; the departing contractor access question instead requires recognizing the distinguishing signal, specifically authentication succeeds after the identity's approved expiry date.
Question 218
Responders addressed insider bulk export using this measure: Escalate under insider-threat procedures and preserve access evidence. What should the SOC test before considering closure?
- Previously affected pages render content safely and browser execution no longer occurs
- Test payloads no longer alter query behavior and logs show no successful exploitation
- Untrusted-origin submissions fail while legitimate authenticated changes still succeed
- The export is accounted for and unauthorized access paths are closed
Explanation
Correct Answer
D:Suspicious activity must be resolved against an approved business purpose, not only volume thresholds. That verification specifically tests whether the intervention to escalate under insider-threat procedures and preserve access evidence corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:For stored cross-site scripting, a server-side input check without output-context testing can miss residual script execution; here the narrower objective is demonstrating that the remediation or control took effect in insider bulk export, best addressed by the export is accounted for and unauthorized access paths are closed.
B:Simply suppressing database error messages could hide an unfixed injection flaw; this evidence or action is associated with SQL injection, whereas the case concerns insider bulk export and calls for the export is accounted for and unauthorized access paths are closed.
C:Blocking all requests is not a valid functional security fix, which would be relevant to cross-site request forgery, but not the insider bulk export scenario that requires the export is accounted for and unauthorized access paths are closed.
Question 219
The first-line team is investigating Google SecOps investigation. Its preliminary finding is: Cross-source detection needs normalized telemetry and rule evaluation. What corroborating material is most decisive?
- Entra role activation logs, approval context and sign-in details
- Google SecOps ingestion mappings, normalized fields and detection result context
- Principal grants, database audit events and provider service boundary documentation
- SCC finding category, resource name, organization scope and state
Explanation
Correct Answer
B:Consistent identities and timestamps are essential across feeds. Linking these records back to cross-source detection needs normalized telemetry and rule evaluation reduces reliance on an isolated indicator.
Incorrect Answers
A:This relates to Azure privileged identity: role assignment and activation are different from ordinary resource API calls; the Google SecOps investigation question instead requires independently corroborating the suspected behavior, specifically Google SecOps ingestion mappings, normalized fields and detection result context.
C:The root cause depends on customer-controlled authorization, not physical hosting; prioritizing that cloud shared responsibility mechanism would leave this Google SecOps investigation decision unresolved because Google SecOps ingestion mappings, normalized fields and detection result context is the direct fit.
D:Project scope and activation level affect visibility and handling; this evidence or action is associated with GCP Security Command Center, whereas the case concerns Google SecOps investigation and calls for Google SecOps ingestion mappings, normalized fields and detection result context.
Question 220
The working hypothesis concerns entity enrichment. The initial finding is: Missing asset and ownership context prevents severity assessment. Which evidence should investigators prioritize?
- Exercise timeline, source ingestion and rule query results
- Correlation keys, matched rule IDs and underlying event identifiers
- Change ticket, scanner identity, source IP and scan time correlation
- CMDB identity, endpoint inventory, network segment and owner mapping
Explanation
Correct Answer
D:Entity enrichment provides the business and technical context missing from raw IPs. This is particularly useful after the initial sign of missing asset and ownership context prevents severity assessment; the two forms of evidence test different parts of the case.
Incorrect Answers
A:The gap could be absent logs, parsing mistakes or faulty rule conditions; this evidence or action is associated with false negative detection, whereas the case concerns entity enrichment and calls for CMDB identity, endpoint inventory, network segment and owner mapping.
B:For alert deduplication, grouping should preserve distinct attack stages, not erase independent evidence; here the narrower objective is independently corroborating the suspected behavior in entity enrichment, best addressed by CMDB identity, endpoint inventory, network segment and owner mapping.
C:Positive identification is safer than suppressing by an entire network segment; that is suited to investigating false positive assessment, whereas the entity enrichment case requires CMDB identity, endpoint inventory, network segment and owner mapping for independently corroborating the suspected behavior.