Question 300
Responders addressed double extortion using this measure: Preserve exfiltration evidence and involve privacy and legal response owners. What should the SOC test before considering closure?
- The data impact assessment is documented independently of restore status
- Restored services pass integrity checks and remain free of attacker access under monitoring
- Adversary simulation no longer succeeds and ownership for residual risk is recorded
- An isolated restore test succeeds and attacker credentials no longer manage backups
- No new encrypted files are created and share activity remains controlled
Explanation
Correct Answer
A:Recovery completion does not mean exfiltration findings are closed. That verification specifically tests whether the intervention to preserve exfiltration evidence and involve privacy and legal response owners corrected the issue rather than merely hiding an alert.
Incorrect Answers
B:Boot success alone is not safe recovery; that is suited to investigating ransomware recovery staging, whereas the double extortion case requires the data impact assessment is documented independently of restore status for demonstrating that the remediation or control took effect.
C:Lessons learned need tracked outcomes, not just meeting minutes; this evidence or action is associated with ransomware lessons learned, whereas the case concerns double extortion and calls for the data impact assessment is documented independently of restore status.
D:Backup job success alone does not prove restorability; applied to this double extortion case, it addresses compromised backup repository instead of the required step: the data impact assessment is documented independently of restore status.
E:This relates to ransomware early containment: stopping the first process does not rule out other encryptors; the double extortion question instead requires demonstrating that the remediation or control took effect, specifically the data impact assessment is documented independently of restore status.
Question 301
A SOC analyst is investigating Linux auditd file access and records this observation: auditd syscall records linked to configured file watches. Which source or comparison would most directly corroborate it?
- auditd events joining syscall, path, user ID and process attributes
- sshd authentication entries with address, account and PAM outcome
- sudo and PAM logs linked to the user's session and executed command
- journald Storage setting, disk paths and remote collector acknowledgments
Explanation
Correct Answer
A:A watch on the right path is necessary; ordinary application messages may omit attribution. This is particularly useful after the initial sign of auditd syscall records linked to configured file watches; the two forms of evidence test different parts of the case.
Incorrect Answers
B:Different Linux distributions place records in different files or journal units; that is suited to investigating Linux SSH failures, whereas the Linux auditd file access case requires auditd events joining syscall, path, user ID and process attributes for independently corroborating the suspected behavior.
C:Successful authorization must be distinguished from rejected elevation attempts; this evidence or action is associated with Linux sudo activity, whereas the case concerns Linux auditd file access and calls for auditd events joining syscall, path, user ID and process attributes.
D:The persistence setting and external copies determine retention through reboot, which would be relevant to systemd journal persistence, but not the Linux auditd file access scenario that requires auditd events joining syscall, path, user ID and process attributes.
Question 302
The SOC has completed this action: Correlate privileged group additions with approvals and subsequent activity. Which result provides the strongest assurance that the specific problem was addressed?
- The unapproved service is absent and test service installations are still logged
- Authorized membership changes are traceable and unapproved additions are reversed
- An approved provisioning test is logged and unauthorized new accounts are investigated
- Required audit subcategories are active and representative events reach collectors
Explanation
Correct Answer
B:Success requires validating actual directory group membership. It documents the result of this response step—Correlate privileged group additions with approvals and subsequent activity—and helps determine whether the protective state persists.
Incorrect Answers
A:For Windows service installation, the SOC must verify both eradication and continued detection coverage; here the narrower objective is demonstrating that the remediation or control took effect in Windows group membership, best addressed by authorized membership changes are traceable and unapproved additions are reversed.
C:Account creation events should be contextualized with change requests; applied to this Windows group membership case, it addresses Windows account created instead of the required step: authorized membership changes are traceable and unapproved additions are reversed.
D:Effective state and ingestion must both be tested after remediation; this evidence or action is associated with Windows policy change, whereas the case concerns Windows group membership and calls for authorized membership changes are traceable and unapproved additions are reversed.
Question 303
A cloud provider monitors infrastructure while an internal team owns application identities and business workflows. Which finding best distinguishes this activity from a routine operational change?
- An alert requires privileged containment outside the provider's delegated remit
- Two active tickets have no explicit primary incident owner
- The departing shift owns open containment decisions with no incoming acknowledgement
- Alerts span infrastructure telemetry and enterprise identity activity
Explanation
Correct Answer
D:No single team has the full evidence needed to decide whether a cloud workload is compromised. Confirmation should then examine a shared escalation matrix mapping cloud and application control planes; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:For managed SOC boundary, the managed service may detect and recommend, but authorization remains with the customer; here the narrower objective is recognizing the distinguishing signal in hybrid SOC coordination, best addressed by alerts span infrastructure telemetry and enterprise identity activity.
B:Duplicated tracking without an accountable lead can create gaps in containment and communications; this evidence or action is associated with incident ownership, whereas the case concerns hybrid SOC coordination and calls for alerts span infrastructure telemetry and enterprise identity activity.
C:A change in personnel can strand urgent steps even when alerts remain visible, which would be relevant to follow-the-sun transfer, but not the hybrid SOC coordination scenario that requires alerts span infrastructure telemetry and enterprise identity activity.
Question 304
A service account suddenly requests service tickets for many unfamiliar SPNs. Supporting evidence includes: Domain controller 4769 records and requestor host process lineage. Which next step most directly reduces the described risk?
- Correlate elevated process starts with approved mechanisms and suspicious parents
- Detect unapproved task definitions and investigate the registering process
- Escalate unauthorized membership and monitor subsequent privileged logons
- Build per-principal SPN and host baselines with targeted anomaly rules
Explanation
Correct Answer
D:Counting all Kerberos traffic globally will produce weak, noisy alerts. For safe case progression, preserve the evidence and later verify a crafted unusual-SPN test alerts without flooding on normal application tickets.
Incorrect Answers
A:The alternative concerns privilege token misuse: detecting only logon failures would miss abuse after authentication; however, the described Kerberos ticket anomaly situation calls for build per-principal SPN and host baselines with targeted anomaly rules.
B:This relates to scheduled task persistence: deleting the running process is insufficient if the trigger remains installed; the Kerberos ticket anomaly question instead requires choosing the immediate operational response, specifically build per-principal SPN and host baselines with targeted anomaly rules.
C:An account lock alone may not remove privilege granted to other identities; that is suited to investigating domain admin group change, whereas the Kerberos ticket anomaly case requires build per-principal SPN and host baselines with targeted anomaly rules for choosing the immediate operational response.
Question 305
Responders addressed DNS algorithmic names using this measure: Detect anomalous NXDOMAIN bursts with client-specific baselines. What should the SOC test before considering closure?
- Suspicious simulated callbacks alert while approved telemetry agents are excluded narrowly
- Approved certificate rotation works and a simulated interceptor remains blocked
- Benign typo traffic stays below threshold and test DGA sequences are flagged
- Authorized integrations remain usable while the tested unauthorized path is denied
Explanation
Correct Answer
C:A good rule controls false positives from software probes. The measure should be evaluated against the actual action, detect anomalous NXDOMAIN bursts with client-specific baselines, rather than against ticket status.
Incorrect Answers
A:This relates to low-and-slow beacon: the suppression must identify vetted software rather than arbitrary destinations; the DNS algorithmic names question instead requires demonstrating that the remediation or control took effect, specifically benign typo traffic stays below threshold and test DGA sequences are flagged.
B:Testing only successful TLS establishment ignores trust requirements; that is suited to investigating TLS certificate anomaly, whereas the DNS algorithmic names case requires benign typo traffic stays below threshold and test DGA sequences are flagged for demonstrating that the remediation or control took effect.
D:The alternative concerns unexpected outbound port: verification needs both security and application health evidence; however, the described DNS algorithmic names situation calls for benign typo traffic stays below threshold and test DGA sequences are flagged.
Question 306
The first-line team is investigating Linux SSH failures. Its preliminary finding is: Authentication failures in journald or distribution auth logs. What corroborating material is most decisive?
- macOS log show or log stream output scoped to process and time
- journald Storage setting, disk paths and remote collector acknowledgments
- auditd events joining syscall, path, user ID and process attributes
- sudo and PAM logs linked to the user's session and executed command
- sshd authentication entries with address, account and PAM outcome
Explanation
Correct Answer
E:Different Linux distributions place records in different files or journal units. This is particularly useful after the initial sign of authentication failures in journald or distribution auth logs; the two forms of evidence test different parts of the case.
Incorrect Answers
A:The alternative concerns macOS unified logging: correct predicates filter the relevant subsystem without requiring Linux auth.log files; however, the described Linux SSH failures situation calls for sshd authentication entries with address, account and PAM outcome.
B:The persistence setting and external copies determine retention through reboot; applied to this Linux SSH failures case, it addresses systemd journal persistence instead of the required step: sshd authentication entries with address, account and PAM outcome.
C:This relates to Linux auditd file access: a watch on the right path is necessary; ordinary application messages may omit attribution; the Linux SSH failures question instead requires independently corroborating the suspected behavior, specifically sshd authentication entries with address, account and PAM outcome.
D:Successful authorization must be distinguished from rejected elevation attempts; prioritizing that Linux sudo activity mechanism would leave this Linux SSH failures decision unresolved because sshd authentication entries with address, account and PAM outcome is the direct fit.
Question 307
A finance employee receives a payment change request apparently from a trusted supplier. Supporting evidence includes: Full message headers, prior payment records and out-of-band supplier verification. Which next step most directly reduces the described risk?
- Quarantine nonaligned high-risk messages and validate legitimate sender configuration
- Secure the exceptional identity and launch high-priority access review
- Preserve the message and isolate affected endpoints while purging identical attachments
- Freeze the suspicious payment change and verify through trusted contact details
Explanation
Correct Answer
D:Replying to the same email thread can reach the impostor. The response must subsequently be checked by confirming payment routing stays unchanged until the real supplier confirms authorization; otherwise the original exposure may persist.
Incorrect Answers
A:For email authentication spoofing, blocking based on display name would disrupt genuine notifications; here the narrower objective is choosing the immediate operational response in business email compromise, best addressed by freeze the suspicious payment change and verify through trusted contact details.
B:Normalizing this account into routine operations defeats its emergency purpose; that is suited to investigating misuse of break-glass account, whereas the business email compromise case requires freeze the suspicious payment change and verify through trusted contact details for choosing the immediate operational response.
C:The alternative concerns malicious email attachment: mailbox cleanup alone will not stop code already running; however, the described business email compromise situation calls for freeze the suspicious payment change and verify through trusted contact details.
Question 308
The working evidence for Windows process start includes this observation: Security event 4688 can record process creation when auditing is enabled. Which intervention is the best fit for the established finding?
- Enable appropriate process-creation auditing with command-line logging controls
- Collect failure events at source and forward them to central monitoring
- Enrich successful logon events with identity and asset context
- Preserve collector copies and open a tampering investigation
Explanation
Correct Answer
A:Logging must be balanced with access restrictions because command lines may expose sensitive data. Operational success is not assumed until a benign test process appears with expected ancestry and command-line detail, the relevant outcome for this response.
Incorrect Answers
B:Successful-logon records alone cannot reveal attacks that never authenticate; prioritizing that Windows failed logons mechanism would leave this Windows process start decision unresolved because enable appropriate process-creation auditing with command-line logging controls is the direct fit.
C:This relates to Windows successful logons: the suspiciousness depends on privileges, timing and post-login actions rather than success status; the Windows process start question instead requires choosing the immediate operational response, specifically enable appropriate process-creation auditing with command-line logging controls.
D:Deleting the latest alert does not recover the historical logging gap; that is suited to investigating Windows audit log cleared, whereas the Windows process start case requires enable appropriate process-creation auditing with command-line logging controls for choosing the immediate operational response.
Question 309
A process on a workstation uses an account different from the interactive user to access a server. Which observation most directly identifies the concern that needs investigation?
- An increasing queue age indicates delayed security-event visibility
- Security event 4688 can record process creation when auditing is enabled
- Security event 4648 records an attempted logon with explicit credentials
- Security event 1102 denotes a cleared Security audit log
Explanation
Correct Answer
C:It indicates explicit credential use and should be interpreted alongside target authentication results. The follow-up evidence is event 4648 subject, target-account and process fields with destination logs, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
A:For collector backlog monitoring, ingestion lag can hide urgent events even when the source is generating logs; here the narrower objective is recognizing the distinguishing signal in Windows explicit credentials, best addressed by security event 4648 records an attempted logon with explicit credentials.
B:The alternative concerns Windows process start: command-line inclusion depends on policy and provides richer detection context; however, the described Windows explicit credentials situation calls for security event 4648 records an attempted logon with explicit credentials.
D:This high-value administrative action can obscure earlier security evidence; that is suited to investigating Windows audit log cleared, whereas the Windows explicit credentials case requires security event 4648 records an attempted logon with explicit credentials for recognizing the distinguishing signal.
Question 310
The working evidence for scheduled task persistence includes this observation: A newly created scheduled task references an unusual executable path. Which intervention is the best fit for the established finding?
- Detect unapproved task definitions and investigate the registering process
- Monitor security-relevant autorun keys and assess new launch targets
- Escalate unauthorized membership and monitor subsequent privileged logons
- Correlate elevated process starts with approved mechanisms and suspicious parents
Explanation
Correct Answer
A:Deleting the running process is insufficient if the trigger remains installed. Operational success is not assumed until malicious registration tests alert and approved system tasks remain distinguishable, the relevant outcome for this response.
Incorrect Answers
B:Blocking all registry edits is infeasible and would not identify persistence intent; that is suited to investigating run key persistence, whereas the scheduled task persistence case requires detect unapproved task definitions and investigate the registering process for choosing the immediate operational response.
C:For domain admin group change, an account lock alone may not remove privilege granted to other identities; here the narrower objective is choosing the immediate operational response in scheduled task persistence, best addressed by detect unapproved task definitions and investigate the registering process.
D:Detecting only logon failures would miss abuse after authentication; this evidence or action is associated with privilege token misuse, whereas the case concerns scheduled task persistence and calls for detect unapproved task definitions and investigate the registering process.