Sample question 1 · Core 2 - Domain 3: Software Troubleshooting (26%)
Technicians at Orbivance Technologies, a large multinational virtualization platform provider operating under strict data-residency regulations in the EU, have identified unusual behavior on a hypervisor management console. Log analysis shows that a guest VM has been attempting to enumerate host-level resources, which is consistent with a known VM-escape exploit signature. The security team lead wants the technician to immediately reimage the guest VM and restore from backup to meet a contractual uptime SLA. The technician has not yet researched the specific malware family or confirmed whether the host hypervisor itself is affected. The security team lead is pressuring the technician to skip directly to reimaging the guest VM. According to best practice malware removal procedures, what should the technician do before reimaging?
- A. Reimage the guest VM immediately as directed by the security team lead to satisfy the contractual SLA obligation.
- B. Educate the security team lead about VM-escape risks and then proceed with scheduling a scan of all guest VMs.
- C. Research the identified exploit signature to determine whether the host hypervisor is also compromised before taking remediation action.
- D. Quarantine only the guest VM's virtual disk file and allow the hypervisor management console to remain fully operational.
View answer & explanation
Correct answer: C. Research the identified exploit signature to determine whether the host hypervisor is also compromised before taking remediation action.
[Domain 3, Subtopic 8 - Software Troubleshooting - Area 1 - Identify] Core Concept: Use best practice procedures for malware removal. requires applying identify in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (C): Research the identified exploit signature to determine whether the host hypervisor is also compromised before taking remediation action. Why the other options are incorrect: Option A: Reimaging immediately without research satisfies the SLA in the short term but risks an incomplete remediation if the hypervisor host is also infected; contractual uptime obligations do not override the need for a thorough malware removal process. Option B: Educating the security team lead is a valid final step but is not the appropriate action at this stage; scheduling scans of all guest VMs without first researching the exploit scope may miss the host-level compromise entirely. Option D: Quarantining only the guest VM's virtual disk while leaving the hypervisor management console fully operational is insufficient when a VM-escape exploit is suspected, because the host itself may already be the primary infection point requiring isolation.