ECCouncil 312-39 (Certified SOC Analyst) Practice Test 15

Question 140

To verify remediation of password spraying, the team reports taking this action: Block the malicious source or enforce risk-based authentication challenges. Which outcome should the analyst demand?

  1. No further distributed attempts and no suspicious successes for targeted accounts
  2. Sensitive service credentials are rotated and anomalous request patterns stop
  3. No repeat LSASS access and affected accounts show no attacker-controlled sessions
  4. No new encryption events and restored files pass integrity and access tests

Explanation

Correct Answer

A:

A quiet failed-login graph does not rule out an already obtained session. That verification specifically tests whether the intervention to block the malicious source or enforce risk-based authentication challenges corrected the issue rather than merely hiding an alert.

Incorrect Answers

B:

Credential rotation without investigating use of cracked passwords leaves residual risk; applied to this password spraying case, it addresses kerberoasting instead of the required step: no further distributed attempts and no suspicious successes for targeted accounts.

C:

The alternative concerns credential dumping: absence of the tool is not proof that stolen passwords or tokens are unusable; however, the described password spraying situation calls for no further distributed attempts and no suspicious successes for targeted accounts.

D:

Cleaning the initial host without checking shared data can conceal ongoing impact; that is suited to investigating ransomware encryption, whereas the password spraying case requires no further distributed attempts and no suspicious successes for targeted accounts for demonstrating that the remediation or control took effect.

Question 141

A responder investigating dormant-account access has corroborated this finding: A long-inactive account initiates a privileged successful session. What action belongs next in the approved workflow?

  1. Correlate dormant-account logons with recent provisioning or reactivation approvals
  2. Implement a per-user sliding-window correlation with explicit exclusions
  3. Monitor security-relevant autorun keys and assess new launch targets
  4. Block the suspicious session and move to phishing-resistant verification where available

Explanation

Correct Answer

A:

A successful password check does not establish that the old account remains authorized. For safe case progression, preserve the evidence and later verify approved reactivation is documented and unknown dormant sessions are investigated.

Incorrect Answers

B:

This relates to authentication failure window: a daily static tally misses rapid behavior and may overcount long periods; the dormant-account access question instead requires choosing the immediate operational response, specifically correlate dormant-account logons with recent provisioning or reactivation approvals.

C:

Blocking all registry edits is infeasible and would not identify persistence intent; that is suited to investigating run key persistence, whereas the dormant-account access case requires correlate dormant-account logons with recent provisioning or reactivation approvals for choosing the immediate operational response.

D:

Simply asking the user to approve another push would compound the attack; this evidence or action is associated with MFA fatigue attempts, whereas the case concerns dormant-account access and calls for correlate dormant-account logons with recent provisioning or reactivation approvals.

Question 142

Analysts confirm the following observation: Windows Security event 4625 reflects failed logon attempts. Supporting material includes: Security log event 4625 fields including logon type and source address. Which operational action addresses the issue most directly?

  1. Preserve collector copies and open a tampering investigation
  2. Collect failure events at source and forward them to central monitoring
  3. Enrich successful logon events with identity and asset context
  4. Enable required IIS logging fields and protect collected log data

Explanation

Correct Answer

B:

Successful-logon records alone cannot reveal attacks that never authenticate. The response must subsequently be checked by confirming synthetic bad-password attempts appear in the SIEM with expected host and user fields; otherwise the original exposure may persist.

Incorrect Answers

A:

The alternative concerns Windows audit log cleared: deleting the latest alert does not recover the historical logging gap; however, the described Windows failed logons situation calls for collect failure events at source and forward them to central monitoring.

C:

The suspiciousness depends on privileges, timing and post-login actions rather than success status; prioritizing that Windows successful logons mechanism would leave this Windows failed logons decision unresolved because collect failure events at source and forward them to central monitoring is the direct fit.

D:

The alternative concerns IIS request logging: missing URI query or user context can break an injection-detection use case; however, the described Windows failed logons situation calls for collect failure events at source and forward them to central monitoring.

Question 143

The first-line team is investigating forensic timeline. Its preliminary finding is: Multiple clock sources and filesystem time fields distort incident chronology. What corroborating material is most decisive?

  1. Write-blocker status, image acquisition log and source-destination hashes
  2. PCAP capture point, five-tuple, TCP stream and TLS visibility constraints
  3. Memory capture metadata, running-process inventory and active sockets
  4. Filesystem metadata, event logs and UTC-normalized network records

Explanation

Correct Answer

D:

Cross-artifact comparison can expose timestamp manipulation or clock error. Linking these records back to multiple clock sources and filesystem time fields distort incident chronology reduces reliance on an isolated indicator.

Incorrect Answers

A:

Acquisition integrity must be verified using suitable cryptographic hashes; that is suited to investigating disk forensic imaging, whereas the forensic timeline case requires filesystem metadata, event logs and UTC-normalized network records for independently corroborating the suspected behavior.

B:

Encryption and incomplete capture affect what can actually be concluded, which would be relevant to network packet evidence, but not the forensic timeline scenario that requires filesystem metadata, event logs and UTC-normalized network records.

C:

Live response documentation provides context for interpreting the dump; this evidence or action is associated with memory capture order, whereas the case concerns forensic timeline and calls for filesystem metadata, event logs and UTC-normalized network records.

Question 144

A high-confidence ransomware alert was detected quickly but isolation approvals stalled for ninety minutes. The team takes this action: Refine approvals and preauthorize safe containment for defined severities. Which check most directly verifies the intended outcome?

  1. Measured detection-to-containment time decreases in controlled exercises
  2. A shorter detection interval on replayed equivalent attack scenarios
  3. Both parties confirm execution of their assigned containment actions
  4. An acknowledged handoff with a named owner and response deadline
  5. Production precision and volume stay within agreed operating thresholds

Explanation

Correct Answer

A:

The metric must follow actual enforcement, not merely ticket creation or chat acknowledgment. The measure should be evaluated against the actual action, refine approvals and preauthorize safe containment for defined severities, rather than against ticket status.

Incorrect Answers

B:

MTTD improvement should be demonstrated on representative behavior and comparable measurements; that is suited to investigating mean time to detect, whereas the mean time to respond case requires measured detection-to-containment time decreases in controlled exercises for demonstrating that the remediation or control took effect.

C:

The alternative concerns hybrid SOC coordination: separate dashboards do not guarantee coordinated closure of a cross-boundary incident; however, the described mean time to respond situation calls for measured detection-to-containment time decreases in controlled exercises.

D:

For tier-one escalation, a ticket alone is not proof that the receiving team accepted time-sensitive responsibility; here the narrower objective is demonstrating that the remediation or control took effect in mean time to respond, best addressed by measured detection-to-containment time decreases in controlled exercises.

E:

For rule-change governance, successful deployment requires evidence of usable alerts, not just an enabled rule; here the narrower objective is demonstrating that the remediation or control took effect in mean time to respond, best addressed by measured detection-to-containment time decreases in controlled exercises.

Question 145

The working evidence for hunt peer baselines includes this observation: Peer-group differences explain some high-volume behavior patterns. Which intervention is the best fit for the established finding?

  1. Normalize and deduplicate intelligence before publishing to SIEM detections
  2. Form an ATT&CK-aligned hypothesis and query cross-host telemetry
  3. Record the coverage limitation and onboard necessary audit sources
  4. Build role-specific baselines and investigate deviations within the proper group

Explanation

Correct Answer

D:

A one-size-fits-all global rate misses context and drives false positives. For safe case progression, preserve the evidence and later verify test outliers are detected without flagging expected high-volume service traffic.

Incorrect Answers

A:

Directly pushing every feed entry can multiply noisy matches, which would be relevant to threat intelligence platform, but not the hunt peer baselines scenario that requires build role-specific baselines and investigate deviations within the proper group.

B:

This relates to hypothesis-driven hunt: searching random suspicious strings without a question rarely produces repeatable insight; the hunt peer baselines question instead requires choosing the immediate operational response, specifically build role-specific baselines and investigate deviations within the proper group.

C:

Closing the hypothesis as false would misstate investigative confidence; applied to this hunt peer baselines case, it addresses hunt data gap instead of the required step: build role-specific baselines and investigate deviations within the proper group.

Question 146

A sensitive configuration file is altered, but syslog contains no actor details. Which finding best distinguishes this activity from a routine operational change?

  1. An ephemeral journal configuration loses records across restarts
  2. auditd syscall records linked to configured file watches
  3. sudo authorization and command records reveal privilege elevation
  4. Unified Logging predicates identify process and event records on macOS

Explanation

Correct Answer

B:

Kernel audit rules can capture selected access and modification events with identity context. The follow-up evidence is auditd events joining syscall, path, user ID and process attributes, which helps separate the observed pattern from merely similar activity.

Incorrect Answers

A:

Volatile journal storage can be unsuitable when historical host events are required; that is suited to investigating systemd journal persistence, whereas the Linux auditd file access case requires auditd syscall records linked to configured file watches for recognizing the distinguishing signal.

C:

Privilege use can be permitted but becomes suspicious when context differs from approval; applied to this Linux auditd file access case, it addresses Linux sudo activity instead of the required step: auditd syscall records linked to configured file watches.

D:

The platform uses its own structured logging mechanism and privacy controls; this evidence or action is associated with macOS unified logging, whereas the case concerns Linux auditd file access and calls for auditd syscall records linked to configured file watches.

Question 147

The first-line team is investigating domain admin group change. Its preliminary finding is: Unexpected membership change grants high-impact directory privileges. What corroborating material is most decisive?

  1. Directory audit of member, group, actor and change ticket linkage
  2. Domain controller 4769 records and requestor host process lineage
  3. Task creation events, task XML and executable hash correlation
  4. Registry change telemetry with value data and modifying process

Explanation

Correct Answer

A:

Effective group membership and actor authorization determine the risk. This is particularly useful after the initial sign of unexpected membership change grants high-impact directory privileges; the two forms of evidence test different parts of the case.

Incorrect Answers

B:

Ticket request context and service names help avoid misreading normal delegation, which would be relevant to Kerberos ticket anomaly, but not the domain admin group change scenario that requires directory audit of member, group, actor and change ticket linkage.

C:

The alternative concerns scheduled task persistence: the registration identity and command path expose the mechanism; however, the described domain admin group change situation calls for directory audit of member, group, actor and change ticket linkage.

D:

The value payload and actor are needed beyond a generic registry-edit count; that is suited to investigating run key persistence, whereas the domain admin group change case requires directory audit of member, group, actor and change ticket linkage for independently corroborating the suspected behavior.

Question 148

The working hypothesis concerns Windows successful logons. The initial finding is: Windows Security event 4624 records a successful logon. Which evidence should investigators prioritize?

  1. Security log event 4625 fields including logon type and source address
  2. Event 1102 subject account and independent forwarded prior events
  3. Event 4648 subject, target-account and process fields with destination logs
  4. macOS log show or log stream output scoped to process and time
  5. Event 4624 logon type, authentication package and source host correlation
  6. Event 4688 creator and new process fields plus command-line audit policy

Explanation

Correct Answer

E:

A success record alone does not establish whether the session was authorized. The result can be compared with Windows Security event 4624 records a successful logon to verify that the suspected mechanism is actually present.

Incorrect Answers

A:

For Windows failed logons, correlating reason codes and origin reduces confusion with user typos or service failures; here the narrower objective is independently corroborating the suspected behavior in Windows successful logons, best addressed by event 4624 logon type, authentication package and source host correlation.

B:

Remote copies help establish activity even after on-host records have been deleted; applied to this Windows successful logons case, it addresses Windows audit log cleared instead of the required step: event 4624 logon type, authentication package and source host correlation.

C:

Pairing the initiating record with remote sessions provides better attribution; prioritizing that Windows explicit credentials mechanism would leave this Windows successful logons decision unresolved because event 4624 logon type, authentication package and source host correlation is the direct fit.

D:

Correct predicates filter the relevant subsystem without requiring Linux auth.log files; that is suited to investigating macOS unified logging, whereas the Windows successful logons case requires event 4624 logon type, authentication package and source host correlation for independently corroborating the suspected behavior.

F:

This relates to Windows process start: without process creation and command line collection the SIEM may lack the evidence; the Windows successful logons question instead requires independently corroborating the suspected behavior, specifically event 4624 logon type, authentication package and source host correlation.

Question 149

A PDF-themed archive delivered through email launches an unsigned executable on a workstation. What finding is the strongest distinguishing indicator for triage?

  1. An unexpected inbox rule or mailbox forwarding setting exports mail
  2. Malicious mail reaches multiple recipients with a common redirect destination
  3. Attachment extraction precedes unexpected executable launch
  4. A payment redirection request deviates from verified supplier instructions

Explanation

Correct Answer

C:

File handling plus process ancestry links the email to endpoint compromise. Confirmation should then examine message-ID, attachment hash, browser or extraction process and EDR telemetry; the signal is a triage lead, not a complete incident narrative.

Incorrect Answers

A:

For mail forwarding persistence, mailbox rules can maintain access without repeated interactive sign-ins; here the narrower objective is recognizing the distinguishing signal in malicious email attachment, best addressed by attachment extraction precedes unexpected executable launch.

B:

The alternative concerns credential-harvesting email campaign: a campaign-level response must account for all delivered copies; however, the described malicious email attachment situation calls for attachment extraction precedes unexpected executable launch.

D:

BEC may contain no malware and relies on impersonation or account compromise; this evidence or action is associated with business email compromise, whereas the case concerns malicious email attachment and calls for attachment extraction precedes unexpected executable launch.

Question 150

The working evidence for compromised privileged account includes this observation: Privilege abuse creates persistence and expands the incident beyond one user. Which intervention is the best fit for the established finding?

  1. Remove unauthorized methods and reset trusted authentication enrollment
  2. Disable or reset compromised credentials and revoke active sessions
  3. Rotate the affected secret and restrict principal privileges while preserving service continuity
  4. Revoke malicious grants, secure the administrator and investigate downstream changes
  5. Explicitly revoke relevant sessions or token grants and review consent

Explanation

Correct Answer

D:

Disabling the first account leaves attacker-created access paths otherwise intact. Operational success is not assumed until the privilege graph returns to approved state and suspicious sessions are terminated, the relevant outcome for this response.

Incorrect Answers

A:

Deleting one sign-in event does not eliminate the attacker's factor; applied to this compromised privileged account case, it addresses suspicious MFA enrollment instead of the required step: revoke malicious grants, secure the administrator and investigate downstream changes.

B:

For stolen user password, changing only the password may not immediately invalidate all existing tokens; here the narrower objective is choosing the immediate operational response in compromised privileged account, best addressed by revoke malicious grants, secure the administrator and investigate downstream changes.

C:

This relates to service principal exposure: resetting a developer's account does not invalidate the exposed app credential; the compromised privileged account question instead requires choosing the immediate operational response, specifically revoke malicious grants, secure the administrator and investigate downstream changes.

E:

Relying solely on credential rotation may leave bearer access alive; prioritizing that refresh token theft mechanism would leave this compromised privileged account decision unresolved because revoke malicious grants, secure the administrator and investigate downstream changes is the direct fit.

Certified SOC Analyst (312-39) Practice Tests