Pass the VMware VMware Certified Specialist - Cloud Foundation 2023 5V0-31.22 Questions and answers with CertsForce

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.

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-1B136277-E46C-41FC-9C8C-3E78E9B97F5C.html

vSphere with Tanzu uses the First Class Disk (FCD) type of virtual disks to back persistent volumes. FCD, also known as Improved Virtual Disk, is a named virtual disk not associated with a VM. FCDs are identified by UUID and can be managed independently of VMs.

Thick provisioned VMDK, Raw Device Mapping (RDM), and Virtual Volumes (vVOLs) are not used as the backing disks for persistent volumes in vSphere with Tanzu.

The references are:

Using Persistent Storage in vSphere with Tanzu, section “Persistent Volume”

vSphere with Tanzu Storage, section “First Class Disk”

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-2C4653EB-5654-45CB-B072-2C2E29CB6C89.html

According to the VMware Cloud Foundation Specialist (v2) exam guide1, one of the objectives is to “Identify the supported storage types for VMware Cloud Foundation”.

According to the VMware Cloud Foundation Design Guide2, the supported storage types for VI workload domains are vSAN, vVols, NFS v3, and VMFS on FC as principal storage, and vSAN, vVols, NFS v3 and v4.1, iSCSI, and NVMeoF/TCP as supplemental storage.

Therefore, when deploying an additional cluster within a VI workload domain that has been created with vSAN as a principal storage, the administrator can choose any of the supported principal storage types for the new cluster.

The only option that contains only valid principal storage types is D. vVols, vSAN, NFS v3, VMFS on FC.

References:

1: VMware Cloud Foundation Specialist (v2) Exam Guide 2: Supported Storage Types for VMware Cloud Foundation

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/com.vmware.vcf.vxrail.doc/GUID-D6271E5A-05E9-4AE1-A3CE-87820DC3001B.html

The option that should be enabled in the Planning and Preparation Workbook to address this issue is C. Identity and Access Management for VMware Cloud Foundation. According to the VMware Cloud Foundation documentation1, Identity and Access Management for VMware Cloud Foundation is a prerequisite for deploying Developer Ready Infrastructure using VMware Cloud Foundation. Identity and Access Management for VMware Cloud Foundation provides a centralized identity and access management service for the SDDC components and workloads, using Workspace ONE Access as the identity provider. If this option is not enabled in the Planning and Preparation Workbook, the Developer Ready Infrastructure using VMware Cloud Foundation option will be excluded and display an error.

A. Stretched Cluster for Management Domain is not a correct option, because it is not related to the deployment of Developer Ready Infrastructure using VMware Cloud Foundation. Stretched Cluster for Management Domain is an optional feature that allows you to stretch the management domain across two availability zones for high availability and disaster recovery purposes2

B. Clustered Workspace ONE Access is not a correct option, because it is not required for deploying Developer Ready Infrastructure using VMware Cloud Foundation. Clustered Workspace ONE Access is an optional feature that allows you to deploy a highly available Workspace ONE Access instance using vRealize Suite Lifecycle Manager. This feature is only available when Identity and Access Management for VMware Cloud Foundation is enabled3

D. Stretched Cluster for Workload Domain is not a correct option, because it is not related to the deployment of Developer Ready Infrastructure using VMware Cloud Foundation. Stretched Cluster for Workload Domain is an optional feature that allows you to stretch a VI workload domain across two availability zones for high availability and disaster recovery purposes4

References: 1: Deploying Application Virtual Networks in VMware Cloud Foundation 2: Deploying Stretched Clusters in VMware Cloud Foundation 3: VMware Cloud Foundation Design for vRealize Suite Lifecycle and Access Management 4: Deploying Stretched Clusters in VMware Cloud Foundation

This configuration will support two host failures by using RAID-6 (Erasure Coding), which creates two parity segments for each data segment. It will use the least amount of hosts among the options, because RAID-6 requires a minimum of six hosts for FTT=2. It will also minimize storage capacity usage, because RAID-6 uses less disk space than RAID-1 (Mirroring), which creates a full copy of each data segment12

A. 6 Hosts, FTT=2, RAID 1 is not a correct option, because it will not minimize storage capacity usage. RAID-1 will use more disk space than RAID-6, because it will create three copies of each data segment for FTT=212

C. 5 Hosts, FTT=2, RAID 5/6 is not a correct option, because it will not support two host failures. RAID-5 requires a minimum of four hosts for FTT=1, and RAID-6 requires a minimum of six hosts for FTT=2. With five hosts, neither RAID-5 nor RAID-6 can tolerate two host failures12

D. 5 Hosts, FTT=2, RAID 1 is not a correct option, because it will not support two host failures or minimize storage capacity usage. RAID-1 requires a minimum of five hosts for FTT=2, but it also requires an additional host as a witness to maintain quorum. Therefore, with five hosts, RAID-1 can only tolerate one host failure. Moreover, RAID-1 will use more disk space than RAID-6, because it will create three copies of each data segment for FTT=212

References: 1: Availability Attributes for vSAN VM Storage Policies - VMware Docs 2: Planning Capacity in vSAN - VMware Docs

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-A56D8E59-A549-4624-BC61-4A92710F9FA1.html

You should remediate the password. That option is used to sync password that were changed directly on component product managed by SDDC manager. https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-92E16E2F-9053-4BBA-9BF9-7B5065C680CF.html

According to the VMware Cloud Foundation documentation1, if you change the password of a service directly on the service node, you must remediate the password in SDDC Manager to update the password in the SDDC Manager database. This ensures that SDDC Manager can continue to manage the service and perform operations such as patching and upgrading. To remediate the password, you need to select the service from the Password Rotation page, click Remediate, and enter the new password.

Manually changing the password in SDDC Manager using the “Update” button is not a valid option, because there is no such button on the Password Rotation page. The only buttons available are Rotate Now, Schedule Rotation, and Remediate1

Scheduling the password rotation in SDDC Manager in the next five minutes using the “Schedule Rotation” button is not a recommended option, because it will change the password again and may cause service disruption. The Schedule Rotation button allows you to set a date and time for rotating the passwords of one or more services automatically1

Rotating the password in SDDC Manager using the “Rotate Now” button is also not a recommended option, because it will change the password again and may cause service disruption. The Rotate Now button allows you to rotate the passwords of one or more services immediately1

References: 1: Rotate Passwords - VMware Cloud Foundation Administration Guide

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-design/GUID-2156EC66-BBBB-4197-91AD-660315385D2E.html

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.

Explanation: 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.