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

This is because according to VMware documentation, these are some of the storage options that can be used for a new VI Workload Domain:

vSAN principal storage with VMFS on FC supplemental storage: You can use vSAN as your primary storage platform and add VMFS on FC as an additional storage option.

vSAN principal storage with NFS supplemental storage: You can use vSAN as your primary storage platform and add NFS as an additional storage option.

https://infohub.delltechnologies.com/l/dell-storage-with-vmware-cloud-foundation-1/principal-and-supplemental-storage-for-workload-domains-1

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

The NSX Manager is a standalone appliance that hosts the API services, the management plane, control plane, and policy management. As a result of this combined format, you no longer need to install the manager and controllers as separate VMs.  The NSX Manager has three built-in roles: policy, manager, and controller  1 .

B. Policy: NSX Manager is responsible for the creation and management of NSX-T policies, which are used to define networking and security configurations and rules.

C. Controller: NSX Manager also serves as a central management point for NSX-T controllers, which are responsible for implementing and enforcing networking and security policies across the NSX-T environment.

References:

VMware Cloud Foundation Specialist (v2) Exam Guide, section 2.2

NSX-T Data Center Administration Guide, section " NSX Manager and NSX-T Controllers "

https://shuttletitan.com/nsx-t/nsx-t-management-cluster-benefits-roles-ccp-sharding-and-failure-handling/

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

According to the VMware Cloud Foundation documentation 1 , vVols supports FC, NFS, and iSCSI storage protocol types for principal storage. These are the protocols that are supported for the new commissioned hosts that will be used for the VI workload domain.

SCSI, FCoE, and SAS are not supported storage protocols for vVols in VMware Cloud Foundation.

References :  1 : vVols Storage with VMware Cloud Foundation

This is because according to VMware documentation, this is one of the supported design options for deploying NSX-T Bare Metal Edge nodes for VMware Cloud Foundation VI workload domains. Sharing an NSX-T Manager cluster between both workload domains can reduce costs by minimizing the number of NSX-T licenses required. Adding the NSX-T Bare Metal Edge cluster to the shared NSX-T Manager cluster can satisfy a requirement for extremely low latency by providing direct access to physical network interfaces.

According to VMware Cloud Foundation Specialist (v2) Exam 1 , one of the objectives is to “Describe how to expand an existing NSX-T Edge cluster”. The exam guide also states that “SDDC Manager provides a single point of management for password rotation” and that “password rotation must be performed through SDDC Manager”.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-E9D93C0C-646C-4F75-95CB-D8AE6DB99618.html

This is because according to VMware documentation 5 , 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 .

See ' Figure 25. Configure Cloud Builder validation ' at https://infohub.delltechnologies.com/l/dell-poweredge-mx-deployment-with-vmware- cloud-foundation-deployment-guide/vmware-cloud-builder-configuration-validation https://my-cloudy-world.com/2021/05/28/vmware-cloud-builder-bringup-validation-tasks/

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-Cloud-Foundation/4.3/vcf-lifecycle/GUID-8FA44ACE-8F04-47DA-845E-E0863094F7B0.html

The administrator can follow these steps to download the latest VCF software bundles:

Download the latest bundle transfer utility from myvmware.com.  This is a tool that allows you to download the bundles from the VMware depot and upload them to the SDDC Manager appliance 1

Use the utility to download the latest software bundles for the upgrade. You need to specify the version to which you are upgrading and provide your VMware Customer Connect credentials.  The utility will verify the file size and checksum of the downloaded bundles 1

Copy the bundles to SDDC manager using file sharing. You can use SCP or SFTP to transfer the bundles from your laptop to the SDDC Manager appliance.  You need to upload the manifest file first, which is a metadata file that contains information about the VMware product versions included in the release Bill of Materials 1

References :  1 : Offline Bundle Download for VMware Cloud Foundation

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. See  Upgrade 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. See  Upgrade 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. See  Upgrade 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].

This is because according to VMware documentation 1 , the VMware Imaging Appliance (VIA) is a tool that automates ESXi host imaging and configuration for VCF deployments.  It supports custom ESXi images that include additional drivers or VIBs that are not part of the base ESXi image 2 .  You can download ESXi software and VIBs from VMware or third-party sources and upload them to VIA for creating custom images 3 .

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 cluster 1 2 .  These options are only available when using vSphere Lifecycle Manager images, not when using vSphere Lifecycle Manager baselines 2 .

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

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-177C23C4-ED81-4ADD-89A2-61654C18201B.html#:~:text=be%20in%20a-,DNS%2Dcompliant,-format .

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 documentation 1 , 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.

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/Network 1 .

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

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 distances 1

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 documentation 1 , 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 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 segment 1 2

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=2 1 2

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 failures 1 2

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=2 1 2

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

https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-48A7A433-F3A0-4F77-99C4-B6280CD5D3F4.html

The next step the systems administrator should take is to prepare and configure the ESXi hosts to be used in the deployment.  According to the VMware Cloud Foundation documentation 1 , before you can deploy the management domain using VMware Cloud Builder, you must prepare the ESXi hosts that will be part of the management domain and the VI workload domains. You need to install ESXi on the hosts, configure the network settings, claim disks for vSAN, and optionally configure certificates for the hosts.  You can use different methods to prepare the ESXi hosts, such as using a custom ISO image, using the VMware Imaging Appliance, or installing ESXi interactively 1

Uploading the Deployment Parameter Workbook is not the next step, because it is done after preparing the ESXi hosts. The Deployment Parameter Workbook is a spreadsheet that contains all the parameters required for deploying VMware Cloud Foundation, such as IP addresses, host names, passwords, and license keys.  You need to download and complete the workbook before uploading it to VMware Cloud Builder 1

Configuring the Management Domain using custom certificates is not the next step, because it is an optional step that can be done after deploying the management domain. Custom certificates are used to secure the communication between the components of VMware Cloud Foundation, such as SDDC Manager, vCenter Server, and NSX-T Manager.  You can use either self-signed certificates or certificates signed by a certificate authority (CA) 1

Deploying the Management Domain using VMware Cloud Builder is not the next step, because it is done after preparing the ESXi hosts and uploading the Deployment Parameter Workbook. The management domain is the first domain that is deployed in VMware Cloud Foundation, and it contains the components for managing and operating the SDDC platform, such as SDDC Manager, vCenter Server, NSX-T Manager, and NSX Edge nodes.  You use VMware Cloud Builder to deploy the management domain by following a guided workflow on its UI 1

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 documentation 1 , 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 Remediate 1

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 automatically 1

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 immediately 1

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

https://docs.vmware.com/en/VMware-Validated-Design/6.2/sddc-architecture-and-design-for-a-vsphere-with-tanzu-workload-domain/GUID-8E524188-65F6-4FF2-B8A3-2D9B0C86FE2A.html

A NSX Tier-1 Gateway provides the functionality of a downlink connection to segments in a vSphere with Tanzu deployment.  According to the VMware documentation 1 , a segment is a virtual layer-2 domain that can be either overlay-backed or VLAN-backed. A NSX Tier-1 Gateway connects to one or more segments and provides routing and security services for the workloads attached to those segments.  A NSX Tier-1 Gateway also connects to a NSX Tier-0 Gateway, which provides uplink connectivity to external networks 2

References :  1 : Create and Configure a vSphere Namespace - VMware Docs  2 : NSX-T Data Center Concepts - VMware Docs

The three NSX components that are automated during the deployment of an edge cluster in a VMware Cloud Foundation environment are:

Edge VM deployment : SDDC Manager deploys the NSX Edge node virtual appliances on the vSphere cluster that backs the workload domain 1 .

Edge Uplink Profile configuration : SDDC Manager configures the edge uplink profile with the MTU, teaming policy, and transport VLAN settings for the edge nodes 1 .

Tier-0 and Tier-1 gateway configuration : SDDC Manager creates a tier-0 gateway and a tier-1 gateway for the edge cluster, and configures the routing, NAT, and firewall rules for them 1 .

This is because according to VMware documentation 1 , a VI workload domain consists of one or more vSphere clusters that run customer workloads.  To enable workload management for a VI workload domain, you need to have an NSX-T edge cluster that provides north-south connectivity and load balancing for Kubernetes clusters 2 .  The minimum requirement for creating an NSX-T edge cluster is two edge nodes 3 4 .  The size of the edge nodes depends on the throughput and features required, but for high availability, large size is recommended 5 .

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-getting-started/GUID-C68FD810-D270-43F2-AEBF-D522BA1F402B.html

This is because according to VMware documentation 3 4 , vSphere with Tanzu uses storage policies to integrate with shared datastores available in your environment, including VMFS, NFS, vSAN, or vVols datastores. The storage policies represent datastores and manage the storage placement of such objects as persistent volumes (PVs).  Storage Policy Based Management (SPBM) is a framework that provides a single unified control plane across different types of datastores and enables administrators to define policies based on storage capabilities and requirements 5 .

The Cloud Native Storage for vSphere with Tanzu workflow is as follows: 1. A developer deploys a pod using the kubectl CLI. 2. The vSphere with Tanzu Cloud Native Storage-Container Storage Interface (CNS-CSI) reads this request from the control plane API server. 3. CNS-CSI informs the vCenter Server CNS that a disk with gold storage class is required. 4. CNS interfaces with SPBM for a suitable datastore that satisfies the gold storage class (storage policy). 5. SPBM decides on a suitable datastore and interfaces with DRS for a suitable ESXi host. 6. Hostd on the ESXi host creates a first class disk (VMDK) on the datastore. 7. Spherelet on the ESXi host takes the VMDK. 8. Spherelet mounts the VMDK to the vSphere pod. 9. Spherelet reports the mount as a successful event to the control plane API server.

The service that is integrated with VMware Cloud Foundation and enables a centralized and simplified lifecycle management of ESXi host is  Option B: vSphere Lifecycle Manager (vLCM)   1 .

vLCM enables you to create cluster images for centralized and simplified lifecycle management of ESXi hosts including firmware.  When a VI workload domain cluster is created with an image, you can update and upgrade the ESXi version on all hosts in the cluster collectively  1 .

vSphere Lifecycle Manager (vLCM) is a key component of VMware Cloud Foundation (VCF) that enables centralized and simplified lifecycle management of ESXi hosts. It provides a single interface to manage host baselines, firmware and driver updates, and upgrades. With vLCM, administrators can create custom images for ESXi hosts, define baselines for host compliance, and apply updates to hosts in a coordinated manner. This helps to ensure consistency across the environment and reduce the risk of configuration drift. (source: VMware Cloud Foundation 4.x Architecture and Deployment Guide)

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-CDEEF4C6-7DFC-4EB5-B5F5-3C41230926F9.html