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

Question 170

Executives track average alert handling time but cannot see how long confirmed intrusions ran before discovery. Which interpretation best fits the observed evidence?

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

Explanation

Correct Answer

D:

Handling duration starts after an alert, whereas detection latency measures delay from incident onset; this is the relevant classification mechanism for Incident detection latency dashboard given “Executives track average alert handling time but cannot see how long confirmed intrusions ran before discovery”.

Incorrect Answers

A:

For the alternative SLA breach trend by incident tier situation, averages across low and critical priorities can conceal unacceptable delays for serious incidents; by contrast, for Incident detection latency dashboard classification, handling duration starts after an alert, whereas detection latency measures delay from incident onset.

B:

In Noisy use-case Pareto dashboard, rule-level workload and outcome charts identify candidates for targeted tuning; the reported Incident detection latency dashboard case calls for a different classification conclusion because handling duration starts after an alert, whereas detection latency measures delay from incident onset.

C:

For the alternative SOC data-source coverage dashboard situation, a rule-success chart can look healthy despite unmonitored critical assets; by contrast, for Incident detection latency dashboard classification, handling duration starts after an alert, whereas detection latency measures delay from incident onset.

Question 171

An infected server must be shut down, but the team needs current network sockets, decrypted runtime artifacts and process memory. The analyst has not yet established malicious intent or downstream impact. What qualification is most important before drawing a firm conclusion?

  1. Memory imaging itself can change a running system's state
  2. Matching hashes do not establish who legally possessed the device
  3. A PCAP may omit traffic outside its capture point or window
  4. A timezone shift is not the same as an inaccurate source clock

Explanation

Correct Answer

A:

Given “An infected server must be shut down, but the team needs current network sockets, decrypted runtime artifacts and process memory”, tools allocate memory and processes while collecting evidence; that best addresses interpretation limit in Volatile memory acquisition priority.

Incorrect Answers

B:

That option fits Disk forensic image integrity since integrity and chain-of-custody authorization address different questions; it does not fit the Volatile memory acquisition priority interpretation limit scenario, where tools allocate memory and processes while collecting evidence.

C:

This option addresses Packet capture time-window reconstruction because missing packets cannot prove a host never communicated elsewhere; the Volatile memory acquisition priority interpretation limit question instead turns on the fact that tools allocate memory and processes while collecting evidence.

D:

That option fits Evidence timezone ambiguity since formatting conversions and clock skew demand different corrections; it does not fit the Volatile memory acquisition priority interpretation limit scenario, where tools allocate memory and processes while collecting evidence.

Question 172

A mobile application shows rising 401 responses after token rotation while request volume stays stable. What evidence should be obtained to validate the suspected mechanism?

  1. IIS status, substatus, time-taken and URI fields
  2. API gateway identity result, route and token validation reason
  3. WAF rule ID, matched component and disposition
  4. Apache access log URI, client, status and user agent

Explanation

Correct Answer

B:

Given “A mobile application shows rising 401 responses after token rotation while request volume stays stable”, auth failure codes help distinguish expired tokens from missing authorization scope; that best addresses corroboration in API gateway authentication logs.

Incorrect Answers

A:

For corroboration in API gateway authentication logs, IIS request diagnostics is a different mechanism: substatus and affected paths narrow the failure mode beyond a top-level 500 count; here, auth failure codes help distinguish expired tokens from missing authorization scope.

C:

For corroboration in API gateway authentication logs, WAF blocked request telemetry is a different mechanism: these fields establish what rule fired and whether the request was blocked or monitored; here, auth failure codes help distinguish expired tokens from missing authorization scope.

D:

The choice is relevant to Apache path enumeration logs, where those fields show which paths were tried and which requests succeeded; for corroboration in API gateway authentication logs, auth failure codes help distinguish expired tokens from missing authorization scope.

Question 173

A user executes sudo on a build runner and the investigator needs to identify commands run with higher privileges. Which step would most precisely determine the affected entities?

  1. Compare source application counts with collector ingestion trends
  2. Identify who modified the task and inspect invoked commands
  3. Compare sudo calls with the host's approved change record
  4. Match success to source IP, session and shell history
  5. Join executable path, auid and effective uid for each event

Explanation

Correct Answer

C:

Given “A user executes sudo on a build runner and the investigator needs to identify commands run with higher privileges”, a privileged command can be legitimate when it matches a maintenance task; that best addresses scope analysis in Linux sudo elevation audit.

Incorrect Answers

A:

For scope analysis in Linux sudo elevation audit, Linux dropped syslog messages is a different mechanism: discrepancies isolate source-side loss from a central search issue; here, a privileged command can be legitimate when it matches a maintenance task.

B:

The choice is relevant to Linux cron persistence evidence, where change history and executable provenance establish whether persistence was planted; for scope analysis in Linux sudo elevation audit, a privileged command can be legitimate when it matches a maintenance task.

D:

The choice is relevant to Linux SSH authentication messages, where the overlap distinguishes a real foothold from unrelated logins; for scope analysis in Linux sudo elevation audit, a privileged command can be legitimate when it matches a maintenance task.

E:

For scope analysis in Linux sudo elevation audit, Linux auditd execution records is a different mechanism: audit user identity helps trace privilege transitions not visible from process name alone; here, a privileged command can be legitimate when it matches a maintenance task.

Question 174

A domain controller produces event 4720 naming a newly created account outside an approved onboarding window. Which scoping query or comparison best tests the working hypothesis?

  1. Inspect assigned privileges and the originating process or service
  2. Check retained forwarded events for the pre-clear timeline
  3. Compare account creation with service tickets and first sign-ins
  4. Correlate process IDs and any command-line auditing data

Explanation

Correct Answer

C:

The Windows new account creation evidence “A domain controller produces event 4720 naming a newly created account outside an approved onboarding window” is decisive for scope analysis because follow-on use helps establish whether the new identity was abused.

Incorrect Answers

A:

This option addresses Windows privileged logon indicator because the surrounding workload separates expected system accounts from unusual privilege use; the Windows new account creation scope analysis question instead turns on the fact that follow-on use helps establish whether the new identity was abused.

B:

That option fits Windows security log clearing since a remote collector may preserve activity no longer present locally; it does not fit the Windows new account creation scope analysis scenario, where follow-on use helps establish whether the new identity was abused.

D:

That option fits Windows process creation auditing since enabled command-line capture can clarify whether suspicious arguments were supplied; it does not fit the Windows new account creation scope analysis scenario, where follow-on use helps establish whether the new identity was abused.

Question 175

A laptop contacts a new external endpoint every sixty seconds with similarly sized HTTPS requests during user inactivity. What follow-up analysis most effectively distinguishes this case?

  1. Measure interarrival regularity while checking legitimate schedulers
  2. Compare affected host behavior with known application update activity
  3. Compare observed port diversity with approved scanner schedules
  4. Compare the initiating binary and fingerprints across similar servers
  5. Identify transferred dataset and whether destination is sanctioned

Explanation

Correct Answer

A:

The Regular command beacon intervals evidence “A laptop contacts a new external endpoint every sixty seconds with similarly sized HTTPS requests during user inactivity” is decisive for scope analysis because software health checks may use a similar cadence with approved destinations.

Incorrect Answers

B:

For the alternative Domain-generation algorithm surge situation, a failed resolver or legitimate telemetry agent may create superficially similar noise; by contrast, for Regular command beacon intervals scope analysis, software health checks may use a similar cadence with approved destinations.

C:

In East-west port scan detection, known vulnerability scanners can cause the same traffic pattern; the reported Regular command beacon intervals case calls for a different scope analysis conclusion because software health checks may use a similar cadence with approved destinations.

D:

For the alternative Anomalous TLS client fingerprint situation, endpoint process attribution prevents overconfidence in network-only classification; by contrast, for Regular command beacon intervals scope analysis, software health checks may use a similar cadence with approved destinations.

E:

In Unusual outbound data volume, a large backup job may be authorized while equally sized unknown exports are not; the reported Regular command beacon intervals case calls for a different scope analysis conclusion because software health checks may use a similar cadence with approved destinations.

Question 176

An exposed API receives many unauthorized requests with rotating tokens and a small set of sensitive resource endpoints. Which scoping query or comparison best tests the working hypothesis?

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

Explanation

Correct Answer

B:

Given “An exposed API receives many unauthorized requests with rotating tokens and a small set of sensitive resource endpoints”, shared automation characteristics matter even when source IPs rotate; that best addresses scope analysis in API bearer-token guessing.

Incorrect Answers

A:

The choice is relevant to Massive object-storage upload through web app, where business-approved ETL jobs must be distinguished from an illicit export; for scope analysis in API bearer-token guessing, shared automation characteristics matter even when source IPs rotate.

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 API bearer-token guessing, shared automation characteristics matter even when source IPs rotate.

D:

For scope analysis in API bearer-token guessing, Web-shell request and process correlation is a different mechanism: file provenance and execution output establish the suspected web shell's capabilities; here, shared automation characteristics matter even when source IPs rotate.

E:

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 API bearer-token guessing, shared automation characteristics matter even when source IPs rotate.

Question 177

CloudTrail reveals an unfamiliar principal assuming a production role and then changing storage permissions. Which artifact provides the strongest corroborating detail?

  1. CloudTrail AssumeRole and subsequent resource API events
  2. Cloud Audit Logs principalEmail and key metadata
  3. Bucket access policy, object classification and access logs
  4. Entra service principal sign-ins and Azure activity records

Explanation

Correct Answer

A:

In the AWS unauthorized role assumption case, the session identifier links granted credentials with follow-on modifications; the observation “CloudTrail reveals an unfamiliar principal assuming a production role and then changing storage permissions” makes this corroboration choice the fitting one.

Incorrect Answers

B:

In GCP service account key exposed, service identity, API method and key history help attribute suspicious operations; the reported AWS unauthorized role assumption case calls for a different corroboration conclusion because the session identifier links granted credentials with follow-on modifications.

C:

For the alternative Cloud storage anonymous exposure situation, configuration and requests establish both exposure and observed retrieval; by contrast, for AWS unauthorized role assumption corroboration, the session identifier links granted credentials with follow-on modifications.

D:

In Azure automation identity misuse, app identity and resource operations connect authentication with control-plane actions; the reported AWS unauthorized role assumption case calls for a different corroboration conclusion because the session identifier links granted credentials with follow-on modifications.

Question 178

After malware cleanup, analysts close an incident even though the original command-and-control beacon still appears in proxy logs. Which investigative step would most directly establish the relevant scope?

  1. Map delays to specific tooling, role and handoff failures
  2. Check credential exposure, boot integrity and persistence inventory
  3. Search across the prior attack chain for residual behavior
  4. Map credential dependencies before staged rotation
  5. Test application transactions before reconnecting users

Explanation

Correct Answer

C:

Given “After malware cleanup, analysts close an incident even though the original command-and-control beacon still appears in proxy logs”, verification should revisit each persistence, credential and network mechanism; that best addresses scope analysis in Incident eradication verification.

Incorrect Answers

A:

For the alternative Post-incident lessons-learned review situation, actionable root causes produce changes that can later be tested; by contrast, for Incident eradication verification scope analysis, verification should revisit each persistence, credential and network mechanism.

B:

In Trusted endpoint rebuild, validation is needed before the device rejoins privileged networks; the reported Incident eradication verification case calls for a different scope analysis conclusion because verification should revisit each persistence, credential and network mechanism.

D:

In Credential recovery after domain compromise, service accounts and key trusts need sequencing to avoid production outages; the reported Incident eradication verification case calls for a different scope analysis conclusion because verification should revisit each persistence, credential and network mechanism.

E:

For the alternative Ransomware isolated restore validation situation, business-level validation detects corruption invisible to a filesystem copy check; by contrast, for Incident eradication verification scope analysis, verification should revisit each persistence, credential and network mechanism.

Question 179

One public IP attempts thousands of distinct usernames with a small set of passwords against a customer portal. Which scoping query or comparison best tests the working hypothesis?

  1. Correlate fallback queries with later SMB authentication attempts
  2. Inspect base-domain frequency and subdomain entropy by client
  3. Test redirect handling and private-address restrictions safely
  4. Pivot from shared client fingerprint to successful accounts
  5. Reproduce safely in a staging environment with parameterized queries
  6. Compare gateway MAC against trusted switch-port inventory

Explanation

Correct Answer

D:

For scope analysis in Credential stuffing on web login, linking failed trials with rare subsequent successes identifies potential takeovers; this applies to the reported “One public IP attempts thousands of distinct usernames with a small set of passwords against a customer portal”.

Incorrect Answers

A:

For scope analysis in Credential stuffing on web login, LLMNR or NBNS name-resolution poisoning is a different mechanism: unexpected follow-up authentication can show whether the spoofed resolution lured credentials; here, linking failed trials with rare subsequent successes identifies potential takeovers.

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 Credential stuffing on web login, linking failed trials with rare subsequent successes identifies potential takeovers.

C:

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

E:

For scope analysis in Credential stuffing on web login, SQL injection probing is a different mechanism: a controlled test distinguishes vulnerable string interpolation from harmless literal input; here, linking failed trials with rare subsequent successes identifies potential takeovers.

F:

The choice is relevant to ARP spoofing on local subnet, where the legitimate uplink mapping differentiates malicious ARP announcements from a planned device swap; for scope analysis in Credential stuffing on web login, linking failed trials with rare subsequent successes identifies potential takeovers.

Question 180

Event 4672 appears near a privileged service start and the analyst assumes it proves credential theft. Which source would most directly corroborate the observation?

  1. 4720 subject and new target-account identity fields
  2. 1102 source account and adjacent remote logon records
  3. Security event fields for 4625 including status and source address
  4. 4672 subject logon ID aligned with event 4624

Explanation

Correct Answer

D:

For corroboration in Windows privileged logon indicator, shared logon identifiers provide an account and logon-type context for privileged sessions; this applies to the reported “Event 4672 appears near a privileged service start and the analyst assumes it proves credential theft”.

Incorrect Answers

A:

In Windows new account creation, the initiating principal and target name help attribute account creation; the reported Windows privileged logon indicator case calls for a different corroboration conclusion because shared logon identifiers provide an account and logon-type context for privileged sessions.

B:

For the alternative Windows security log clearing situation, the clearing actor and prior session context determine whether maintenance or evasion is likely; by contrast, for Windows privileged logon indicator corroboration, shared logon identifiers provide an account and logon-type context for privileged sessions.

C:

In Windows 4625 authentication failures, failure status and logon type distinguish bad credentials from blocked logon rights; the reported Windows privileged logon indicator case calls for a different corroboration conclusion because shared logon identifiers provide an account and logon-type context for privileged sessions.

Certified SOC Analyst (312-39) Practice Tests