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

Question 730

EDR reports disagreement between kernel module inventory and ordinary process listings after a high-privilege compromise. Which evidence collection choice best supports this investigation?

  1. File-change telemetry, process lineage and share write access
  2. Trusted offline disk or memory analysis with module checks
  3. Backup restore test, access audit and snapshot integrity results
  4. Endpoint execution chain and east-west connection logs
  5. Container runtime process details and outbound pool connections

Explanation

Correct Answer

B:

Independent acquisition helps test whether kernel data structures were manipulated; this is the relevant corroboration mechanism for Kernel rootkit suspected on endpoint given “EDR reports disagreement between kernel module inventory and ordinary process listings after a high-privilege compromise”.

Incorrect Answers

A:

For corroboration in Kernel rootkit suspected on endpoint, Active ransomware encryption response is a different mechanism: evidence identifies executing processes and reachable data paths; here, independent acquisition helps test whether kernel data structures were manipulated.

C:

For corroboration in Kernel rootkit suspected on endpoint, Ransomware backup recovery selection is a different mechanism: recovery requires verified readable data and confidence in the repository; here, independent acquisition helps test whether kernel data structures were manipulated.

D:

The choice is relevant to Worm-like propagation across segments, where the propagation path connects source hosts to newly infected destinations; for corroboration in Kernel rootkit suspected on endpoint, independent acquisition helps test whether kernel data structures were manipulated.

E:

For corroboration in Kernel rootkit suspected on endpoint, Cryptojacking in production cluster is a different mechanism: execution context differentiates mining from approved high-CPU workloads; here, independent acquisition helps test whether kernel data structures were manipulated.

Question 731

An alert rule counts five failures every hour but misses twenty failures occurring across an hour boundary. How should the analyst classify the activity at this stage?

  1. Fixed-bucket versus sliding-window detection gap
  2. Untested detection-content deployment
  3. Ordered multi-event detection
  4. Improper entity peer grouping

Explanation

Correct Answer

A:

Given “An alert rule counts five failures every hour but misses twenty failures occurring across an hour boundary”, attacks spanning adjacent time buckets can evade static per-hour thresholds; that best addresses classification in Sliding-window aggregation error.

Incorrect Answers

B:

For the alternative Detection-as-code regression situation, version changes can break queries or field dependencies without obvious application errors; by contrast, for Sliding-window aggregation error classification, attacks spanning adjacent time buckets can evade static per-hour thresholds.

C:

In Multi-stage attack sequence correlation, temporal correlation across delivery, execution and network activity provides greater confidence than isolated signatures; the reported Sliding-window aggregation error case calls for a different classification conclusion because attacks spanning adjacent time buckets can evade static per-hour thresholds.

D:

For the alternative Peer-group baseline mismatch situation, workload roles have different normal traffic volumes and should not share one generic threshold; by contrast, for Sliding-window aggregation error classification, attacks spanning adjacent time buckets can evade static per-hour thresholds.

Question 732

An alert is created before the asset inventory labels the targeted host as a payment-processing system. What monitoring improvement would best help detect recurrence?

  1. Alert when critical sources miss their expected event cadence
  2. Monitor hot-age and archive restoration success
  3. Alert on stale asset and identity enrichment feeds
  4. Track unmapped or ambiguous principal rates by source

Explanation

Correct Answer

C:

The Context enrichment delay evidence “An alert is created before the asset inventory labels the targeted host as a payment-processing system” is decisive for ongoing detection improvement because data-quality monitoring maintains the trustworthiness of risk scoring.

Incorrect Answers

A:

For the alternative SIEM ingestion freshness gap situation, log-source health is itself a detection use case requiring asset baselines; by contrast, for Context enrichment delay ongoing detection improvement, data-quality monitoring maintains the trustworthiness of risk scoring.

B:

In SIEM hot-search retention mismatch, age and restore metrics prevent analysts from mistaking search limits for true absence; the reported Context enrichment delay case calls for a different ongoing detection improvement conclusion because data-quality monitoring maintains the trustworthiness of risk scoring.

D:

In Cross-vendor user identifier normalization, mapping quality predicts missed joins better than raw ingestion volume; the reported Context enrichment delay case calls for a different ongoing detection improvement conclusion because data-quality monitoring maintains the trustworthiness of risk scoring.

Question 733

A signed Windows utility loads a DLL from a user's temporary download directory and contacts a novel host. What follow-up analysis most effectively distinguishes this case?

  1. Decode safely and correlate parent process with network events
  2. Inspect the caller binary, privileges and memory-access context
  3. Map the script origin and compare host agents' health
  4. Compare loaded module hash against approved software inventory
  5. Check creation account and file origin across affected profiles

Explanation

Correct Answer

D:

A suspicious library path can be evaluated without flagging every rundll32 invocation; this is the relevant scope analysis mechanism for Rundll32 unusual DLL loading given “A signed Windows utility loads a DLL from a user's temporary download directory and contacts a novel host”.

Incorrect Answers

A:

In Encoded PowerShell execution chain, legitimate configuration scripts and hostile downloaders can share command flags; the reported Rundll32 unusual DLL loading case calls for a different scope analysis conclusion because a suspicious library path can be evaluated without flagging every rundll32 invocation.

B:

For the alternative Credential store memory access situation, signed security tools may inspect protected processes for legitimate diagnostics; by contrast, for Rundll32 unusual DLL loading scope analysis, a suspicious library path can be evaluated without flagging every rundll32 invocation.

C:

In Defender telemetry suppression attempt, a management rollout must be distinguished from unauthorized tampering; the reported Rundll32 unusual DLL loading case calls for a different scope analysis conclusion because a suspicious library path can be evaluated without flagging every rundll32 invocation.

E:

In Persistence through registry Run key, file history identifies whether the change came from an installer or adversary; the reported Rundll32 unusual DLL loading case calls for a different scope analysis conclusion because a suspicious library path can be evaluated without flagging every rundll32 invocation.

Question 734

A single workstation triggers a phishing-open alert, then script execution and privileged outbound access within minutes. What record is most useful for confirming this specific pattern?

  1. Raw event timestamps and rule aggregation window settings
  2. Rule exception filters and historical matched-event samples
  3. Shared host identity and chronological events across sensors
  4. Asset role labels alongside historical transfer distributions

Explanation

Correct Answer

C:

Given “A single workstation triggers a phishing-open alert, then script execution and privileged outbound access within minutes”, stable entity joins and event time establish whether signals form one progression; that best addresses corroboration in Multi-stage attack sequence correlation.

Incorrect Answers

A:

That option fits Sliding-window aggregation error since the data reveals whether a cluster was split across reporting boundaries; it does not fit the Multi-stage attack sequence correlation corroboration scenario, where stable entity joins and event time establish whether signals form one progression.

B:

This option addresses Overbroad allowlist suppression because reviewing suppressed events shows which maliciously relevant contexts disappear; the Multi-stage attack sequence correlation corroboration question instead turns on the fact that stable entity joins and event time establish whether signals form one progression.

D:

This option addresses Peer-group baseline mismatch because separating backup servers from office endpoints exposes why the baseline is distorted; the Multi-stage attack sequence correlation corroboration question instead turns on the fact that stable entity joins and event time establish whether signals form one progression.

Question 735

Security staff discover that a token-signing key may have been extracted from an identity federation service. The analyst has not yet established malicious intent or downstream impact. Which interpretive boundary is most relevant to this situation?

  1. Deleting a commit or file does not invalidate a copied secret
  2. Removing a group membership does not undo actions already completed
  3. A password reset may leave certain already-issued tokens active temporarily
  4. A newly registered factor is not necessarily fraudulent
  5. Password resets alone do not repair a compromised token-signing trust

Explanation

Correct Answer

E:

The Compromised federation signing key evidence “Security staff discover that a token-signing key may have been extracted from an identity federation service” is decisive for interpretation limit because the fundamental trust anchor needs rotation and relying-party coordination.

Incorrect Answers

A:

This option addresses Exposed cloud API credential because the credential remains usable until explicitly revoked or expired; the Compromised federation signing key interpretation limit question instead turns on the fact that the fundamental trust anchor needs rotation and relying-party coordination.

B:

That option fits Privilege escalation via group membership since separate forensic review is required for privileged activity during the exposure window; it does not fit the Compromised federation signing key interpretation limit scenario, where the fundamental trust anchor needs rotation and relying-party coordination.

C:

This option addresses Employee account takeover because revocation and token validity must be considered explicitly; the Compromised federation signing key interpretation limit question instead turns on the fact that the fundamental trust anchor needs rotation and relying-party coordination.

D:

That option fits Unauthorized MFA factor registration since legitimate device replacement is common but must be verified for high-risk users; it does not fit the Compromised federation signing key interpretation limit scenario, where the fundamental trust anchor needs rotation and relying-party coordination.

Question 736

Employees scanned QR images in office notices and reached an external login replica absent from email URL scanners. Which artifact provides the strongest corroborating detail?

  1. Mail trace, click telemetry and identity-provider sign-in results
  2. Consent audit, app service principal and token access records
  3. QR destination decoding and web access logs
  4. Mail headers, mailbox access logs and payment request trail
  5. Email attachment hash, process tree and file creation events

Explanation

Correct Answer

C:

In the QR-code phishing landing page case, inspecting the encoded URL establishes where users were directed; the observation “Employees scanned QR images in office notices and reached an external login replica absent from email URL scanners” makes this corroboration choice the fitting one.

Incorrect Answers

A:

For corroboration in QR-code phishing landing page, Targeted phishing mail delivery is a different mechanism: delivery and user interaction reveal who was exposed and whether tokens were issued; here, inspecting the encoded URL establishes where users were directed.

B:

The choice is relevant to Malicious OAuth app consent response, where the grant and resource usage show which access exists and was exercised; for corroboration in QR-code phishing landing page, inspecting the encoded URL establishes where users were directed.

D:

The choice is relevant to Business email compromise wire request, where identity activity and message history establish the attack and potential financial consequence; for corroboration in QR-code phishing landing page, inspecting the encoded URL establishes where users were directed.

E:

For corroboration in QR-code phishing landing page, Malicious email attachment execution is a different mechanism: artifact lineage links the message to on-host behavior; here, inspecting the encoded URL establishes where users were directed.

Question 737

A low-confidence endpoint detection fires on a server containing sensitive identity keys and remains unassigned. The analyst has not yet established malicious intent or downstream impact. Which caveat most directly affects assessment of the evidence?

  1. Model confidence is not equivalent to business risk
  2. A detector title is not an incident narrative
  3. Two sensors can report different severity without one being broken
  4. Same host and time alone do not prove alerts are duplicates

Explanation

Correct Answer

A:

The Low-confidence alert with crown-jewel impact evidence “A low-confidence endpoint detection fires on a server containing sensitive identity keys and remains unassigned” is decisive for interpretation limit because a rare severe outcome can justify attention despite weak preliminary signals.

Incorrect Answers

B:

For interpretation limit in Low-confidence alert with crown-jewel impact, Alert escalation missing supporting evidence is a different mechanism: the downstream team needs supporting observations and uncertainty, not just a label; here, a rare severe outcome can justify attention despite weak preliminary signals.

C:

The choice is relevant to Conflicting alert severity from two sources, where they may measure attempt confidence versus observed endpoint consequence; for interpretation limit in Low-confidence alert with crown-jewel impact, a rare severe outcome can justify attention despite weak preliminary signals.

D:

For interpretation limit in Low-confidence alert with crown-jewel impact, Repeated duplicate detection tickets is a different mechanism: independent attack steps may deserve separate conclusions within a shared case; here, a rare severe outcome can justify attention despite weak preliminary signals.

Question 738

During an active compromise, the on-call analyst and infrastructure lead disagree over who may shut down a production service. What focused analysis should the analyst perform next?

  1. Assess affected assets, attacker progression and potential impact
  2. Run a tabletop to exercise emergency isolation decisions
  3. Reconcile endpoint identity to hosting and application records
  4. Verify responder identities using known alternate contact paths

Explanation

Correct Answer

B:

In the Incident response authority chart case, scenario testing exposes missing approvals and unavailable delegates; the observation “During an active compromise, the on-call analyst and infrastructure lead disagree over who may shut down a production service” makes this scope analysis choice the fitting one.

Incorrect Answers

A:

This option addresses Incident declaration threshold because a unified assessment distinguishes an active campaign from isolated benign matches; the Incident response authority chart scope analysis question instead turns on the fact that scenario testing exposes missing approvals and unavailable delegates.

C:

This option addresses Incident readiness inventory because hostname ambiguity can delay targeted action or harm the wrong system; the Incident response authority chart scope analysis question instead turns on the fact that scenario testing exposes missing approvals and unavailable delegates.

D:

That option fits Out-of-band crisis communications since channel trust must be established before sharing containment instructions; it does not fit the Incident response authority chart scope analysis scenario, where scenario testing exposes missing approvals and unavailable delegates.

Question 739

An alert rule counts five failures every hour but misses twenty failures occurring across an hour boundary. The finding has been corroborated and the response team has authorization to act. Which targeted action should the authorized response team prioritize?

  1. Implement appropriate rolling-window correlation with throttling
  2. Apply role-aware thresholds without exempting backup servers entirely
  3. Roll back the faulty version and repair the field dependency
  4. Replace the subnet exemption with actor-and-task-scoped conditions
  5. Escalate the complete attack chain as one incident

Explanation

Correct Answer

A:

The Sliding-window aggregation error evidence “An alert rule counts five failures every hour but misses twenty failures occurring across an hour boundary” is decisive for response decision because window design catches boundary-spanning activity while limiting alert storms.

Incorrect Answers

B:

That option fits Peer-group baseline mismatch since unusual backup traffic can still be malicious and deserves coverage; it does not fit the Sliding-window aggregation error response decision scenario, where window design catches boundary-spanning activity while limiting alert storms.

C:

This option addresses Detection-as-code regression because restoring previous logic recovers coverage while a corrected query is tested; the Sliding-window aggregation error response decision question instead turns on the fact that window design catches boundary-spanning activity while limiting alert storms.

D:

That option fits Overbroad allowlist suppression since narrow suppressions preserve coverage outside the approved maintenance context; it does not fit the Sliding-window aggregation error response decision scenario, where window design catches boundary-spanning activity while limiting alert storms.

E:

This option addresses Multi-stage attack sequence correlation because unified case context prevents disjoint alerts from obscuring campaign progression; the Sliding-window aggregation error response decision question instead turns on the fact that window design catches boundary-spanning activity while limiting alert storms.

Question 740

Firewall events appear to occur five minutes after the corresponding endpoint alerts even though packet traces show the reverse order. Which source would most directly corroborate the observation?

  1. Packet capture showing UDP 514 log payloads in clear text
  2. Raw event IDs and collector-route metadata
  3. Raw sample versus parsed field mapping and parser version
  4. Device NTP status with raw timestamp and timezone fields

Explanation

Correct Answer

D:

For corroboration in Clock skew across security sensors, source clock offsets and timezone parsing explain conflicting event order; this applies to the reported “Firewall events appear to occur five minutes after the corresponding endpoint alerts even though packet traces show the reverse order”.

Incorrect Answers

A:

That option fits Secure syslog transport mismatch since the wire trace confirms both transport choice and exposure of event content; it does not fit the Clock skew across security sensors corroboration scenario, where source clock offsets and timezone parsing explain conflicting event order.

B:

This option addresses Duplicate event ingestion because matching identifiers reveal whether observations are true repeats or pipeline duplicates; the Clock skew across security sensors corroboration question instead turns on the fact that source clock offsets and timezone parsing explain conflicting event order.

C:

That option fits SIEM parser field loss since direct comparison identifies which structured field no longer matches source syntax; it does not fit the Clock skew across security sensors corroboration scenario, where source clock offsets and timezone parsing explain conflicting event order.

Certified SOC Analyst (312-39) Practice Tests