ECCouncil 212-89 (EC-Council Certified Incident Handler) Practice Test 39

Question 380

A container is about to be replaced by an orchestrator, and its local filesystem is ephemeral. What should be collected?

  1. Create a controlled snapshot before resource termination
  2. Preserve relevant object versions under retention controls
  3. Export ephemeral container logs and state before replacement
  4. Export cloud control-plane audit records to protected storage

Explanation

Correct Answer

C:

Container-local artifacts may disappear when the pod or task is removed. Collection should include workload identity and orchestrator metadata needed to attribute activity.

Incorrect Answers

A:

Cloud lifecycles can destroy ephemeral evidence when instances terminate; the case requires evidence from a short-lived container instance; that distinct outcome is not produced by this measure alone.

B:

Version history can distinguish successive object states if enabled and retained; here the immediate decision turns on evidence from a short-lived container instance, not the separate objective served by this response.

D:

Management API logs establish who performed configuration actions and when; for the described evidence and constraints, evidence from a short-lived container instance must be achieved first; this pursues a different result.

Question 381

An attacker used stolen service credentials to deploy ransomware across hosts. What should be coordinated with cleanup?

  1. Delete or disable malicious persistence mechanisms after preserving evidence
  2. Rebuild from vetted media and verify the boot chain
  3. Rotate affected service secrets and revoke active sessions
  4. Patch or reconfigure the vulnerable initial access service

Explanation

Correct Answer

C:

Compromised credentials remain usable after endpoint cleanup unless invalidated. Secret replacement may require coordination to avoid breaking legitimate dependent services.

Incorrect Answers

A:

A recurring launch point can recreate the payload even if the active file is quarantined; here the immediate decision turns on revocation of credentials enabling malware deployment, not the separate objective served by this response.

B:

A controlled rebuild avoids relying on a possibly untrustworthy system to certify its own cleanliness; it leaves the stated requirement—revocation of credentials enabling malware deployment—unresolved, even though it can help in another response stage.

D:

Removing malicious files without fixing the exploited weakness allows renewed compromise; the scenario asks for revocation of credentials enabling malware deployment. This alternative does not provide that particular investigation or containment result.

Question 382

A phished employee's inbox contains an attacker-created rule deleting all security notices. What corrective action is appropriate?

  1. Inspect MFA fatigue activity and reset affected sessions
  2. Remove the malicious inbox rule after preserving its metadata
  3. Correlate browser events with identity sign-in anomalies
  4. Remove unauthorized authentication methods and reverify identity

Explanation

Correct Answer

B:

Inbox rules can hide warnings or move messages to conceal compromise. Capturing the rule before deletion helps establish what activity may have been suppressed.

Incorrect Answers

A:

Repeated unsolicited prompts and unexpected approvals can signal account takeover; it leaves the stated requirement—eradication of mailbox-based concealment persistence—unresolved, even though it can help in another response stage.

C:

Visiting a page is not proof of credential disclosure; the scenario asks for eradication of mailbox-based concealment persistence. This alternative does not provide that particular investigation or containment result.

D:

An attacker-controlled MFA method may preserve access even after a password change; it can support an adjacent task, but it does not satisfy the scenario’s core need for eradication of mailbox-based concealment persistence.

Question 383

A proxy sees HTTP requests for unrelated virtual hosts over the same IP. What field helps determine the intended site for plaintext HTTP/1.1?

  1. Correlate SNI, certificate, destination, and flow characteristics
  2. Use fingerprint similarity as a hunting lead with corroboration
  3. Validate certificate identity and possible interception
  4. Review the HTTP Host header

Explanation

Correct Answer

D:

The Host field identifies the requested virtual host in many HTTP/1.1 exchanges. It does not itself prove the remote address is trustworthy or the server honored the value.

Incorrect Answers

A:

Handshake and flow data can provide clues when payload inspection is unavailable; for the described evidence and constraints, identification of a requested HTTP virtual host must be achieved first; this pursues a different result.

B:

TLS client fingerprints can cluster related implementations but are not unique malware identities; the scenario asks for identification of a requested HTTP virtual host. This alternative does not provide that particular investigation or containment result.

C:

Certificate mismatch may indicate misconfiguration or an impostor endpoint; it can support an adjacent task, but it does not satisfy the scenario’s core need for identification of a requested HTTP virtual host.

Question 384

An attacker publishes a malicious package using a similar name to a common dependency. What supply-chain control helps prevent recurrence?

  1. Pin verified dependency sources and validate package provenance
  2. Update the affected component and verify the fixed deployment
  3. Replace or isolate the unsupported component through a tracked migration
  4. Consult a current software bill of materials and dependency inventory

Explanation

Correct Answer

A:

Controlled registries, integrity metadata, and code review reduce accidental installation of impostor packages. Typosquatting exploits trust in package naming rather than a server-side injection flaw.

Incorrect Answers

B:

A tested version change removes the known vulnerable code path; it can support an adjacent task, but it does not satisfy the scenario’s core need for verification of dependency package identity.

C:

Unmaintained packages may retain exploitable defects indefinitely; by itself, it cannot deliver verification of dependency package identity, which is the decision point distinguished by the available evidence.

D:

A component inventory links vulnerable libraries to deployed applications and versions; the stated observations instead call for verification of dependency package identity; using this approach would address a different failure mode.

Question 385

A responder isolates an AWS workload by changing a security group but forgets an alternative interface path. What should the team verify?

  1. Place the API behind approved private connectivity and authentication
  2. Remove unintended public ingress and restrict network policy
  3. Apply defined egress policy and monitoring at cloud network boundaries
  4. Inspect all attached interfaces and effective network controls

Explanation

Correct Answer

D:

An instance may have multiple paths, and security-group changes apply according to attachment and stateful behavior. Validation should confirm actual reachability.

Incorrect Answers

A:

Private paths reduce exposure, while strong identity controls remain essential for callers; it can support an adjacent task, but it does not satisfy the scenario’s core need for complete containment across a cloud instance's network paths.

B:

Narrow routing and firewall rules reduce external attack paths; by itself, it cannot deliver complete containment across a cloud instance's network paths, which is the decision point distinguished by the available evidence.

C:

Egress restrictions reduce command-and-control and data-exfiltration opportunities; the stated observations instead call for complete containment across a cloud instance's network paths; using this approach would address a different failure mode.

Question 386

An organization retains full behavioral profiles indefinitely with no review. What governance improvement should be implemented?

  1. Restrict case visibility to authorized investigative roles
  2. Apply proportionate monitoring and minimize sensitive capture
  3. Define justified retention periods and secure disposal controls
  4. Provide appropriate notice and document lawful monitoring authority

Explanation

Correct Answer

C:

Monitoring data should not be kept longer than needed for approved purposes and obligations. Retention rules need legal review and accountable enforcement.

Incorrect Answers

A:

Need-to-know access protects privacy and prevents retaliation or information leaks; by itself, it cannot deliver controlled lifetime of employee behavior data, which is the decision point distinguished by the available evidence.

B:

Overcollection can expose secrets and create serious privacy risks; the stated observations instead call for controlled lifetime of employee behavior data; using this approach would address a different failure mode.

D:

Transparent policy and applicable consent or notice requirements support legitimate monitoring; because the case hinges on controlled lifetime of employee behavior data, this option would be an incomplete or mistimed response.

Question 387

An engineering workstation is communicating with an unknown Internet endpoint during an active process. What containment should be evaluated?

  1. Plan a tested maintenance window with vendor and operations approval
  2. Coordinate with plant safety and process operators before intervention
  3. Maintain validated controller logic and configuration backups
  4. Restrict unauthorized external paths while preserving controller operations

Explanation

Correct Answer

D:

Targeted network controls can reduce adversary connectivity without blocking critical PLC communication. Actual process dependencies must be validated before changes.

Incorrect Answers

A:

Industrial patching needs device compatibility, process safety, and rollback planning; the stated observations instead call for network containment compatible with ongoing plant operations; using this approach would address a different failure mode.

B:

OT response must protect human and physical safety while preserving evidence; that is separate from network containment compatible with ongoing plant operations, so it would leave the responder without the required control or evidence.

C:

Known-good logic and settings support trusted restoration after tampering; because the case hinges on network containment compatible with ongoing plant operations, this option would be an incomplete or mistimed response.

Question 388

The team must explain why a suspicious login is linked to a later database export. What proof is needed?

  1. Correlate identity, session, and transaction artifacts
  2. Build a cross-source timeline with normalized timestamps
  3. Create a defensible snapshot or forensic image of relevant storage
  4. Keep a protected master and analyze verified working copies

Explanation

Correct Answer

A:

A defensible relationship requires more than close timestamps. Authentication identifiers, session context, and database records can support or weaken the proposed sequence.

Incorrect Answers

B:

A timeline aligns evidence from separate systems to show causality and propagation; here the immediate decision turns on evidential linkage of access and data activity, not the separate objective served by this response.

C:

Point-in-time acquisition preserves the investigated state for independent analysis; it leaves the stated requirement—evidential linkage of access and data activity—unresolved, even though it can help in another response stage.

D:

Separating original evidence from working material reduces accidental alteration; for the described evidence and constraints, evidential linkage of access and data activity must be achieved first; this pursues a different result.

Question 389

Cloud administrators need to preserve who changed access policies during an incident. What is the relevant evidence source?

  1. Preserve relevant object versions under retention controls
  2. Create a controlled snapshot before resource termination
  3. Export ephemeral container logs and state before replacement
  4. Export cloud control-plane audit records to protected storage

Explanation

Correct Answer

D:

Management API logs establish who performed configuration actions and when. Central preservation matters because affected administrators may otherwise alter retention or access settings.

Incorrect Answers

A:

Version history can distinguish successive object states if enabled and retained; here the immediate decision turns on history of management-plane privilege changes, not the separate objective served by this response.

B:

Cloud lifecycles can destroy ephemeral evidence when instances terminate; it leaves the stated requirement—history of management-plane privilege changes—unresolved, even though it can help in another response stage.

C:

Container-local artifacts may disappear when the pod or task is removed; for the described evidence and constraints, history of management-plane privilege changes must be achieved first; this pursues a different result.

Question 390

A compromised boot component resists reliable removal by security software. Which recovery action restores stronger trust?

  1. Delete or disable malicious persistence mechanisms after preserving evidence
  2. Rotate affected service secrets and revoke active sessions
  3. Rebuild from vetted media and verify the boot chain
  4. Patch or reconfigure the vulnerable initial access service

Explanation

Correct Answer

C:

A controlled rebuild avoids relying on a possibly untrustworthy system to certify its own cleanliness. Firmware and boot integrity should be checked where compromise indicators warrant it.

Incorrect Answers

A:

A recurring launch point can recreate the payload even if the active file is quarantined; it leaves the stated requirement—trustworthy restoration after deep persistence—unresolved, even though it can help in another response stage.

B:

Compromised credentials remain usable after endpoint cleanup unless invalidated; for the described evidence and constraints, trustworthy restoration after deep persistence must be achieved first; this pursues a different result.

D:

Removing malicious files without fixing the exploited weakness allows renewed compromise; it can support an adjacent task, but it does not satisfy the scenario’s core need for trustworthy restoration after deep persistence.

EC-Council Certified Incident Handler (212-89) Practice Tests