2V0-621 · Question #26
An administrator has been instructed to secure existing virtual machines in vCenter Server. Which two actions should the administrator take to secure these virtual machines? (Choose two.)
The correct answer is B. Restrict Remote Console access D. Prevent use of Independent Non-Persistent virtual disks. Securing existing VMs requires restricting Remote Console access to reduce attack surface and preventing Independent Non-Persistent disks to preserve audit logs and security patches.
Question
An administrator has been instructed to secure existing virtual machines in vCenter Server. Which two actions should the administrator take to secure these virtual machines? (Choose two.)
Options
- ADisable native remote management services
- BRestrict Remote Console access
- CUse Independent Non-Persistent virtual disks
- DPrevent use of Independent Non-Persistent virtual disks
How the community answered
(30 responses)- A17% (5)
- B73% (22)
- C10% (3)
Why each option
Securing existing VMs requires restricting Remote Console access to reduce attack surface and preventing Independent Non-Persistent disks to preserve audit logs and security patches.
Disabling native remote management services is a guest OS-level hardening task, not a vCenter VM security action, and can break legitimate administrative access without being managed through vSphere security policies.
Restricting Remote Console access limits who can interact directly with a VM's console through vCenter, reducing the risk of unauthorized guest OS access via the management plane. This is a VMware security hardening guideline that prevents console-based attacks even when network-level controls are in place.
Using Independent Non-Persistent virtual disks introduces a security risk because all disk changes - including installed patches and logged activity - are wiped on reboot, making it trivial to hide malicious activity and destroying forensic evidence.
Independent Non-Persistent disks discard all changes when a VM is powered off or reset, meaning security patches, audit logs, and forensic evidence are permanently destroyed on each reboot. Preventing their use ensures that VM state is preserved, maintaining the integrity of security controls and compliance records on machines handling sensitive data.
Concept tested: Virtual machine security hardening best practices in vSphere
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-397FAB4B-4B72-4B3B-86EE-E11F6FAEEB5E.html
Topics
Community Discussion
No community discussion yet for this question.