Question 550
To keep sensitive data-access records intact for the investigation window, which option is the direct technical match?
- Database row-level security
- Data export approval
- Data subject deletion workflow
- Data integrity constraints
- Audit-log retention protection
Explanation
Correct Answer
E:Restricted append and retention permissions help preserve evidence against user-level manipulation; the requested outcome is precisely to keep sensitive data-access records intact for the investigation window.
Incorrect Answers
A:Row-level policy filters result visibility within a shared table according to request identity or attributes; that is useful when the task is to limit each regional analyst to records within assigned territories, not the stated requirement to keep sensitive data-access records intact for the investigation window.
B:Governed exports apply least privilege and traceability to high-impact transfer operations; a team would select it to require authorization and logging before bulk extraction of employee records, which does not provide the particular result to keep sensitive data-access records intact for the investigation window.
C:Erasure handling tracks replicas, backups and legal exemptions rather than deleting one database row only; its operational purpose is to coordinate removal of eligible personal records across connected systems, not to achieve the specific requirement to keep sensitive data-access records intact for the investigation window.
D:Database constraints maintain permissible states but do not authenticate who submitted every transaction; applying it would serve reject invalid or inconsistent records before they enter a relational table without directly satisfying the goal to keep sensitive data-access records intact for the investigation window.
Question 551
To reduce attack exposure on hosts running many production virtual machines, which approach should a virtualization security engineer choose?
- Golden VM images
- Virtual machine secure boot
- VM escape patching
- Virtual TPM enablement
- Hypervisor management isolation
- Type-1 hypervisor hardening
Explanation
Correct Answer
F:Bare-metal virtualization hosts require restricted management, timely updates and minimized optional services; this choice fits the scenario because the team must reduce attack exposure on hosts running many production virtual machines.
Incorrect Answers
A:Controlled templates reduce inconsistent settings across newly created workloads; it could help someone trying to provision servers from a repeatedly tested hardened baseline, but the problem is instead to reduce attack exposure on hosts running many production virtual machines.
B:Guest UEFI verification validates signed boot artifacts independently of the physical server's startup chain; that is useful when the task is to reject unauthorized guest boot components after a template change, not the stated requirement to reduce attack exposure on hosts running many production virtual machines.
C:Maintaining the virtualization layer protects a trust boundary not enforced by guest antivirus alone; a team would select it to mitigate a hypervisor flaw that could let guest code affect the host, which does not provide the particular result to reduce attack exposure on hosts running many production virtual machines.
D:A virtual TPM supplies guest cryptographic capabilities but its state must be protected during host migration and backup; its operational purpose is to support measured startup and protected guest encryption keys, not to achieve the specific requirement to reduce attack exposure on hosts running many production virtual machines.
E:Dedicated access networks and strong authentication protect operations capable of manipulating many guests; applying it would serve stop ordinary office clients from accessing virtualization control APIs without directly satisfying the goal to reduce attack exposure on hosts running many production virtual machines.
Question 552
To stop ordinary office clients from accessing virtualization control APIs, which method is designed for the task?
- VM escape patching
- Type-1 hypervisor hardening
- Hypervisor management isolation
- Golden VM images
Explanation
Correct Answer
C:Dedicated access networks and strong authentication protect operations capable of manipulating many guests; this mechanism directly supports the requirement to stop ordinary office clients from accessing virtualization control APIs.
Incorrect Answers
A:Maintaining the virtualization layer protects a trust boundary not enforced by guest antivirus alone; although relevant to mitigate a hypervisor flaw that could let guest code affect the host, it does not by itself achieve the required task to stop ordinary office clients from accessing virtualization control APIs.
B:Bare-metal virtualization hosts require restricted management, timely updates and minimized optional services; it could help someone trying to reduce attack exposure on hosts running many production virtual machines, but the problem is instead to stop ordinary office clients from accessing virtualization control APIs.
D:Controlled templates reduce inconsistent settings across newly created workloads; a team would select it to provision servers from a repeatedly tested hardened baseline, which does not provide the particular result to stop ordinary office clients from accessing virtualization control APIs.
Question 553
To mitigate a hypervisor flaw that could let guest code affect the host, what technique should the team use?
- Virtual machine secure boot
- VM escape patching
- Virtual TPM enablement
- Golden VM images
Explanation
Correct Answer
B:Maintaining the virtualization layer protects a trust boundary not enforced by guest antivirus alone; it supplies the specific control needed to mitigate a hypervisor flaw that could let guest code affect the host.
Incorrect Answers
A:Guest UEFI verification validates signed boot artifacts independently of the physical server's startup chain; the outcome it supports is to reject unauthorized guest boot components after a template change, whereas this scenario asks defenders to mitigate a hypervisor flaw that could let guest code affect the host.
C:A virtual TPM supplies guest cryptographic capabilities but its state must be protected during host migration and backup; it could help someone trying to support measured startup and protected guest encryption keys, but the problem is instead to mitigate a hypervisor flaw that could let guest code affect the host.
D:Controlled templates reduce inconsistent settings across newly created workloads; that is useful when the task is to provision servers from a repeatedly tested hardened baseline, not the stated requirement to mitigate a hypervisor flaw that could let guest code affect the host.
Question 554
A cloud tenant is concerned that a compromised virtualization host could inspect plaintext contents of a running guest. The hardware and hypervisor explicitly support confidential virtual machines. Which protection is designed to restrict host-level access to guest memory?
- Hardware-backed confidential VM memory encryption
- Virtual machine secure boot
- Virtual disk encryption at rest
- Routine hypervisor patch scheduling
Explanation
Correct Answer
A:Confidential VM technology uses supported hardware-backed memory protection to restrict the host from reading guest memory in plaintext. Deployment requires compatible hardware, hypervisor support, and the appropriate confidential VM configuration.
Incorrect Answers
B:Virtual machine secure boot evaluates boot-component trust before guest operating-system startup. It does not independently stop a privileged host from inspecting the runtime plaintext memory of an ordinary guest.
C:Virtual disk encryption protects guest data stored on virtual disks or storage media. It cannot alone prevent a compromised host from observing decrypted bytes in a running virtual machine’s memory.
D:Patching the hypervisor reduces exploitation of known vulnerabilities and is important defense in depth. It does not deliver the specific hardware-enforced runtime memory isolation requested in the scenario.
Question 555
To support measured startup and protected guest encryption keys, what is the most direct option?
- Type-1 hypervisor hardening
- Virtual TPM enablement
- VM snapshot governance
- Virtual machine secure boot
- Virtual disk encryption
Explanation
Correct Answer
B:A virtual TPM supplies guest cryptographic capabilities but its state must be protected during host migration and backup; its relevant protective or investigative effect is to support measured startup and protected guest encryption keys.
Incorrect Answers
A:Bare-metal virtualization hosts require restricted management, timely updates and minimized optional services; the technique works for situations involving reduce attack exposure on hosts running many production virtual machines, rather than this need to support measured startup and protected guest encryption keys.
C:Snapshots may include secrets and outdated vulnerable states and should have bounded retention and access; the outcome it supports is to avoid preserving sensitive machine state indefinitely in rollback images, whereas this scenario asks defenders to support measured startup and protected guest encryption keys.
D:Guest UEFI verification validates signed boot artifacts independently of the physical server's startup chain; although relevant to reject unauthorized guest boot components after a template change, it does not by itself achieve the required task to support measured startup and protected guest encryption keys.
E:Encrypting virtual storage addresses offline image disclosure when keys and backups are protected; it could help someone trying to protect VM image files removed from shared hypervisor storage, but the problem is instead to support measured startup and protected guest encryption keys.
Question 556
To provision servers from a repeatedly tested hardened baseline, what should defenders select?
- Hypervisor patch scheduling
- VM snapshot governance
- VM escape patching
- Golden VM images
Explanation
Correct Answer
D:Controlled templates reduce inconsistent settings across newly created workloads; the requested outcome is precisely to provision servers from a repeatedly tested hardened baseline.
Incorrect Answers
A:Maintenance-mode migration and capacity planning let supported workloads move before a host is serviced; it addresses the different need to update virtualization hosts without unnecessary application interruption, leaving the requested ability to provision servers from a repeatedly tested hardened baseline unresolved.
B:Snapshots may include secrets and outdated vulnerable states and should have bounded retention and access; the technique works for situations involving avoid preserving sensitive machine state indefinitely in rollback images, rather than this need to provision servers from a repeatedly tested hardened baseline.
C:Maintaining the virtualization layer protects a trust boundary not enforced by guest antivirus alone; its mechanism supports mitigate a hypervisor flaw that could let guest code affect the host, while the requested control must be able to provision servers from a repeatedly tested hardened baseline.
Question 557
To avoid preserving sensitive machine state indefinitely in rollback images, which mechanism best fits?
- Hypervisor patch scheduling
- VM console privilege
- VM snapshot governance
- Golden VM images
Explanation
Correct Answer
C:Snapshots may include secrets and outdated vulnerable states and should have bounded retention and access; this choice fits the scenario because the team must avoid preserving sensitive machine state indefinitely in rollback images.
Incorrect Answers
A:Maintenance-mode migration and capacity planning let supported workloads move before a host is serviced; applying it would serve update virtualization hosts without unnecessary application interruption without directly satisfying the goal to avoid preserving sensitive machine state indefinitely in rollback images.
B:Console access may bypass ordinary network login paths and warrants stronger role separation; it addresses the different need to restrict who can open a hypervisor console to sensitive guests, leaving the requested ability to avoid preserving sensitive machine state indefinitely in rollback images unresolved.
D:Controlled templates reduce inconsistent settings across newly created workloads; its mechanism supports provision servers from a repeatedly tested hardened baseline, while the requested control must be able to avoid preserving sensitive machine state indefinitely in rollback images.
Question 558
To update virtualization hosts without unnecessary application interruption and to restrict who can open a hypervisor console to sensitive guests, which TWO measures should the defender select? Choose TWO.
- Virtual host log forwarding
- Hypervisor patch scheduling
- Virtual machine secure boot
- VM snapshot governance
- VM console privilege
Explanation
Correct Answers
B:Maintenance-mode migration and capacity planning let supported workloads move before a host is serviced; this is the measure that can update virtualization hosts without unnecessary application interruption as one of the separately stated outcomes.
E:Console access may bypass ordinary network login paths and warrants stronger role separation; this is the measure that can restrict who can open a hypervisor console to sensitive guests as one of the separately stated outcomes.
Incorrect Answers
A:Off-host logs record administrative sessions and policy changes beyond guest operating-system events; its operational purpose is to preserve management actions during a compromised virtualization-host investigation, not to achieve the specific requirement to update virtualization hosts without unnecessary application interruption and to restrict who can open a hypervisor console to sensitive guests.
C:Guest UEFI verification validates signed boot artifacts independently of the physical server's startup chain; it addresses the different need to reject unauthorized guest boot components after a template change, leaving the requested ability to update virtualization hosts without unnecessary application interruption and to restrict who can open a hypervisor console to sensitive guests unresolved.
D:Snapshots may include secrets and outdated vulnerable states and should have bounded retention and access; the technique works for situations involving avoid preserving sensitive machine state indefinitely in rollback images, rather than this need to update virtualization hosts without unnecessary application interruption and to restrict who can open a hypervisor console to sensitive guests.
Question 559
To restrict who can open a hypervisor console to sensitive guests, what control should be selected?
- Golden VM images
- Virtual host log forwarding
- VM console privilege
- Virtual TPM enablement
Explanation
Correct Answer
C:Console access may bypass ordinary network login paths and warrants stronger role separation; it supplies the specific control needed to restrict who can open a hypervisor console to sensitive guests.
Incorrect Answers
A:Controlled templates reduce inconsistent settings across newly created workloads; a team would select it to provision servers from a repeatedly tested hardened baseline, which does not provide the particular result to restrict who can open a hypervisor console to sensitive guests.
B:Off-host logs record administrative sessions and policy changes beyond guest operating-system events; its operational purpose is to preserve management actions during a compromised virtualization-host investigation, not to achieve the specific requirement to restrict who can open a hypervisor console to sensitive guests.
D:A virtual TPM supplies guest cryptographic capabilities but its state must be protected during host migration and backup; it addresses the different need to support measured startup and protected guest encryption keys, leaving the requested ability to restrict who can open a hypervisor console to sensitive guests unresolved.
Question 560
To protect VM image files removed from shared hypervisor storage, which security control is most appropriate?
- Hypervisor patch scheduling
- VM snapshot governance
- Virtual disk encryption
- VM console privilege
- Virtual host log forwarding
Explanation
Correct Answer
C:Encrypting virtual storage addresses offline image disclosure when keys and backups are protected; that is why it addresses the operational task to protect VM image files removed from shared hypervisor storage.
Incorrect Answers
A:Maintenance-mode migration and capacity planning let supported workloads move before a host is serviced; that is useful when the task is to update virtualization hosts without unnecessary application interruption, not the stated requirement to protect VM image files removed from shared hypervisor storage.
B:Snapshots may include secrets and outdated vulnerable states and should have bounded retention and access; a team would select it to avoid preserving sensitive machine state indefinitely in rollback images, which does not provide the particular result to protect VM image files removed from shared hypervisor storage.
D:Console access may bypass ordinary network login paths and warrants stronger role separation; applying it would serve restrict who can open a hypervisor console to sensitive guests without directly satisfying the goal to protect VM image files removed from shared hypervisor storage.
E:Off-host logs record administrative sessions and policy changes beyond guest operating-system events; it addresses the different need to preserve management actions during a compromised virtualization-host investigation, leaving the requested ability to protect VM image files removed from shared hypervisor storage unresolved.