Free VMware 5V0-31.22 Practice Exam with Questions & Answers

These are valid use cases for multiple clusters in a workload domain according to VMware documentation. A workload domain with multiple availability zones each containing clusters can provide high availability and disaster recovery by distributing workloads across different physical locations within a region. A workload domain with multiple clusters in one rack can provide scalability and flexibility by allowing different configurations and policies for different clusters within a single logical unit. Two clusters forming one stretched workload domain can provide resiliency and fault tolerance by synchronizing data across two sites within a region.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.3/vcf-lifecycle/GUID-BB15EADE-DCD3-4D51-824E-124C9B364D20.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-management-domain-design/GUID-11177D00-C8BE-4CEC-B997-659CC03B6D12.html

According to the VMware KB article Understand vMotion networking requirements (59232), a successful Long Distance vMotion requires a RTT (round-trip time) latency of 150 milliseconds or less, between hosts. This is the maximum accepted latency supported by vMotion across long distances1

An architect is decommissioning a host from a VI Workload Domain and wants to reuse it in a VMware Cloud Foundation environment.

Which statement accurately describes this process?

A. Use the decommission host workflow against a host with an unassigned state, and then run the commission host workflow.

B. Use the decommission host workflow against a host with an unassigned state, re-image the host, and then run the commission host workflow.

C. Use the decommission host workflow against a host with an assigned state, re-image the host, and then run the commission host workflow.

D. Use the decommission host workflow against a host with an assigned state, and then run the commission host workflow.

Answer: B

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-2C3E06BA-7B77-4F4B-958C-1BFCB3E9CBA7.html Removing hosts from the SDDC Manager inventory is called decommissioning. If you want to re-use a host in a different workload domain, you must decommission, re-image, and commission the host before adding it to the workload domain. The hosts that you want to decommission must not be assigned to a workload domain. If a host is assigned to a workload domain, you must remove it before you can decommission it. See Remove a Host from a vSphere Cluster in a Workload Domain.

Use the decommission host workflow against a host with an unassigned state, re-image the host, and then run the commission host workflow. According to the VMware Cloud Foundation documentation1, removing hosts from the SDDC Manager inventory is called decommissioning. If you want to re-use a host in a different workload domain, you must decommission, re-image, and commission the host before adding it to the workload domain. The hosts that you want to decommission must not be assigned to a workload domain. If a host is assigned to a workload domain, you must remove it before you can decommission it.

References: 1: Decommission Hosts - VMware Docs

This is because VIA service uses PXE boot to install ESXi on the servers, and it requires onboard NICs to be enabled and connected to an untagged VLAN/Network1.

According to VMware documentation on VMware Imaging Appliance, when preparing a host for imaging using VIA, it is recommended to enable the onboard NICs on the server. This enables the network adapter to participate in the boot sequence of the host to retrieve the image from the Imaging Appliance.

Here is the relevant quote from the documentation:

"To prepare the host, ensure that the onboard NICs are enabled on the server. During boot up, the server firmware detects the network adapter and adds it to the boot sequence list so that it can participate in network boot."

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-deploy/GUID-735928E5-1DD7-44E5-BE32-E598230326AD.html

This is because according to VMware documentation, this is what an administrator must register as an external component to complete this task of configuring scheduled backups for the SDDC Manager. SFTP server is one of the supported backup targets for SDDC Manager backups. The administrator can register an SFTP server by navigating to the SDDC Manager UI > Administration > Backup > Site Settings and clicking Register External.

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-177C23C4-ED81-4ADD-89A2-61654C18201B.html

According to the VMware Cloud Foundation documentation1, the prerequisites for creating a vSphere Namespace are:

• Configure a cluster with vSphere with Tanzu. This is the first step to enable Workload Management on a vSphere cluster and create a Kubernetes management cluster known as a Supervisor Cluster2
• Create storage policies for persistent storage. Storage policies can define different types and classes of storage, for example, gold, silver, and bronze. They are used to specify the storage requirements for the vSphere Namespace and the workloads that run on it1

A. Define CPU and Memory limits is not a correct option, because it is not a prerequisite for creating a vSphere Namespace, but a configuration option that can be done after creating the namespace. CPU and Memory limits are used to specify the resource allocation for the vSphere Namespace and the workloads that run on it1

D. Enable Harbor Image Registry is not a correct option, because it is not a prerequisite for creating a vSphere Namespace, but an optional feature that can be enabled after creating the namespace. Harbor Image Registry is an embedded container registry that provides secure image management for the Supervisor Cluster and Tanzu Kubernetes clusters. It is only available when using NSX-T networking for the Supervisor Cluster3

E. Assign user and groups access is not a correct option, because it is not a prerequisite for creating a vSphere Namespace, but a configuration option that can be done after creating the namespace. User and group access are used to specify the permissions for the vSphere Namespace and the workloads that run on it1

References: 1: Create and Configure a vSphere Namespace - VMware Docs 2: Prerequisites for Configuring vSphere with Tanzu on a vSphere Cluster - VMware Docs 3: Harbor Registry Overview - VMware Docs

A Tanzu Basic license is required to enable Workload Management on VMware Cloud Foundation. Once enabled, the Supervisor Cluster must be assigned a Tanzu license before the 60-day evaluation period expires. This license can be added to the license inventory of vSphere if a valid Tanzu Edition license is available.

"You can remove NSX Edge nodes from an NSX Edge Cluster that you created with SDDC Manager if you need to scale down to meet business needs.

Prerequisites

-The NSX Edge cluster must be available in the SDDC Manager inventory and must be Active.

-The NSX Edge node must be available in the SDDC Manager inventory.

-The NSX Edge cluster must be hosted on one or more vSphere clusters from the same workload domain.

-The NSX Edge cluster must contain more than two NSX Edge nodes.

-The NSX Edge cluster must not be federated or stretched.

-If the NSX Edge cluster was deployed with a Tier-0 Service High Availability of Active-Active, the NSX Edge cluster must contain two or more NSX Edge nodes with two or more Tier-0 routers (SR component) after the NSX Edge nodes are removed.

-If selected edge cluster was deployed with a Tier-0 Service High Availability of Active-Standby, you cannot remove NSX Edge nodes that are the active or standby node for the Tier-0 router."

These three statements accurately answer the manager’s question about NSX Edge nodes. Here is a brief explanation for each statement:

• B. They can only be removed if the NSX Edge cluster is available in the SDDC Manager inventory and is active. This is a prerequisite for removing NSX Edge nodes from an NSX Edge cluster using SDDC Manager. If the NSX Edge cluster is not available or not active, you cannot remove NSX Edge nodes from it1
• C. They can only be removed if the NSX Edge cluster is not stretched. This is another prerequisite for removing NSX Edge nodes from an NSX Edge cluster using SDDC Manager. If the NSX Edge cluster is stretched across different sites, you cannot remove NSX Edge nodes from it using SDDC Manager. You need to use the VMware Cloud Foundation NSX-T Edge Cluster Deployment Removal Tool instead12
• E. They can only be removed if the NSX Edge node is available in the SDDC Manager inventory. This is also a prerequisite for removing NSX Edge nodes from an NSX Edge cluster using SDDC Manager. If the NSX Edge node is not available in the SDDC Manager inventory, you cannot remove it using SDDC Manager. You need to delete it from the NSX-T Manager UI instead13

A. They can be removed at any time if they are in a powered-off state. This is not a correct statement, because powering off the NSX Edge nodes does not affect their removal process using SDDC Manager. You can remove NSX Edge nodes that are powered on or powered off, as long as they meet the other prerequisites1

D. They can be removed if there are at least two nodes in the NSX Edge cluster. This is not a correct statement, because the minimum number of nodes in an NSX Edge cluster depends on the Tier-0 service high availability mode that was selected during the deployment. If the mode was Active-Active, you need at least two nodes in the NSX Edge cluster after removing any nodes. If the mode was Active-Standby, you need at least one node in the NSX Edge cluster after removing any nodes1

F. They can only be removed if the NSX Edge node was deployed from NSX-T Manager directly. This is not a correct statement, because the question is about removing NSX Edge nodes that were deployed using SDDC Manager, not NSX-T Manager directly. If the NSX Edge node was deployed from NSX-T Manager directly, you cannot remove it using SDDC Manager, but you can delete it from the NSX-T Manager UI.

References: 1: Remove Edge Nodes from an NSX Edge Cluster - VMware Docs 2: VMware Cloud Foundation NSX-T Edge Cluster Deployment Removal Tool (78635) | VMware KB 3: Delete the Failed NSX Edge Node from the NSX Manager Cluster - VMware Docs

This is because according to VMware documentation5, this is the tool that an administrator should use for verifying the operation of SDDC Manager after restoring it from a file-based backup. The SoS tool can run various tests and checks on SDDC Manager and its components to ensure their health and functionality.

https://docs.vmware.com/en/VMware-Validated-Design/6.0.1/sddc-backup-and-restore/GUID-39E9509F-D7BB-4601-9DF8-C44147B2B007.html#:~:text=After%20a%20successful%20restore%20of%20SDDC%20Manager%2C%20you%20must%20validate%20the%20SDDC%20Manager%20state.%20You%20run%20the%20health%20checks%20by%20using%20the%20sos%20tool .

 This is because when deploying a stretched cluster in a VMware Cloud Foundation environment, you must ensure that:

• The vSAN network, the host overlay network and the vMotion network are stretched across both availability zones12. These networks enable data replication, communication and migration between hosts in different sites.
• The host overlay network has DHCP enabled to provide IP addresses to hosts1. This simplifies the configuration and management of hosts in different sites.
• Each vSAN stretched cluster has one witness host deployed in a separate location from both availability zones12. The witness host acts as a tie-breaker in case of a site failure or split-brain scenario.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-7B4CC729-20BD-4CC9-B855-B38F02F74D40.html