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

Question 540

A containment playbook isolates every endpoint that produces a single unsigned-binary alert, including production servers. Which result would most convincingly demonstrate safe recovery?

  1. Test that repeated triggers leave one predictable effective policy
  2. Exercise benign and confirmed-malicious test cases before re-enabling
  3. Review execution logs for false matches and unauthorized removals
  4. Measure acknowledgment and triage times against the stated SLA

Explanation

Correct Answer

B:

For recovery and closure validation involving “Exercise benign and confirmed-malicious test” and the report “a single unsigned-binary alert, including production servers”, a successful replay must show the intended separation between harmless alerts and real compromise. “Use multi-signal criteria and asset-aware exception handling” is the preventive step behind this check.

Incorrect Answers

A:

For recovery and closure validation, contrasting “Test that repeated triggers leave” with “a single unsigned-binary alert, including production servers”, validation should verify idempotent end state, not just that each playbook reported success. Against “a single unsigned-binary alert, including production servers”, this does not establish “Exercise benign and confirmed-malicious test cases before”.

C:

A reliable automation result proves both threat reduction and absence of destructive side effects. “a single unsigned-binary alert, including production servers” is why proof of “benign and confirmed-malicious test cases before re-enabling” matters here.

D:

For recovery and closure validation, contrasting “Measure acknowledgment and triage times” with “a single unsigned-binary alert, including production servers”, operational improvement needs elapsed-time evidence across several shifts. The option does not link “a single unsigned-binary alert, including production servers” to “Exercise benign and confirmed-malicious test cases before”.

Question 541

Investigators must inspect a disk containing encrypted volumes and consider collecting recovery-key records. Which remediation best removes the root cause?

  1. Document imaging procedures, device errors and tool versions
  2. Add key-management coordination to the forensic readiness plan
  3. Adopt resumable validated transfers with end-to-end integrity checks
  4. Make verified forensic copies under documented handling rules
  5. Enforce one-to-one evidence identifiers and immediate intake checks

Explanation

Correct Answer

B:

For eradication and systemic correction involving “Add key-management coordination to the” and the report “encrypted volumes and consider collecting recovery-key records”, preparation can avoid frantic searches for keys after systems are isolated. “Secure the image and keys separately with controlled access” is an immediate safeguard rather than systemic prevention.

Incorrect Answers

A:

For eradication and systemic correction, contrasting “Document imaging procedures, device errors” with “encrypted volumes and consider collecting recovery-key records”, reproducibility depends on recording what was acquired and any unreadable areas. “key-management coordination to the forensic readiness” remains unverified against the reported “encrypted volumes and consider collecting recovery-key records”.

C:

For eradication and systemic correction, contrasting “Adopt resumable validated transfers with” with “encrypted volumes and consider collecting recovery-key records”, reliable acquisition addresses interrupted network transport without accepting silent corruption. “encrypted volumes and consider collecting recovery-key records” gives a different evidentiary target: “key-management coordination to the forensic readiness”.

D:

For eradication and systemic correction, contrasting “Make verified forensic copies under” with “encrypted volumes and consider collecting recovery-key records”, the process should preserve evidentiary originals rather than use them for routine analysis. The incident detail “encrypted volumes and consider collecting recovery-key records” still calls for “key-management coordination to the”.

E:

For eradication and systemic correction, contrasting “Enforce one-to-one evidence identifiers and” with “encrypted volumes and consider collecting recovery-key records”, consistent labeling prevents swapped or ambiguous exhibits. “key-management coordination to the forensic readiness” addresses a gap left by the “encrypted volumes and consider collecting recovery-key records” observation.

Question 542

A smart camera on a production LAN communicates with an unfamiliar external host and cannot run standard EDR software. What corrective action should the response owner require?

  1. Enforce unique credentials and disable unused administration services
  2. Update trusted firmware and rotate default or exposed device credentials
  3. Enforce segmentation and approved maintenance pathways at the gateway
  4. Fix event forwarding and require logging regression checks for firmware releases
  5. Require cryptographic firmware signatures and protected update channels

Explanation

Correct Answer

B:

For eradication and systemic correction involving “Update trusted firmware and rotate” and the report “host and cannot run standard EDR software”, a hardened appliance needs verified software and access settings. “Preserve gateway flows, DNS lookups, firmware version and device inventory” is the short-term measure to contrast with remediation.

Incorrect Answers

A:

For eradication and systemic correction, contrasting “Enforce unique credentials and disable” with “host and cannot run standard EDR software”, fleet-level policy removes the repeatable initial access route. The comparison turns on “host and cannot run standard EDR software” versus “trusted firmware and rotate default or”.

C:

For eradication and systemic correction, contrasting “Enforce segmentation and approved maintenance” with “host and cannot run standard EDR software”, network design must prevent edge devices from bridging trust zones. “trusted firmware and rotate default” is the criterion not satisfied for “host and cannot run standard EDR software”.

D:

For eradication and systemic correction, contrasting “Fix event forwarding and require” with “host and cannot run standard EDR software”, reliable auditing must be part of update acceptance criteria. For the “host and cannot run standard EDR software” observation, “and rotate default or exposed device credentials” remains open.

E:

For eradication and systemic correction, contrasting “Require cryptographic firmware signatures and” with “host and cannot run standard EDR software”, device-side verification prevents installation of untrusted images. The “default or exposed device credentials” requirement follows from “host and cannot run standard EDR software”.

Question 543

A legitimate newsletter service sends on behalf of a firm, but recipients reject it after a strict domain-authentication policy change. What change best turns containment into lasting eradication?

  1. Increase DMARC rejection enforcement without correcting sender-domain alignment
  2. Correct unauthorized transport transformations or block tampering paths
  3. Create forwarding-policy exceptions without authenticating the newsletter sender
  4. Configure an aligned DKIM signature or approved SPF return-path domain

Explanation

Correct Answer

D:

Alignment allows legitimate mail to satisfy policy without weakening enforcement globally. “Temporarily route affected authorized mail for review without disabling all protection” is the action that limits current exposure.

Incorrect Answers

A:

Tightening rejection policy makes legitimate newsletter delivery worse if the sender still lacks aligned SPF or DKIM. Authentication configuration for the approved provider must be fixed first.

B:

For eradication and systemic correction, contrasting “Correct unauthorized transport transformations or” with “it after a strict domain-authentication policy change”, legitimate gateways must avoid unintended modification of signed material. For this “it after a strict domain-authentication policy change” event, “signature or approved SPF return-path domain” is still outstanding.

C:

Forwarding exceptions do not establish that this outbound provider is authorized to speak for the company domain. The immediate failure is missing aligned authenticated identity for its messages.

Question 544

A device repeatedly executes a script from a temporary directory after reboot, although the associated user denies running it. Which preventive correction targets the problem at its source?

  1. Repair EDR isolation policy or network segmentation for multi-homed devices
  2. Remove malicious payloads and repair the document or application entry route
  3. Remove persistence and determine how the script was placed on the device
  4. Maintain signed application inventory and controlled deployment rules

Explanation

Correct Answer

C:

For eradication and systemic correction involving “Remove persistence and determine how” and the report “although the associated user denies running it”, a cleaned temp folder can be repopulated by a surviving dropper. “Isolate the host and suspend the malicious launcher under evidence procedures” is the action that limits current exposure.

Incorrect Answers

A:

For eradication and systemic correction, contrasting “Repair EDR isolation policy or” with “although the associated user denies running it”, root correction addresses the control coverage gap, not just this workstation. “although the associated user denies running it” is why proof of “persistence and determine how the script” matters here.

B:

For eradication and systemic correction, contrasting “Remove malicious payloads and repair” with “although the associated user denies running it”, killing only the child interpreter leaves the initial execution path. The option does not link “although the associated user denies running it” to “determine how the script was placed on”.

D:

For eradication and systemic correction, contrasting “Maintain signed application inventory and” with “although the associated user denies running it”, a trustworthy baseline improves investigation and allowlisting decisions. Only “persistence and determine how the script” would test the “although the associated user denies running it” condition.

Question 545

A suspected attacker changes network security group rules through Azure management APIs. What engineering or process change closes the original failure path?

  1. Require controlled admin consent workflows and permission reviews
  2. Repair automation rule scope and workflow permissions with least privilege
  3. Enforce least-privilege Azure RBAC and policy-based change governance
  4. Replace embedded long-lived keys with managed workload identities or short-lived tokens

Explanation

Correct Answer

C:

For eradication and systemic correction involving “Enforce least-privilege Azure RBAC and” and the report “security group rules through Azure management APIs”, preventing unauthorized updates addresses the administrative boundary. “Revert unauthorized rules and disable or constrain the initiating principal” is a temporary safeguard.

Incorrect Answers

A:

For eradication and systemic correction, contrasting “Require controlled admin consent workflows” with “security group rules through Azure management APIs”, governed application onboarding reduces future privilege abuse. “security group rules through Azure management APIs” gives a different evidentiary target: “least-privilege Azure RBAC and policy-based change”.

B:

For eradication and systemic correction, contrasting “Repair automation rule scope and” with “security group rules through Azure management APIs”, the orchestration path must be authorized and correctly mapped to incidents. The incident detail “security group rules through Azure management APIs” still calls for “least-privilege Azure RBAC and policy-based”.

D:

For eradication and systemic correction, contrasting “Replace embedded long-lived keys with” with “security group rules through Azure management APIs”, removing hardcoded secrets reduces recurrence across deployments. Against “security group rules through Azure management APIs”, this does not establish “least-privilege Azure RBAC and policy-based change”.

Question 546

A serverless cloud function begins invoking an unapproved external API after a new deployment. Which initial assessment is most strongly supported by these facts?

  1. Recognize possible malicious deployment or secret misuse in serverless execution
  2. Recognize ephemeral logging loss in orchestrated workloads
  3. Recognize that Admin Activity logs alone may not show object reads
  4. Recognize administrative privilege escalation through a compromised workload identity

Explanation

Correct Answer

A:

For assessment and interpretation involving “Recognize possible malicious deployment or” and the report “unapproved external API after a new deployment”, short-lived functions can leak data without leaving persistent VM artifacts. “Preserve deployment revision, invocation logs and secret-access events” is the independent record to examine.

Incorrect Answers

B:

For assessment and interpretation, contrasting “Recognize ephemeral logging loss in” with “unapproved external API after a new deployment”, container replacement can discard local context needed to trace an exploit. For the “unapproved external API after a new deployment” observation, “deployment or secret misuse in serverless execution” remains open.

C:

For assessment and interpretation, contrasting “Recognize that Admin Activity logs” with “unapproved external API after a new deployment”, data Access log coverage depends on service and configuration. The “possible malicious deployment or secret misuse in” requirement follows from “unapproved external API after a new deployment”.

D:

For assessment and interpretation, contrasting “Recognize administrative privilege escalation through” with “unapproved external API after a new deployment”, unusual grants can create persistent human or machine access long after a key rotates. “malicious deployment or secret misuse in serverless” remains unverified against the reported “unapproved external API after a new deployment”.

Question 547

A responder needs to preserve an EC2 EBS volume before replacing a suspected compromised instance. What acceptance test would provide the most relevant closure evidence?

  1. Generate approved test API calls and verify their delivery to protected storage
  2. Test anonymous access denial and approved service access after the fix
  3. Confirm CloudTrail shows no new unauthorized API changes after restriction
  4. Verify snapshot ownership, encryption access and collection metadata
  5. Verify the rebuilt instance's behavior and review follow-on findings

Explanation

Correct Answer

D:

For recovery and closure validation involving “Verify snapshot ownership, encryption access” and the report “volume before replacing a suspected compromised instance”, the copy must remain accessible to investigators with an auditable provenance. “Use a separate restricted forensic account and controlled analysis copies” is the remediation record that supports sign-off.

Incorrect Answers

A:

For recovery and closure validation, contrasting “Generate approved test API calls” with “volume before replacing a suspected compromised instance”, a configured trail is useful only when events are actually retained. “volume before replacing a suspected compromised instance” is not evaluated through the “snapshot ownership encryption access and collection” requirement.

B:

For recovery and closure validation, contrasting “Test anonymous access denial and” with “volume before replacing a suspected compromised instance”, security and business operations must both be verified. Here, “snapshot ownership encryption” must account for “volume before replacing a suspected compromised instance”.

C:

Validation must observe control-plane activity, not solely guest EDR. “volume before replacing a suspected compromised instance” needs a more direct result for “snapshot ownership encryption access and collection”.

E:

For recovery and closure validation, contrasting “Verify the rebuilt instance's behavior” with “volume before replacing a suspected compromised instance”, recovery should demonstrate both clean workload state and constrained reachability. The case fact “volume before replacing a suspected compromised instance” makes “snapshot ownership encryption access and collection” the better test.

Question 548

A serverless cloud function begins invoking an unapproved external API after a new deployment. Which preventive correction targets the problem at its source?

  1. Repair deployment controls and rotate compromised function secrets
  2. Enable appropriate Data Access audit logging and protected retention
  3. Add centralized logging and hardened service-account RBAC for the workload
  4. Redeploy from verified images and patch the vulnerable build path
  5. Apply least-privilege IAM governance and alert on sensitive policy updates

Explanation

Correct Answer

A:

For eradication and systemic correction involving “Repair deployment controls and rotate” and the report “unapproved external API after a new deployment”, prevention should target both code provenance and execution identity. “Disable the affected revision and restrict outbound access or credentials” is near-term containment.

Incorrect Answers

B:

For eradication and systemic correction, contrasting “Enable appropriate Data Access audit” with “unapproved external API after a new deployment”, prepared audit scope supports future object-level investigations. Only “deployment controls and rotate compromised” would test the “unapproved external API after a new deployment” condition.

C:

For eradication and systemic correction, contrasting “Add centralized logging and hardened” with “unapproved external API after a new deployment”, response readiness and least privilege reduce both evidence loss and blast radius. The “unapproved external API after a new deployment” report requires a finding about “deployment controls and rotate compromised function”.

D:

For eradication and systemic correction, contrasting “Redeploy from verified images and” with “unapproved external API after a new deployment”, eradication addresses the compromised workload and distribution source. In “unapproved external API after a new deployment”, the necessary control concerns “deployment controls and rotate compromised function”.

E:

For eradication and systemic correction, contrasting “Apply least-privilege IAM governance and” with “unapproved external API after a new deployment”, review controls reduce recurring escalation through administrative APIs. For this “unapproved external API after a new deployment” event, “deployment controls and rotate compromised” is still outstanding.

Question 549

A branch finds an employee-connected personal hotspot bridging an unmanaged device to a sensitive wired network. What should the team verify after implementing the corrective action?

  1. Verify managed clients reject the rogue certificate and join approved access points
  2. Verify revoked users and unmanaged devices fail new authentication
  3. Verify sensitive segments cannot be reached through wireless tethering
  4. Confirm disconnect rates normalize and spoofed frames no longer disrupt clients

Explanation

Correct Answer

C:

Testing must include the forbidden path rather than relying on a policy document. “Apply endpoint interface policy and network access control for unmanaged devices” is the lasting control change.

Incorrect Answers

A:

Successful defense should be measured on endpoint connection behavior. “sensitive segments cannot be reached” addresses a gap left by the “unmanaged device to a sensitive wired network” observation.

B:

For recovery and closure validation, contrasting “Verify revoked users and unmanaged” with “unmanaged device to a sensitive wired network”, the network should accept only currently authorized principals. Against “unmanaged device to a sensitive wired network”, this does not establish “segments cannot be reached through wireless tethering”.

D:

For recovery and closure validation, contrasting “Confirm disconnect rates normalize and” with “unmanaged device to a sensitive wired network”, a stable wired uplink does not test the actual wireless fault. “unmanaged device to a sensitive wired network” is why proof of “cannot be reached through wireless tethering” matters here.

Question 550

A jump host logs successful RDP sessions using a departed contractor's account after the end of the contract. What check should be completed before the incident can be closed?

  1. Check allowed application flow and denied unauthorized egress together
  2. Test prohibited guest-to-management connections and approved admin access
  3. Confirm privileged access logs show only approved accounts and hosts
  4. Confirm no active sessions or privileged grants remain for the contractor

Explanation

Correct Answer

D:

For recovery and closure validation involving “Confirm no active sessions or” and the report “account after the end of the contract”, a password change alone may leave tokens and other access intact. “Enforce automated offboarding and review inherited remote access rights” is a control change requiring validation.

Incorrect Answers

A:

For recovery and closure validation, contrasting “Check allowed application flow and” with “account after the end of the contract”, security validation must prove both service operation and restriction. The “no active sessions or privileged grants” requirement follows from “account after the end of the contract”.

B:

For recovery and closure validation, contrasting “Test prohibited guest-to-management connections and” with “account after the end of the contract”, validation needs a negative access test as well as business continuity. “active sessions or privileged grants remain for” remains unverified against the reported “account after the end of the contract”.

C:

For recovery and closure validation, contrasting “Confirm privileged access logs show” with “account after the end of the contract”, a clean network scan is not sufficient proof of restored authorization. For “account after the end of the contract”, the missing check concerns “no active sessions or”.

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