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

Question 820

A finance clerk receives an apparently internal urgent wire request after an executive mailbox shows anomalous sign-ins. What evidence should be obtained to validate the suspected mechanism?

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

Explanation

Correct Answer

C:

The Business email compromise wire request evidence “A finance clerk receives an apparently internal urgent wire request after an executive mailbox shows anomalous sign-ins” is decisive for corroboration because identity activity and message history establish the attack and potential financial consequence.

Incorrect Answers

A:

For corroboration in Business email compromise wire request, Malicious email attachment execution is a different mechanism: artifact lineage links the message to on-host behavior; here, identity activity and message history establish the attack and potential financial consequence.

B:

The choice is relevant to Targeted phishing mail delivery, where delivery and user interaction reveal who was exposed and whether tokens were issued; for corroboration in Business email compromise wire request, identity activity and message history establish the attack and potential financial consequence.

D:

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

Question 821

A hash blocklist stops one malicious sample but a recompilation evades matching despite unchanged attacker behavior. The finding has been corroborated and the response team has authorization to act. Which targeted action should the authorized response team prioritize?

  1. Normalize the shared objects into the intelligence platform
  2. Mark the claim unconfirmed and avoid disruptive blocking
  3. Merge duplicate observables without discarding source histories
  4. Build behavior rules alongside hash-based detections
  5. Configure authorized collection polling with safe rate limits
  6. Expire outdated block rules unless renewed by evidence

Explanation

Correct Answer

D:

In the Malware hash IoC specificity case, layered detection catches payload variants without relying on one checksum; the observation “A hash blocklist stops one malicious sample but a recompilation evades matching despite unchanged attacker behavior” makes this response decision choice the fitting one.

Incorrect Answers

A:

For the alternative STIX structured intelligence exchange situation, structured import preserves entities for enrichment and correlation; by contrast, for Malware hash IoC specificity response decision, layered detection catches payload variants without relying on one checksum.

B:

In Intelligence source circular reporting, unverified stories should not trigger high-impact controls without local risk evidence; the reported Malware hash IoC specificity case calls for a different response decision conclusion because layered detection catches payload variants without relying on one checksum.

C:

For the alternative Threat intelligence platform deduplication situation, preserving attribution supports later re-evaluation and false-positive handling; by contrast, for Malware hash IoC specificity response decision, layered detection catches payload variants without relying on one checksum.

E:

For the alternative TAXII intelligence distribution situation, managed collection access supports reliable feed updates with controlled credentials; by contrast, for Malware hash IoC specificity response decision, layered detection catches payload variants without relying on one checksum.

F:

In Threat feed confidence decay, time-limited enforcement avoids penalizing newly legitimate tenants; the reported Malware hash IoC specificity case calls for a different response decision conclusion because layered detection catches payload variants without relying on one checksum.

Question 822

The SIEM counts two identical firewall denies for each packet after administrators enable a second collector path. Which interpretation best fits the observed evidence?

  1. Multi-path duplicate logging
  2. Insufficient protected log retention
  3. Log forwarder buffering backlog
  4. Unprotected log transport
  5. Security telemetry time synchronization drift

Explanation

Correct Answer

A:

The Duplicate event ingestion evidence “The SIEM counts two identical firewall denies for each packet after administrators enable a second collector path” is decisive for classification because two feeds can deliver the same source event twice and inflate detections and costs.

Incorrect Answers

B:

For classification in Duplicate event ingestion, Immutable log retention requirements is a different mechanism: accessible archives need retention and tamper controls appropriate to the investigation period; here, two feeds can deliver the same source event twice and inflate detections and costs.

C:

The choice is relevant to Forwarder queue saturation, where agents can queue events locally when collectors are temporarily unreachable; for classification in Duplicate event ingestion, two feeds can deliver the same source event twice and inflate detections and costs.

D:

For classification in Duplicate event ingestion, Secure syslog transport mismatch is a different mechanism: plain UDP syslog lacks transport confidentiality and native reliable delivery guarantees; here, two feeds can deliver the same source event twice and inflate detections and costs.

E:

The choice is relevant to Clock skew across security sensors, where unsynchronized source clocks can invert an investigation timeline without changing actual causality; for classification in Duplicate event ingestion, two feeds can deliver the same source event twice and inflate detections and costs.

Question 823

One firewall records jsmith while the identity provider records a full principal name and correlation fails to join their events. What security condition most directly explains the pattern?

  1. Conflicting host identity resolution
  2. Identity entity-normalization mismatch
  3. Late asset-context enrichment
  4. Missing SIEM data-source heartbeat

Explanation

Correct Answer

B:

Given “One firewall records jsmith while the identity provider records a full principal name and correlation fails to join their events”, different identifier representations can prevent related events from being grouped into one actor; that best addresses classification in Cross-vendor user identifier normalization.

Incorrect Answers

A:

That option fits Cross-source entity duplication since device renaming and transient addresses can split one asset into separate investigation entities; it does not fit the Cross-vendor user identifier normalization classification scenario, where different identifier representations can prevent related events from being grouped into one actor.

C:

That option fits Context enrichment delay since detection ranking can be wrong when criticality metadata is unavailable at alert creation; it does not fit the Cross-vendor user identifier normalization classification scenario, where different identifier representations can prevent related events from being grouped into one actor.

D:

This option addresses SIEM ingestion freshness gap because a sudden source silence can disable detections even when the sensor continues operating; the Cross-vendor user identifier normalization classification question instead turns on the fact that different identifier representations can prevent related events from being grouped into one actor.

Question 824

A business application uploads an unusually large archive from a low-volume user account to an external bucket. Which investigative step would most directly establish the relevant scope?

  1. Reconstruct matched HTTP request from edge to application
  2. Check source records and approved integration destination list
  3. Correlate role grant with the supporting session and approval
  4. Group invalid-token requests by client fingerprint and resource
  5. Inspect the endpoint's source file and child command tree

Explanation

Correct Answer

B:

Business-approved ETL jobs must be distinguished from an illicit export; this is the relevant scope analysis mechanism for Massive object-storage upload through web app given “A business application uploads an unusually large archive from a low-volume user account to an external bucket”.

Incorrect Answers

A:

The choice is relevant to WAF bypass with origin success, where following the trace identifies the vulnerable parameter and whether an operation completed; for scope analysis in Massive object-storage upload through web app, business-approved ETL jobs must be distinguished from an illicit export.

C:

The choice is relevant to Unexpected web administrative role assignment, where linking access to an authorized ticket separates legitimate support from abuse; for scope analysis in Massive object-storage upload through web app, business-approved ETL jobs must be distinguished from an illicit export.

D:

For scope analysis in Massive object-storage upload through web app, API bearer-token guessing is a different mechanism: shared automation characteristics matter even when source IPs rotate; here, business-approved ETL jobs must be distinguished from an illicit export.

E:

The choice is relevant to Web-shell request and process correlation, where file provenance and execution output establish the suspected web shell's capabilities; for scope analysis in Massive object-storage upload through web app, business-approved ETL jobs must be distinguished from an illicit export.

Question 825

A malware outbreak requires specialist reverse engineering but the response plan lacks current contact and authorization for the retained firm. Which evidence collection choice best supports this investigation?

  1. Approved incident roles, escalation policy and service ownership
  2. Linked event timeline and incident severity criteria
  3. Active retainer agreement, scope and escalation contact verification
  4. Preapproved external bridge details and responder contact list

Explanation

Correct Answer

C:

The Third-party incident retainer activation evidence “A malware outbreak requires specialist reverse engineering but the response plan lacks current contact and authorization for the retained firm” is decisive for corroboration because contract terms define assistance level, notification requirements and access limits.

Incorrect Answers

A:

For the alternative Incident response authority chart situation, the policy establishes who can authorize high-impact containment; by contrast, for Third-party incident retainer activation corroboration, contract terms define assistance level, notification requirements and access limits.

B:

In Incident declaration threshold, the aggregated evidence should be evaluated against defined declaration triggers; the reported Third-party incident retainer activation case calls for a different corroboration conclusion because contract terms define assistance level, notification requirements and access limits.

D:

In Out-of-band crisis communications, a separate trusted channel remains reachable during identity system isolation; the reported Third-party incident retainer activation case calls for a different corroboration conclusion because contract terms define assistance level, notification requirements and access limits.

Question 826

A storage service produces security-relevant operation logs locally, but the SOC's Log Analytics workspace receives none. Which scoping query or comparison best tests the working hypothesis?

  1. Validate KQL against the workspace's actual tables and fields
  2. Group recurring findings by account, resource and control
  3. Filter events by resource, actor and account around the change
  4. Pivot from finding to CloudTrail and configuration history
  5. Compare source activity against table arrival and transformation rules

Explanation

Correct Answer

E:

For scope analysis in Azure Monitor diagnostic data routing, the test identifies missing categories or rejected schema mappings; this applies to the reported “A storage service produces security-relevant operation logs locally, but the SOC's Log Analytics workspace receives none”.

Incorrect Answers

A:

For the alternative Microsoft Sentinel analytic rule situation, data connector configuration determines which logs can participate in correlation; by contrast, for Azure Monitor diagnostic data routing scope analysis, the test identifies missing categories or rejected schema mappings.

B:

In AWS Security Hub finding consolidation, deduplication and enrichment support enterprise-level prioritization; the reported Azure Monitor diagnostic data routing case calls for a different scope analysis conclusion because the test identifies missing categories or rejected schema mappings.

C:

For the alternative AWS CloudTrail API activity situation, focused API history helps reconstruct the relevant sequence; by contrast, for Azure Monitor diagnostic data routing scope analysis, the test identifies missing categories or rejected schema mappings.

D:

In AWS GuardDuty threat finding, original API records are needed to reconstruct exact changes and consequences; the reported Azure Monitor diagnostic data routing case calls for a different scope analysis conclusion because the test identifies missing categories or rejected schema mappings.

Question 827

A nightly backup identity unexpectedly reads payroll data from a service it has never used. Which source would most directly corroborate the observation?

  1. Policy-change audit and file-share access chronology
  2. Application identity sign-ins and resource access audit
  3. Endpoint DLP file labels and removable-volume write events
  4. Cloud or directory role-assignment audit with actor and scope

Explanation

Correct Answer

B:

Given “A nightly backup identity unexpectedly reads payroll data from a service it has never used”, token subject and target resource reveal where the automated principal operated; that best addresses corroboration in Service principal unusual resource access.

Incorrect Answers

A:

This option addresses SIEM audit policy tampering because the sequence ties reduced visibility to a later high-impact operation; the Service principal unusual resource access corroboration question instead turns on the fact that token subject and target resource reveal where the automated principal operated.

C:

This option addresses DLP alert for removable media transfer because classification and device IDs show the material and destination of the copies; the Service principal unusual resource access corroboration question instead turns on the fact that token subject and target resource reveal where the automated principal operated.

D:

That option fits Privileged identity rare administrative action since role change records show precisely which permission was delegated and at what level; it does not fit the Service principal unusual resource access corroboration scenario, where token subject and target resource reveal where the automated principal operated.

Question 828

Critical incidents appear within target on an overall dashboard but several have exceeded the escalation SLA. How should the analyst classify the activity at this stage?

  1. Missing mean-time-to-detect reporting
  2. SOC alert-load concentration analysis
  3. Misleading source coverage visualization
  4. Ingestion-driven apparent threat increase
  5. Severity-blended response reporting

Explanation

Correct Answer

E:

For classification in SLA breach trend by incident tier, averages across low and critical priorities can conceal unacceptable delays for serious incidents; this applies to the reported “Critical incidents appear within target on an overall dashboard but several have exceeded the escalation SLA”.

Incorrect Answers

A:

The choice is relevant to Incident detection latency dashboard, where handling duration starts after an alert, whereas detection latency measures delay from incident onset; for classification in SLA breach trend by incident tier, averages across low and critical priorities can conceal unacceptable delays for serious incidents.

B:

For classification in SLA breach trend by incident tier, Noisy use-case Pareto dashboard is a different mechanism: rule-level workload and outcome charts identify candidates for targeted tuning; here, averages across low and critical priorities can conceal unacceptable delays for serious incidents.

C:

The choice is relevant to SOC data-source coverage dashboard, where a rule-success chart can look healthy despite unmonitored critical assets; for classification in SLA breach trend by incident tier, averages across low and critical priorities can conceal unacceptable delays for serious incidents.

D:

For classification in SLA breach trend by incident tier, Threat trend comparison without normalization is a different mechanism: adding sensors can increase observed alerts without any change in true attacker activity; here, averages across low and critical priorities can conceal unacceptable delays for serious incidents.

Question 829

A detection rule generates thousands of alerts but nearly all are closed as expected administration activity. What evidence should be obtained to validate the suspected mechanism?

  1. Current playbook revisions and the two case timelines
  2. Detection and containment timestamps for confirmed cases
  3. Asset inventory criticality and the detection evidence
  4. Disposition codes and supporting false-positive examples
  5. Original alert export with source and event timestamps

Explanation

Correct Answer

D:

Documented closures show which benign behaviors are causing the unwanted matches; this is the relevant corroboration mechanism for SOC detection quality governance given “A detection rule generates thousands of alerts but nearly all are closed as expected administration activity”.

Incorrect Answers

A:

The choice is relevant to SOC runbook decision ambiguity, where comparing written guidance with actual actions pinpoints the ambiguous decision branch; for corroboration in SOC detection quality governance, documented closures show which benign behaviors are causing the unwanted matches.

B:

For corroboration in SOC detection quality governance, SOC management performance metric is a different mechanism: verified incident milestones support meaningful measures of operational effectiveness; here, documented closures show which benign behaviors are causing the unwanted matches.

C:

The choice is relevant to Alert severity versus priority, where business ownership and supporting telemetry are necessary to justify an urgency change; for corroboration in SOC detection quality governance, documented closures show which benign behaviors are causing the unwanted matches.

E:

The choice is relevant to SOC case evidence preservation, where immutable source context lets another analyst reproduce the investigation and distinguish collection times; for corroboration in SOC detection quality governance, documented closures show which benign behaviors are causing the unwanted matches.

Question 830

A new user Run-key value points to an executable in a roaming profile and starts after every interactive sign-in. Which technical explanation is most defensible from the evidence?

  1. Suspicious interpreter behavior correlation
  2. Potential credential dumping chain
  3. Coordinated defense-evasion configuration change
  4. Registry-based user persistence

Explanation

Correct Answer

D:

An autostart entry launches code when the affected account signs in; this is the relevant classification mechanism for Persistence through registry Run key given “A new user Run-key value points to an executable in a roaming profile and starts after every interactive sign-in”.

Incorrect Answers

A:

For the alternative Encoded PowerShell execution chain situation, an encoded command with related egress warrants deeper review than the flag alone; by contrast, for Persistence through registry Run key classification, an autostart entry launches code when the affected account signs in.

B:

In Credential store memory access, sensitive-process access can precede extraction of authentication material when the caller is unauthorized; the reported Persistence through registry Run key case calls for a different classification conclusion because an autostart entry launches code when the affected account signs in.

C:

For the alternative Defender telemetry suppression attempt situation, telemetry disappearing after administrative modifications may signal attackers disabling security controls; by contrast, for Persistence through registry Run key classification, an autostart entry launches code when the affected account signs in.

Certified SOC Analyst (312-39) Practice Tests