Pass ECCouncil 212-89 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
ECCouncil 212-89 Practice Test 73
Question 720
At Maplepoint Telecom, the incident commander needs to resolve: A media company finds an IAM access key posted in a public ticket while unusual S3 object listings appear overnight. Which focused investigation AND separately observable proof BEST verify the conclusion?
Explanation
Correct Answer
The targeted investigation is: Query CloudTrail by access key identifier and compare with bucket server access evidence. Independent acceptance: The leaked key is rejected and authorized automation resumes with reduced privileges. It is tied to the observed evidence: CloudTrail records show GetObject and ListBucket from a new source address under the exposed key. It tests the conditions for this response: Disable the compromised key, rotate dependent workloads and evaluate S3 requests, data access and role permissions.
Incorrect Answers
Another investigation would examine: Test anonymous object access and review object access logs for the exposure window. Independent acceptance: Anonymous requests fail and approved application identities can still read their intended objects. It does not directly establish the reported condition: CloudTrail records show GetObject and ListBucket from a new source address under the exposed key.
Another check would investigate Correlate service account key IDs, audit resource calls and workload deployment history. Independent acceptance: Unexpected export calls cease while approved jobs run with a new managed identity pathway. The case observation to isolate is CloudTrail records show GetObject and ListBucket from a new source address under the exposed key. The focused check here is: Query CloudTrail by access key identifier and compare with bucket server access evidence. Independent acceptance: The leaked key is rejected and authorized automation resumes with reduced privileges.
Another investigation would compare organization-level event history with account trail modification records. Independent acceptance: New control-plane actions are recorded in the approved centralized audit account with tamper alarms. It does not directly establish the reported condition: CloudTrail records show GetObject and ListBucket from a new source address under the exposed key.
Question 721
At fictional Ironwood Transport, incident responders encounter this case: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. Collected triage evidence: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. Which authorized response BEST addresses the situation?
Explanation
Correct Answer
The issue turns on Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The relevant rule is that Google Cloud incident handling must examine service identities and token access independently of compute instances. The targeted correction is: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries.
Incorrect Answers
Another proposed action is: Revoke relevant sessions, rotate exposed application secrets and review privileged app consent with an authorized identity team. That does not directly address the observed condition: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The more targeted correction is: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries.
Another proposed action is: Protect existing replicated logs, restore governed trails and investigate the principal's permissions and other actions. It targets a different dependency; the evidence here is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
That alternative concerns: Map collectible provider logs, guest records and snapshot controls to the approved incident playbook. The relevant evidence is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The corresponding fix is: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries.
Question 722
At Ironwood Transport, responders investigate this incident scenario: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. Which evidence MOST specifically validates the underlying concern?
Explanation
Correct Answer
Consider this evidence: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The applicable explanation is: Google Cloud incident handling must examine service identities and token access independently of compute instances. The matching response is: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries.
Incorrect Answers
This other option describes: Use this distinguishing observed fact: Provider support can supply platform-level records, but the tenant has not enabled guest telemetry or authorized snapshot workflows. The problem to explain is different: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
Another proposed finding is: Use this distinguishing observed fact: Storage policy analysis and access records show public principals can retrieve a restricted sample object. It is not the recorded discriminator, which is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
That alternative uses a different finding: Instance lifecycle settings show ephemeral storage and no recent disk snapshot or memory collection as decisive. The actual evidence in this case is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
Question 723
At Ironwood Transport, the proposed containment or recovery measure is: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries. What independently observable result BEST demonstrates appropriate resolution?
Explanation
Correct Answer
The independent verification condition is: Unexpected export calls cease while approved jobs run with a new managed identity pathway. That result checks whether the original evidence—Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions—has been addressed.
Incorrect Answers
Passing that test would not establish resolution of the stated issue. The relevant proof is: Unexpected export calls cease while approved jobs run with a new managed identity pathway.
That result would assess another condition: Require independent verification by showing: An exercise obtains the required tenant evidence without assuming inaccessible provider internals. The correct criterion is directly linked to the finding: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
A different option checks: Require independent verification by showing: The leaked key is rejected and authorized automation resumes with reduced privileges. The case-specific acceptance condition is instead Unexpected export calls cease while approved jobs run with a new managed identity pathway.
Question 724
At Ironwood Transport, an incident commander examines: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. The important discriminating evidence is: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. Which incident-response principle BEST fits the case?
Explanation
Correct Answer
The observed evidence is: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The governing principle is: Google Cloud incident handling must examine service identities and token access independently of compute instances. Consequently, the targeted action is: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries.
Incorrect Answers
A competing choice applies the relevant incident-response principle: Azure incident containment should join identity telemetry with affected app registrations and conditional access. The governing distinction for the recorded case is Google Cloud incident handling must examine service identities and token access independently of compute instances.
Another option applies the relevant incident-response principle: Cloud recovery should restore services using least privilege and higher-level governance constraints. The present evidence is: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The case-relevant principle is: Google Cloud incident handling must examine service identities and token access independently of compute instances.
That principle concerns another fact pattern: Apply the relevant incident-response principle: Cloud investigation must preserve immutable off-account audit sources and identify logging-control tampering. Here the key fact is: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
Question 725
The incident response team at Ironwood Transport plans to: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries. Which safety, privacy, forensic or operational caveat is MOST important?
Explanation
Correct Answer
The risk to retain is: Removing only the compromised pod can leave credentials active elsewhere. The original evidence is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions; widening the change beyond it is not justified.
Incorrect Answers
This limitation concerns another setting: Retain this material forensic, business or safety caveat: Incorrect responsibility assumptions can allow ephemeral evidence to expire. The observed facts here make a different caution decisive: Removing only the compromised pod can leave credentials active elsewhere.
A different caution is to retain this material forensic, business or safety caveat: Deleting a visible secret does not remove copies already downloaded by attackers. The key risk in this case is: Removing only the compromised pod can leave credentials active elsewhere.
This limitation concerns another setting: Retain this material forensic, business or safety caveat: Blindly removing all administrators can lock responders out of critical recovery controls. The observed facts here make a different caution decisive: Removing only the compromised pod can leave credentials active elsewhere.
Question 726
In a second deliberately RELATED fictional incident response exercise at Crestview Utilities: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. Which evidence–action–proof sequence BEST handles the incident safely?
Explanation
Correct Answer
The starting point is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The proposed action and its separate check are Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries and Unexpected export calls cease while approved jobs run with a new managed identity pathway, respectively.
Incorrect Answers
An alternative sequence would follow this validated evidence, authorized response and proof sequence: Confirm the distinguishing observation: Control-plane audit logs show the role grant and an unfamiliar session using a credential issued shortly before the changes. Under the incident commander and applicable safety, legal and privacy authority, apply this bounded response: Revoke suspect sessions, limit excessive role grants and capture affected audit/configuration history through approved responders. Independently confirm the result: Unauthorized privilege paths close and critical audit visibility is restored with no unreviewed roles. It has no direct link to the distinguishing evidence: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
Another action-and-check pairing is: Follow this validated evidence, authorized response and proof sequence: Confirm the distinguishing observation: Storage policy analysis and access records show public principals can retrieve a restricted sample object. Under the incident commander and applicable safety, legal and privacy authority, apply this bounded response: Remove public permission, preserve access evidence and perform a counsel-guided exposure assessment and configuration remediation. Independently confirm the result: Anonymous requests fail and approved application identities can still read their intended objects. The evidence here is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The required action and proof are Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries and Unexpected export calls cease while approved jobs run with a new managed identity pathway.
Another combination would follow this validated evidence, authorized response and proof sequence: Confirm the distinguishing observation: Entra sign-in and audit records identify successful token use from an unfamiliar device and application credential creation. Under the incident commander and applicable safety, legal and privacy authority, apply this bounded response: Revoke relevant sessions, rotate exposed application secrets and review privileged app consent with an authorized identity team. Independently confirm the result: Unrecognized access stops and tenant administration continues with verified trusted principals. The current record instead supports Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries, verified by Unexpected export calls cease while approved jobs run with a new managed identity pathway.
Question 727
At Crestview Utilities, a related incident requires response to: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. Which containment or recovery action AND independently measurable acceptance test form the BEST pair?
Explanation
Correct Answer
The case evidence indicates: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. Apply the scoped action: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries. Confirm its effect independently: Unexpected export calls cease while approved jobs run with a new managed identity pathway.
Incorrect Answers
Another possible combination is: Revoke suspect sessions, limit excessive role grants and capture affected audit/configuration history through approved responders. Independent confirmation: Unauthorized privilege paths close and critical audit visibility is restored with no unreviewed roles. The current record instead supports Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries, verified by Unexpected export calls cease while approved jobs run with a new managed identity pathway.
Another potential sequence is: Protect existing replicated logs, restore governed trails and investigate the principal's permissions and other actions. Independent confirmation: New control-plane actions are recorded in the approved centralized audit account with tamper alarms. It has no direct link to the distinguishing evidence: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
An alternative plan is: Document the missing historical data and enable supported diagnostic capture and retention for critical resources. Independent confirmation: A controlled future test connection produces the expected normalized network evidence. It does not test the case-specific condition: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
Question 728
Responders at Crestview Utilities investigate a related case: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. Which evidence AND causal interpretation BEST match the underlying incident?
Explanation
Correct Answer
The observed evidence is: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The governing principle is: Google Cloud incident handling must examine service identities and token access independently of compute instances. Consequently, the targeted action is: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries. For the current case, the offered answer is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. Causal principle: Google Cloud incident handling must examine service identities and token access independently of compute instances.
Incorrect Answers
This alternative invokes: IAM role diff shows wildcard access returning before application functionality tests. Causal principle: Cloud recovery should restore services using least privilege and higher-level governance constraints. The governing distinction for the recorded case is Google Cloud incident handling must examine service identities and token access independently of compute instances.
The competing option invokes: Instance lifecycle settings show ephemeral storage and no recent disk snapshot or memory collection. Causal principle: Cloud containment must weigh active attack risk against ephemeral forensic preservation and service effects. The present evidence is: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The case-relevant principle is: Google Cloud incident handling must examine service identities and token access independently of compute instances.
That principle concerns another fact pattern: Entra sign-in and audit records identify successful token use from an unfamiliar device and application credential creation. Causal principle: Azure incident containment should join identity telemetry with affected app registrations and conditional access. Here the key fact is: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
Question 729
At Crestview Utilities, responders must address: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. Which bounded response AND safety or evidence-preservation safeguard are BEST paired?
Explanation
Correct Answer
The relevant boundary is: Removing only the compromised pod can leave credentials active elsewhere. It matters when applying the specific response: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries.
Incorrect Answers
This limitation concerns another setting: Proportionate incident response: Revoke suspect sessions, limit excessive role grants and capture affected audit/configuration history through approved responders. Key caveat: Blindly removing all administrators can lock responders out of critical recovery controls. The observed facts here make a different caution decisive: Removing only the compromised pod can leave credentials active elsewhere.
Another caution is: Proportionate incident response: Map collectible provider logs, guest records and snapshot controls to the approved incident playbook. Key caveat: Incorrect responsibility assumptions can allow ephemeral evidence to expire. The key risk in this case is: Removing only the compromised pod can leave credentials active elsewhere.
A separate response consideration is: Revoke relevant sessions, rotate exposed application secrets and review privileged app consent with an authorized identity team. Key caveat: A password change without app-token review may leave unauthorized control. The current change is Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries; the material limitation is Removing only the compromised pod can leave credentials active elsewhere.
Question 730
At Crestview Utilities, the incident commander needs to resolve: A Google Cloud analytics team rebuilds a container after suspected tampering but leaves its highly privileged service account key unchanged. Which focused investigation AND separately observable proof BEST verify the conclusion?
Explanation
Correct Answer
The targeted investigation is: Correlate service account key IDs, audit resource calls and workload deployment history. Independent acceptance: Unexpected export calls cease while approved jobs run with a new managed identity pathway. It is tied to the observed evidence: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. It tests the conditions for this response: Disable exposed key material, limit the service account's IAM roles and preserve related GCP audit entries.
Incorrect Answers
Another investigation would examine: Test anonymous object access and review object access logs for the exposure window. Independent acceptance: Anonymous requests fail and approved application identities can still read their intended objects. It does not directly establish the reported condition: Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions.
That check concerns a different signal: Compare effective GCP IAM policies and replay safe allowed/denied API operations. Independent acceptance: Approved service calls work while unauthorized project administration attempts fail. The case-relevant check is: Correlate service account key IDs, audit resource calls and workload deployment history. Independent acceptance: Unexpected export calls cease while approved jobs run with a new managed identity pathway.
Another check would investigate Inspect Azure diagnostic settings, storage destinations and time coverage. Independent acceptance: A controlled future test connection produces the expected normalized network evidence. The case observation to isolate is Cloud Audit Logs show the same service account creating unexpected storage exports from multiple regions. The focused check here is: Correlate service account key IDs, audit resource calls and workload deployment history. Independent acceptance: Unexpected export calls cease while approved jobs run with a new managed identity pathway.
EC-Council Certified Incident Handler (212-89) Practice Tests
- ECCouncil 212-89 Practice Test 71 - 10 Questions (Last Reviewed 08-Nov-2026)
- ECCouncil 212-89 Practice Test 72 - 10 Questions (Last Reviewed 07-Nov-2026)
- ECCouncil 212-89 Practice Test 73 - 10 Questions (Last Reviewed 06-Nov-2026)
- ECCouncil 212-89 Practice Test 74 - 10 Questions (Last Reviewed 05-Nov-2026)
- ECCouncil 212-89 Practice Test 75 - 10 Questions (Last Reviewed 04-Nov-2026)
