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

Question 80

A public API becomes unreachable during a geographically distributed traffic surge. Which TWO interpretations should an incident report avoid presenting as established facts from edge-flow counts alone? Choose TWO.

  1. Every apparent source address represents an independently controlled attacking device.
  2. The outage coincided with a substantial increase in connection attempts.
  3. Service degradation should be measured against baseline latency and error rates.
  4. Rate limiting and upstream-provider coordination may be necessary to restore capacity.
  5. All observed requests were malicious merely because they arrived during the outage.

Explanation

Correct Answers

A:

Source IPs may reflect proxies, carrier gateways, spoofed packets or cloud edges. A flow count does not by itself establish the number of distinct compromised endpoints.

E:

Flash crowds, retries and legitimate monitoring can contribute to high volume. Intent needs protocol patterns and corroborating context, not just an association with service failure.

Incorrect Answers

B:

If the time series and health data are validated, the report can properly state the observed correlation. That descriptive finding does not require identifying each source's owner.

C:

That is an appropriate validation step rather than an unsupported interpretation. It helps connect reported user impact with the timing and severity of elevated traffic.

D:

This is a plausible mitigation consideration, not a false attribution claim. It must still be tailored to the congested protocol layer and provider controls.

Question 81

A SOC subscribes to many feeds but analysts cannot explain which business threats the data is meant to address. Which source would most directly corroborate the observation?

  1. Stakeholder threat questions and critical-asset inventory
  2. Sector-focused threat assessments and campaign trends
  3. Documented technique chains and ATT&CK mappings
  4. Full campaign TTP sequence and independent corroboration

Explanation

Correct Answer

A:

The Intelligence collection requirement evidence “A SOC subscribes to many feeds but analysts cannot explain which business threats the data is meant to address” is decisive for corroboration because questions tied to assets identify which intelligence would actually influence operations.

Incorrect Answers

B:

In Strategic threat intelligence for executives, aggregated reporting supports investment decisions despite uncertainty in specific attackers; the reported Intelligence collection requirement case calls for a different corroboration conclusion because questions tied to assets identify which intelligence would actually influence operations.

C:

For the alternative Tactical intelligence of attacker procedures situation, observed behaviors expose the mechanisms that remain when individual domains disappear; by contrast, for Intelligence collection requirement corroboration, questions tied to assets identify which intelligence would actually influence operations.

D:

In Threat actor attribution uncertainty, multiple independent behaviors support confidence better than one public malware family; the reported Intelligence collection requirement case calls for a different corroboration conclusion because questions tied to assets identify which intelligence would actually influence operations.

Question 82

Regional analysts close their shifts with open high-priority cases but the next region receives only short chat messages. Which artifact provides the strongest corroborating detail?

  1. Ticket schemas and severity mapping from each unit
  2. Cross-team case history and assignment changes
  3. After-hours alert arrival and acknowledgement records
  4. Shift handover notes with linked case artifacts

Explanation

Correct Answer

D:

The Follow-the-sun SOC transfer evidence “Regional analysts close their shifts with open high-priority cases but the next region receives only short chat messages” is decisive for corroboration because the notes should identify the owner, current hypothesis, containment status and next decision.

Incorrect Answers

A:

For corroboration in Follow-the-sun SOC transfer, Virtual SOC tool integration is a different mechanism: differences in mandatory fields or classifications explain why cross-unit prioritization fails; here, the notes should identify the owner, current hypothesis, containment status and next decision.

B:

The choice is relevant to Co-managed SOC handoff, where case records show missing attachments or ownership changes when identity and network alerts converge; for corroboration in Follow-the-sun SOC transfer, the notes should identify the owner, current hypothesis, containment status and next decision.

C:

For corroboration in Follow-the-sun SOC transfer, In-house SOC staffing is a different mechanism: ticket timestamps expose the gap between event creation and a human taking responsibility; here, the notes should identify the owner, current hypothesis, containment status and next decision.

Question 83

A report claims attacks doubled after new branch-office sensors were added to the SIEM last month. Which evidence collection choice best supports this investigation?

  1. Sensor onboarding dates and normalized event exposure
  2. Asset inventory matched with log-source heartbeat records
  3. Confirmed timeline onset and first-detection timestamps
  4. Alert counts, disposition codes and analyst effort by rule
  5. Priority-specific assignment, acknowledgement and escalation timestamps

Explanation

Correct Answer

A:

Coverage changes are needed to interpret count trends fairly; this is the relevant corroboration mechanism for Threat trend comparison without normalization given “A report claims attacks doubled after new branch-office sensors were added to the SIEM last month”.

Incorrect Answers

B:

That option fits SOC data-source coverage dashboard since the coverage denominator must include all assets expected to provide security telemetry; it does not fit the Threat trend comparison without normalization corroboration scenario, where coverage changes are needed to interpret count trends fairly.

C:

This option addresses Incident detection latency dashboard because verified milestones define the time interval being measured; the Threat trend comparison without normalization corroboration question instead turns on the fact that coverage changes are needed to interpret count trends fairly.

D:

That option fits Noisy use-case Pareto dashboard since volume alone cannot show which detections waste investigation capacity; it does not fit the Threat trend comparison without normalization corroboration scenario, where coverage changes are needed to interpret count trends fairly.

E:

This option addresses SLA breach trend by incident tier because milestone data supports accurate SLA measurement for each severity tier; the Threat trend comparison without normalization corroboration question instead turns on the fact that coverage changes are needed to interpret count trends fairly.

Question 84

A worker opened a booby-trapped document and EDR observed a spawned interpreter creating an unknown executable. What focused analysis should the analyst perform next?

  1. Map poster distribution and resulting identity sign-ins
  2. Verify pending transactions with finance via known callback numbers
  3. Identify affected identities and all permission scopes
  4. Find recipients and hunt the spawned executable across devices

Explanation

Correct Answer

D:

For scope analysis in Malicious email attachment execution, campaign scope requires both mail and endpoint visibility; this applies to the reported “A worker opened a booby-trapped document and EDR observed a spawned interpreter creating an unknown executable”.

Incorrect Answers

A:

This option addresses QR-code phishing landing page because physical and web evidence jointly estimate exposed employee populations; the Malicious email attachment execution scope analysis question instead turns on the fact that campaign scope requires both mail and endpoint visibility.

B:

That option fits Business email compromise wire request since independent confirmation limits reliance on potentially compromised mail threads; it does not fit the Malicious email attachment execution scope analysis scenario, where campaign scope requires both mail and endpoint visibility.

C:

This option addresses Malicious OAuth app consent response because incident scope depends on the app's grants, not only the initially clicked link; the Malicious email attachment execution scope analysis question instead turns on the fact that campaign scope requires both mail and endpoint visibility.

Question 85

A storage service produces security-relevant operation logs locally, but the SOC's Log Analytics workspace receives none. Which engineering change provides the most relevant ongoing visibility?

  1. Monitor analytics-rule failures and source ingestion health
  2. Measure open critical findings and control compliance by account
  3. Route high-confidence GuardDuty findings into a centralized response workflow
  4. Centralize organization trails with tamper-resistant storage
  5. Alert on unexpected resource-log volume gaps by asset type

Explanation

Correct Answer

E:

Given “A storage service produces security-relevant operation logs locally, but the SOC's Log Analytics workspace receives none”, monitoring collection health prevents silent visibility failures; that best addresses ongoing detection improvement in Azure Monitor diagnostic data routing.

Incorrect Answers

A:

For ongoing detection improvement in Azure Monitor diagnostic data routing, Microsoft Sentinel analytic rule is a different mechanism: a correct KQL rule cannot alert on absent or unmapped event data; here, monitoring collection health prevents silent visibility failures.

B:

The choice is relevant to AWS Security Hub finding consolidation, where posture dashboards need consistent account and resource scope; for ongoing detection improvement in Azure Monitor diagnostic data routing, monitoring collection health prevents silent visibility failures.

C:

For ongoing detection improvement in Azure Monitor diagnostic data routing, AWS GuardDuty threat finding is a different mechanism: automated intake supports timely triage while retaining source details; here, monitoring collection health prevents silent visibility failures.

D:

The choice is relevant to AWS CloudTrail API activity, where cross-account archival reduces the chance of unilateral log deletion; for ongoing detection improvement in Azure Monitor diagnostic data routing, monitoring collection health prevents silent visibility failures.

Question 86

A suspected malicious process exits quickly but a forensic memory snapshot was acquired while the host remained running. The finding has been corroborated and the response team has authorization to act. What containment or corrective change best addresses the confirmed finding?

  1. Deploy vetted YARA rules to scoped evidence collections
  2. Deploy backend-specific conversions only after validation
  3. Investigate high-risk hosts identified by metadata anomalies
  4. Analyze a verified image copy while preserving the original

Explanation

Correct Answer

D:

In the Volatility memory-focused hunt case, evidence integrity matters when interpreting volatile captures; the observation “A suspected malicious process exits quickly but a forensic memory snapshot was acquired while the host remained running” makes this response decision choice the fitting one.

Incorrect Answers

A:

In YARA rule string matching, static matching assists discovery without executing suspect binaries; the reported Volatility memory-focused hunt case calls for a different response decision conclusion because evidence integrity matters when interpreting volatile captures.

B:

For the alternative Sigma analytic rule portability situation, successful translation still needs data and field coverage confirmation; by contrast, for Volatility memory-focused hunt response decision, evidence integrity matters when interpreting volatile captures.

C:

In Threat hunt with Zeek connection logs, flow evidence narrows the scope for more expensive endpoint analysis; the reported Volatility memory-focused hunt case calls for a different response decision conclusion because evidence integrity matters when interpreting volatile captures.

Question 87

A rule flags every nightly large file copy from backup servers because it uses the workstation transfer baseline. The analyst has not yet established malicious intent or downstream impact. What caution prevents an unsupported inference from these records?

  1. An anomaly score is relative to the chosen baseline
  2. A threshold is meaningful only with its window semantics
  3. Three alerts on one asset are not necessarily one attack
  4. An exclusion is not a risk treatment by itself

Explanation

Correct Answer

A:

The Peer-group baseline mismatch evidence “A rule flags every nightly large file copy from backup servers because it uses the workstation transfer baseline” is decisive for interpretation limit because a high score may describe a normal job in the wrong comparison cohort.

Incorrect Answers

B:

That option fits Sliding-window aggregation error since the same event rate can trigger or evade depending on aggregation design; it does not fit the Peer-group baseline mismatch interpretation limit scenario, where a high score may describe a normal job in the wrong comparison cohort.

C:

This option addresses Multi-stage attack sequence correlation because a causal interpretation requires timing, context and compatible process or session evidence; the Peer-group baseline mismatch interpretation limit question instead turns on the fact that a high score may describe a normal job in the wrong comparison cohort.

D:

That option fits Overbroad allowlist suppression since hiding an event from a rule does not prevent the underlying behavior; it does not fit the Peer-group baseline mismatch interpretation limit scenario, where a high score may describe a normal job in the wrong comparison cohort.

Question 88

An IIS-hosted application returns repeated HTTP 500 errors after deployment while client requests vary normally. The finding has been corroborated and the response team has authorization to act. What action should the incident owner take to reduce the immediate risk?

  1. Investigate any successful sensitive-file access before rate-limiting
  2. Keep the malicious sample quarantined and hunt related recipients
  3. Roll back a confirmed faulty deployment under change control
  4. Suspend confirmed unauthorized grants and preserve audit trails

Explanation

Correct Answer

C:

The IIS request diagnostics evidence “An IIS-hosted application returns repeated HTTP 500 errors after deployment while client requests vary normally” is decisive for response decision because a functional regression needs repair rather than blind IP blocking.

Incorrect Answers

A:

That option fits Apache path enumeration logs since an enumeration attempt becomes more serious if it discovers protected content; it does not fit the IIS request diagnostics response decision scenario, where a functional regression needs repair rather than blind IP blocking.

B:

This option addresses Email message trace analysis because preserving evidence supports detection without restoring unsafe content to users; the IIS request diagnostics response decision question instead turns on the fact that a functional regression needs repair rather than blind IP blocking.

D:

This option addresses Database privileged query audit because least-disruptive response should protect data and retain investigative evidence; the IIS request diagnostics response decision question instead turns on the fact that a functional regression needs repair rather than blind IP blocking.

Question 89

A malware analyst wants to classify suspicious binaries using several distinctive byte strings and a rule condition. How should the detection program improve coverage for this pattern?

  1. Monitor YARA detection precision after signature updates
  2. Enable protected forwarding of relevant script block telemetry
  3. Record memory-acquisition quality and plugin reproducibility
  4. Baseline rare network destinations with sensor health checks

Explanation

Correct Answer

A:

In the YARA rule string matching case, new variants may change string placement or benign software may share patterns; the observation “A malware analyst wants to classify suspicious binaries using several distinctive byte strings and a rule condition” makes this ongoing detection improvement choice the fitting one.

Incorrect Answers

B:

This option addresses PowerShell script-block hunting because central retention reduces reliance on local event storage; the YARA rule string matching ongoing detection improvement question instead turns on the fact that new variants may change string placement or benign software may share patterns.

C:

That option fits Volatility memory-focused hunt since incomplete captures or wrong symbols can produce misleading results; it does not fit the YARA rule string matching ongoing detection improvement scenario, where new variants may change string placement or benign software may share patterns.

D:

This option addresses Threat hunt with Zeek connection logs because visibility and traffic volume affect the interpretation of rarity; the YARA rule string matching ongoing detection improvement question instead turns on the fact that new variants may change string placement or benign software may share patterns.

Question 90

A serverless workload begins contacting an unapproved Internet host after a dependency update. Which step would most precisely determine the affected entities?

  1. Compare revision hash and dependency changes against prior builds
  2. Trace source parser, UDM field and detection match
  3. Compare misconfiguration findings with project ownership and exposure
  4. Correlate key creation with subsequent setIamPolicy operations

Explanation

Correct Answer

A:

The Cloud function unusual outbound connections evidence “A serverless workload begins contacting an unapproved Internet host after a dependency update” is decisive for scope analysis because deployment lineage narrows which code introduced outbound behavior.

Incorrect Answers

B:

That option fits Google Security Operations threat correlation since schema mapping and entity integrity are required for reliable correlation; it does not fit the Cloud function unusual outbound connections scope analysis scenario, where deployment lineage narrows which code introduced outbound behavior.

C:

This option addresses Google Cloud Security Command Center posture because business criticality and actual access paths determine remediation priority; the Cloud function unusual outbound connections scope analysis question instead turns on the fact that deployment lineage narrows which code introduced outbound behavior.

D:

That option fits Google Cloud audit log principal investigation since a session sequence can reveal whether a new credential changed authorization; it does not fit the Cloud function unusual outbound connections scope analysis scenario, where deployment lineage narrows which code introduced outbound behavior.

Certified SOC Analyst (312-39) Practice Tests