5V0-31-23 Sample Questions & Answers

VMware Cloud Foundation automates vSAN configuration during workload domain creation. To control which devices are used for cache and capacity, the administrator must assign specific tags to the disks during the host commissioning phase before creating the workload domain. By tagging the NVMe devices with the 'cache' tag and SSDs with the 'capacity' tag, the administrator instructs the SDDC Manager automation to build the vSAN disk groups according to this specification.

The correct VCF upgrade sequence is critical to maintain stability. The process always begins with upgrading the orchestrator, which is the SDDC Manager itself. After the SDDC Manager is updated, the administrator must upgrade the Management Domain's components in a specific order (typically NSX, then vCenter, then ESXi). Only after the entire Management Domain is successfully upgraded can the administrator proceed to upgrade the VI Workload Domains, which should be done sequentially (one after the other), not concurrently.

The purpose of a vSAN Witness in a stretched cluster is to act as a tie-breaker in the event of a network partition between the two main sites (availability zones). To fulfill this role, it must reside in a third failure domain, completely independent of the two sites it is monitoring. Placing it in either of the two main sites or even the Management Domain (if it resides in one of the main sites) would defeat its purpose, as it would be lost during a site failure.

For disconnected VCF environments, VMware provides the LCM (Lifecycle Management) Bundle Transfer Utility. This command-line tool is run on an internet-connected machine to download the necessary upgrade bundles from the VMware depot. The downloaded bundles are then transferred to the air-gapped SDDC Manager, where they can be used for the offline upgrade process.

This design has a fundamental flaw. A core requirement in VCF is that all VI Workload Domains that share a single NSX Manager instance must use the same vSphere Lifecycle Manager update method. Since WLD1 uses vLCM Images, WLD2 must also use vLCM Images to share its NSX Manager. The requirement to use vLCM Baselines for WLD2 makes the proposed resource-sharing plan invalid. The administrator must either deploy a dedicated NSX Manager for WLD2 or change WLD2 to use vLCM Images.

The correct procedure in VMware Cloud Foundation is to use the 'Commission Host' workflow within the SDDC Manager UI. This process discovers the host on the network, runs a series of validation checks against VCF requirements (e.g., hardware, software version, networking), and prepares it by installing necessary agents. Once commissioned, the host is placed into a 'free pool' of unassigned hosts, ready to be added to any workload domain or cluster.

The SoS (Supportability and Serviceability) utility is the designated tool in VCF for troubleshooting and log collection. By running specific commands from the SDDC Manager appliance's command line, an administrator can perform health checks and generate comprehensive log bundles. The tool is designed to collect logs not only from the SDDC Manager itself but also from the other integrated components it manages, such as vCenter Servers and NSX Managers, into a single, consolidated archive for support.

The VMware Cloud Builder appliance has a single, specific purpose: to perform the initial deployment, or 'bring-up,' of the VCF Management Domain. It takes a configuration file (JSON or Excel) as input, validates the environment, and then automates the deployment and configuration of ESXi, vCenter, NSX, and SDDC Manager. Once the bring-up is complete and SDDC Manager is running, the Cloud Builder's primary job is done, and it is typically decommissioned.

This statement is true. SDDC Manager provides centralized password management for all components under its control, including ESXi hosts. This functionality is available through both the UI and the REST API. An administrator can trigger a password rotation task for all hosts within a specific domain or cluster, which is a critical security and compliance feature.

The process of deleting a VI Workload Domain in SDDC Manager is destructive. It decommissions the hosts, destroys the vSAN datastore, and removes the vCenter and NSX configurations for that domain. The workflow does NOT include any automatic migration of workloads. It is the administrator's explicit responsibility to manually migrate or shut down and back up any virtual machines they wish to preserve before starting the deletion process. The workflow will fail if it detects running VMs.