VMware Cloud Foundation Specialist (v2) 5V0-31.22 Exam Questions

Answer : A

This is because according to VMware documentation3, developers can only access Kubernetes storage classes that are mapped from VM Storage Policies. They cannot modify or delete them.

Answer : B, C

This is because vSphere Lifecycle Manager images can include firmware updates and third-party software components that can be applied to all hosts in a cluster12.These options are only available when using vSphere Lifecycle Manager images, not when using vSphere Lifecycle Manager baselines2.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-9A112231-AD7C-4EF5-AB6A-A8DAA704D307.html

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-9A20C2DA-F45F-4C9B-9D17-A89BCB62E6EF.html

Answer : B

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-lifecycle/GUID-E101AFB5-1034-4CF9-B96E-A2E70DCF02F5.html

SDDC Manager and VMware Cloud Foundation services. This step upgrades the SDDC Manager software and the VMware Cloud Foundation services that run on the management domain controller VMs. SeeUpgrade VMware Cloud Foundation Software.

vRealize Suite products. This step upgrades the vRealize Suite Lifecycle Manager and the vRealize Suite products that are deployed and managed by it, such as vRealize Automation, vRealize Operations Manager, and vRealize Log Insight. SeeUpgrade vRealize Suite Lifecycle Manager and vRealize Suite Products.

NSX-T Data Center. This step upgrades the NSX-T Data Center software that provides network virtualization and security for the management domain. SeeUpgrade NSX-T Data Center.

vCenter Server. This step upgrades the vCenter Server software that manages the ESXi hosts and VMs in the management domain. See [Upgrade vCenter Server].

ESXi servers. This step upgrades the ESXi software that runs on the physical servers in the management domain. See [Upgrade ESXi].

Answer : B, D

To expand storage capacity in a vSAN cluster with one disk group, you can either add more drives to hosts in the cluster, which is commonly referred to as scaling up, or add capacity drives to existing disk groups

Option B: Add an additional disk group - According to search result [1], adding additional drives to a host will increase both capacity and performance [1], and each disk group contains one flash cache device and one or multiple capacity devices for persistent storage [2]. Therefore, adding an additional disk group to each host would increase the storage capacity of the vSAN cluster.

Option D: Increase the number of capacity disks in the existing disk group - Search result [1] explains that vSAN clusters require capacity and cache devices to function, and each disk group can contain multiple capacity devices for persistent storage [2]. Thus, an additional way to expand storage capacity in the vSAN cluster would be to increase the number of capacity disks in the existing disk group.

A disk group is a collection of one or more flash-based cache devices and one or more capacity devices that provide storage capacity for a vSAN cluster. A vSAN cluster can have multiple disk groups, and each disk group can have a different configuration.

To expand storage capacity in a vSAN cluster where each host currently has only one disk group, the administrator can add an additional disk group or increase the number of capacity disks in the existing disk group.

Adding an additional disk group involves adding more disks to the host and creating a new disk group. This approach can provide additional capacity and performance benefits, as the new disk group can be configured with different settings to optimize performance and capacity.

Increasing the number of capacity disks in the existing disk group involves adding more capacity devices to the existing disk group. This approach can provide additional capacity, but may not necessarily provide performance benefits as the existing disk group may already be fully utilized.

VMware vSAN 7.0 Design and Sizing Guide: https://storagehub.vmware.com/t/vmware-vsan/vmware-vsan-7-0-design-and-sizing-guide-2/

VMware vSAN Documentation: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-9B7C9685-64C5-49C2-8E3C-CC2E47AFBC6F.html

Answer : B, C, F

This is because according to VMware documentation2, these are some of the prerequisites for enabling workload management for a VMware Cloud Foundation Management Workload Domain:

You must have a vSphere cluster with NSX-T networking configured.

You must have vSAN File Services enabled on your cluster.

You must have vSphere HA and DRS enabled in fully automated mode on your cluster.

The other options are incorrect because they are not required or supported for this deployment.

https://docs.vmware.com/en/VMware-Harbor-Registry/services/vmware-harbor-registry/GUID-index.html

Answer : A

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-lifecycle/GUID-3B41CF79-C721-4AFC-A263-0672143DF41E.html

Answer : A

This is because according to VMware documentation1, these are the steps to replace a failed host in a stretched cluster:

Run the compact cluster API to remove any stale data from vSAN.

Decommission the host to be removed using SDDC Manager UI or API.

Commission the replacement host to the same network pool as the removed host using SDDC Manager UI or API.

Add the newly commissioned host to the cluster using SDDC Manager UI or API.

According to the VMware documentation, when replacing a failed host in a stretched cluster, the first step is to decommission the failed host. This should be followed by removing the host using cluster APIs, commissioning the new host with the correct network, and then adding the newly commissioned host to the cluster using cluster APIs.