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

Question 950

A service account runs unusual export queries against confidential tables outside its normal batch window. What evidence should be obtained to validate the suspected mechanism?

  1. Apache access log URI, client, status and user agent
  2. IIS status, substatus, time-taken and URI fields
  3. API gateway identity result, route and token validation reason
  4. Database audit principal, object, statement and source session

Explanation

Correct Answer

D:

For corroboration in Database privileged query audit, execution context distinguishes authorized exports from suspicious account misuse; this applies to the reported “A service account runs unusual export queries against confidential tables outside its normal batch window”.

Incorrect Answers

A:

That option fits Apache path enumeration logs since those fields show which paths were tried and which requests succeeded; it does not fit the Database privileged query audit corroboration scenario, where execution context distinguishes authorized exports from suspicious account misuse.

B:

This option addresses IIS request diagnostics because substatus and affected paths narrow the failure mode beyond a top-level 500 count; the Database privileged query audit corroboration question instead turns on the fact that execution context distinguishes authorized exports from suspicious account misuse.

C:

That option fits API gateway authentication logs since auth failure codes help distinguish expired tokens from missing authorization scope; it does not fit the Database privileged query audit corroboration scenario, where execution context distinguishes authorized exports from suspicious account misuse.

Question 951

An incident begins as a single infected laptop but investigators discover the same command channel on domain controllers. What follow-up analysis most effectively distinguishes this case?

  1. Verify the received image digest against the acquisition record
  2. Map new evidence to business services and privilege boundaries
  3. Review dependency and sequencing of proposed containment steps
  4. Separate established observations from hypotheses and pending checks

Explanation

Correct Answer

B:

Given “An incident begins as a single infected laptop but investigators discover the same command channel on domain controllers”, updated scope changes containment and notification needs; that best addresses scope analysis in Incident severity change during response.

Incorrect Answers

A:

That option fits Evidence transfer between response teams since matching hashes support bitwise consistency across the transfer; it does not fit the Incident severity change during response scope analysis scenario, where updated scope changes containment and notification needs.

C:

That option fits Incident commander coordination gap since some operations must precede others to preserve access and business continuity; it does not fit the Incident severity change during response scope analysis scenario, where updated scope changes containment and notification needs.

D:

This option addresses Public incident communications control because an uncertainty-aware briefing avoids exaggerating or minimizing impact; the Incident severity change during response scope analysis question instead turns on the fact that updated scope changes containment and notification needs.

Question 952

A hunter needs to list running processes and autorun entries across a controlled endpoint fleet. Which interpretation best fits the observed evidence?

  1. OSQuery structured endpoint enumeration
  2. YARA signature-based artifact matching
  3. Sigma generic log-detection rule
  4. Zeek network metadata hunting

Explanation

Correct Answer

A:

The OSQuery endpoint state hunt evidence “A hunter needs to list running processes and autorun entries across a controlled endpoint fleet” is decisive for classification because SQL-like queries expose operating-system state for fleet investigation.

Incorrect Answers

B:

That option fits YARA rule string matching since YARA combines textual or hexadecimal patterns with conditional logic to identify files or memory content; it does not fit the OSQuery endpoint state hunt classification scenario, where SQL-like queries expose operating-system state for fleet investigation.

C:

This option addresses Sigma analytic rule portability because sigma expresses event selection and conditions independent of a particular SIEM's query syntax; the OSQuery endpoint state hunt classification question instead turns on the fact that SQL-like queries expose operating-system state for fleet investigation.

D:

That option fits Threat hunt with Zeek connection logs since connection logs summarize sessions and protocol observations without requiring full payload storage; it does not fit the OSQuery endpoint state hunt classification scenario, where SQL-like queries expose operating-system state for fleet investigation.

Question 953

A URL preview service fetches an attacker-supplied address that resolves to an internal metadata endpoint. Which scoping query or comparison best tests the working hypothesis?

  1. Test redirect handling and private-address restrictions safely
  2. Inspect base-domain frequency and subdomain entropy by client
  3. Pivot from shared client fingerprint to successful accounts
  4. Correlate fallback queries with later SMB authentication attempts

Explanation

Correct Answer

A:

For scope analysis in Server-side request forgery, validation must include DNS changes and redirect hops, not only the initial URL text; this applies to the reported “A URL preview service fetches an attacker-supplied address that resolves to an internal metadata endpoint”.

Incorrect Answers

B:

The choice is relevant to DNS tunneling over queries, where grouping by resolver client differentiates unusual encoded labels from normal service discovery; for scope analysis in Server-side request forgery, validation must include DNS changes and redirect hops, not only the initial URL text.

C:

For scope analysis in Server-side request forgery, Credential stuffing on web login is a different mechanism: linking failed trials with rare subsequent successes identifies potential takeovers; here, validation must include DNS changes and redirect hops, not only the initial URL text.

D:

The choice is relevant to LLMNR or NBNS name-resolution poisoning, where unexpected follow-up authentication can show whether the spoofed resolution lured credentials; for scope analysis in Server-side request forgery, validation must include DNS changes and redirect hops, not only the initial URL text.

Question 954

A valid automation access key appears in a public source repository and its usage logs show new foreign IPs. What focused analysis should the analyst perform next?

  1. Enumerate API calls and accessible resources using the key
  2. Confirm the principal independently and review subsequent access
  3. Trace effective privileges and actions taken after the membership change
  4. Enumerate signing keys, token audiences and affected trust relationships
  5. Enumerate sessions, tokens, changes and accessed sensitive apps

Explanation

Correct Answer

A:

Given “A valid automation access key appears in a public source repository and its usage logs show new foreign IPs”, permission scope and observed operations determine potential impact; that best addresses scope analysis in Exposed cloud API credential.

Incorrect Answers

B:

That option fits Unauthorized MFA factor registration since the attacker may have gained access before suspicious enrollment was flagged; it does not fit the Exposed cloud API credential scope analysis scenario, where permission scope and observed operations determine potential impact.

C:

This option addresses Privilege escalation via group membership because the blast radius depends on what the new rights enabled and whether they were exercised; the Exposed cloud API credential scope analysis question instead turns on the fact that permission scope and observed operations determine potential impact.

D:

That option fits Compromised federation signing key since response scope extends across services that rely on the compromised certificate; it does not fit the Exposed cloud API credential scope analysis scenario, where permission scope and observed operations determine potential impact.

E:

This option addresses Employee account takeover because scope includes persistence such as new authenticators or OAuth grants; the Exposed cloud API credential scope analysis question instead turns on the fact that permission scope and observed operations determine potential impact.

Question 955

A noninteractive database service identity suddenly logs on to a user desktop through a remote interactive session. Which artifact provides the strongest corroborating detail?

  1. Windows logon type and service-account ownership records
  2. Identity token issuance and application sign-in audit
  3. MFA challenge outcomes aligned to session creation
  4. Historical sign-in activity with current admin role assignments

Explanation

Correct Answer

A:

Given “A noninteractive database service identity suddenly logs on to a user desktop through a remote interactive session”, session type distinguishes an interactive login from expected application authentication; that best addresses corroboration in Service account interactive use.

Incorrect Answers

B:

For corroboration in Service account interactive use, Unusual federation token issuance is a different mechanism: token and client information distinguishes silent renewal from fresh interactive authentication; here, session type distinguishes an interactive login from expected application authentication.

C:

The choice is relevant to MFA fatigue notification storm, where approval status and post-authentication resource actions determine whether access was granted; for corroboration in Service account interactive use, session type distinguishes an interactive login from expected application authentication.

D:

For corroboration in Service account interactive use, Dormant account revival is a different mechanism: last-use history and privilege explain why the return to activity is risky; here, session type distinguishes an interactive login from expected application authentication.

Question 956

Security personnel remain embedded in different business units and use incompatible ticket fields for the same incident severity. Which technical explanation is most defensible from the evidence?

  1. Uncovered internal SOC shifts
  2. Fragmented virtual-SOC coordination
  3. Unclear managed-SOC response authority
  4. Broken co-managed ownership transition

Explanation

Correct Answer

B:

A distributed SOC needs consistent taxonomy and central case routing despite having no single physical operations room; this is the relevant classification mechanism for Virtual SOC tool integration given “Security personnel remain embedded in different business units and use incompatible ticket fields for the same incident severity”.

Incorrect Answers

A:

For the alternative In-house SOC staffing situation, an internally staffed operation has a monitoring gap when alert ownership stops outside local working hours; by contrast, for Virtual SOC tool integration classification, a distributed SOC needs consistent taxonomy and central case routing despite having no single physical operations room.

C:

For the alternative Managed SOC provider accountability situation, outsourced monitoring does not automatically delegate containment rights or define customer approval boundaries; by contrast, for Virtual SOC tool integration classification, a distributed SOC needs consistent taxonomy and central case routing despite having no single physical operations room.

D:

In Co-managed SOC handoff, shared SOC operations require one case owner when separate teams contribute findings to the same incident; the reported Virtual SOC tool integration case calls for a different classification conclusion because a distributed SOC needs consistent taxonomy and central case routing despite having no single physical operations room.

Question 957

An infected server must be shut down, but the team needs current network sockets, decrypted runtime artifacts and process memory. Which source would most directly corroborate the observation?

  1. Acquisition manifest and independently computed image hash
  2. Raw timestamp, timezone offset and collector conversion settings
  3. Memory image with acquisition time and active session snapshot
  4. PCAP timestamps and synchronized reference traffic

Explanation

Correct Answer

C:

Volatile captures can retain evidence absent from persistent storage; this is the relevant corroboration mechanism for Volatile memory acquisition priority given “An infected server must be shut down, but the team needs current network sockets, decrypted runtime artifacts and process memory”.

Incorrect Answers

A:

For the alternative Disk forensic image integrity situation, hash comparison detects accidental or deliberate byte changes during copying; by contrast, for Volatile memory acquisition priority corroboration, volatile captures can retain evidence absent from persistent storage.

B:

In Evidence timezone ambiguity, these fields reveal whether a discrepancy is representational or a clock error; the reported Volatile memory acquisition priority case calls for a different corroboration conclusion because volatile captures can retain evidence absent from persistent storage.

D:

In Packet capture time-window reconstruction, a common event allows the timeline offset to be estimated; the reported Volatile memory acquisition priority case calls for a different corroboration conclusion because volatile captures can retain evidence absent from persistent storage.

Question 958

A hash blocklist stops one malicious sample but a recompilation evades matching despite unchanged attacker behavior. Which step would most precisely determine the affected entities?

  1. Cross-check recent behavior against other independent sources
  2. Validate schema and relationship targets before import
  3. Test incremental fetch and object-version handling
  4. Seek an independent technical artifact or trusted witness
  5. Compare related samples by code traits and runtime actions

Explanation

Correct Answer

E:

The Malware hash IoC specificity evidence “A hash blocklist stops one malicious sample but a recompilation evades matching despite unchanged attacker behavior” is decisive for scope analysis because a variant may preserve capabilities even with a completely different digest.

Incorrect Answers

A:

For the alternative Threat feed confidence decay situation, current local evidence should outweigh a stale single-provider label; by contrast, for Malware hash IoC specificity scope analysis, a variant may preserve capabilities even with a completely different digest.

B:

In STIX structured intelligence exchange, malformed references can degrade knowledge graphs and subsequent matching; the reported Malware hash IoC specificity case calls for a different scope analysis conclusion because a variant may preserve capabilities even with a completely different digest.

C:

For the alternative TAXII intelligence distribution situation, a client must handle additions and revisions without repeatedly ingesting all content; by contrast, for Malware hash IoC specificity scope analysis, a variant may preserve capabilities even with a completely different digest.

D:

In Intelligence source circular reporting, separate evidence streams provide stronger corroboration than repeated headlines; the reported Malware hash IoC specificity case calls for a different scope analysis conclusion because a variant may preserve capabilities even with a completely different digest.

Question 959

A suspected tenant-wide identity compromise leaves investigators unsure whether their normal corporate chat is trustworthy. What lasting monitoring control should be added after the case?

  1. Test alternate channels and contact rotations quarterly
  2. Train analysts to escalate cross-sensor attack chains
  3. Exercise asset lookup during incident simulations
  4. Review response role coverage and delegation after exercises

Explanation

Correct Answer

A:

In the Out-of-band crisis communications case, unused emergency methods often fail when staff details change; the observation “A suspected tenant-wide identity compromise leaves investigators unsure whether their normal corporate chat is trustworthy” makes this ongoing detection improvement choice the fitting one.

Incorrect Answers

B:

This option addresses Incident declaration threshold because case linkage rules improve declaration speed without inflating every alert; the Out-of-band crisis communications ongoing detection improvement question instead turns on the fact that unused emergency methods often fail when staff details change.

C:

That option fits Incident readiness inventory since time-to-owner tests reveal whether inventory information is usable under pressure; it does not fit the Out-of-band crisis communications ongoing detection improvement scenario, where unused emergency methods often fail when staff details change.

D:

This option addresses Incident response authority chart because personnel turnover can invalidate an otherwise well-written authority matrix; the Out-of-band crisis communications ongoing detection improvement question instead turns on the fact that unused emergency methods often fail when staff details change.

Question 960

A standard user is added to a high-privilege group by a previously unused administrator account. How should the analyst classify the activity at this stage?

  1. Federation trust material compromise
  2. Unauthorized privilege assignment response
  3. Leaked machine credential incident
  4. Compromised workforce identity containment

Explanation

Correct Answer

B:

In the Privilege escalation via group membership case, membership modification can allow subsequent access beyond the original identity's role; the observation “A standard user is added to a high-privilege group by a previously unused administrator account” makes this classification choice the fitting one.

Incorrect Answers

A:

The choice is relevant to Compromised federation signing key, where a stolen signing key can undermine token integrity for relying parties that trust it; for classification in Privilege escalation via group membership, membership modification can allow subsequent access beyond the original identity's role.

C:

The choice is relevant to Exposed cloud API credential, where a committed secret can be copied by anyone who can read the repository, even after deletion; for classification in Privilege escalation via group membership, membership modification can allow subsequent access beyond the original identity's role.

D:

For classification in Privilege escalation via group membership, Employee account takeover is a different mechanism: valid tokens can continue accessing applications until relevant sessions and factors are addressed; here, membership modification can allow subsequent access beyond the original identity's role.

Certified SOC Analyst (312-39) Practice Tests