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

The VMware Cloud Foundation Specialist (v2) certification exam guide from VMware specifically mentions that "Upgrade vCenter Server to a new version using vSphere Lifecycle Manager (vLCM)" is a key knowledge area for the exam (source[1][2]: ).

Additionally, search result [1] mentions that SDDC Manager is responsible for the life cycle management of vCenter Server and other components[3], indicating that vSphere LCM is specifically responsible for upgrading vCenter Server, a supported function.

a supported function of vSphere Lifecycle Manager (LCM) in VMware Cloud Foundation (VCF) is Option A: Upgrade vCenter Server 1. vSphere Lifecycle Manager provides a framework for desired state lifecycle management of vSphere hosts in a cluster 2.

 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.

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.

when upgrading ESXi software on Dell EMC PowerEdge servers using SDDC Manager Lifecycle Management (LCM), you must use a Dell EMC customized image that contains drivers for specific hardware components such as storage adapters.

According to About Architecture and Design for a vSphere with Tanzu Workload Domain4, two of the functionalities that a NSX Tier-0 Gateway provides to a vSphere with Tanzu deployment are:

• Connectivity to all Tier-1 Gateways: A Tier-0 Gateway connects to one or more Tier-1 Gateways that provide routing services for each namespace in vSphere with Tanzu.
• Connectivity to physical networks and routers: A Tier-0 Gateway connects to external networks via uplink interfaces that can use static routing or dynamic routing protocols such as BGP.

This is because according to VMware documentation6, these are three initial shared storage types that are supported for deploying a new VI Workload Domain into an existing VCF environment. You can also add other supported storage types after deploying the VI Workload Domain.

According to NSX Manager VM and Host Transport Node System Requirements23, an NSX-T management cluster formed using a medium-sized appliance can support up to 128 hypervisors. Since each VI Workload Domain has 36 hosts (18 x 2), and there are three VI Workload Domains, the total number of hosts is 108 (36 x 3), which is within the limit of a medium-sized NSX-T Manager cluster.

According to the VMware documentation, each NSX-T Local Manager is associated with a vCenter Server, and each NSX-T Local Manager can manage up to three vCenters. In a VCF deployment with two environments (PROD and DEV) and two different hardware server types in PROD, there would be a total of three vCenter Servers. Therefore, a total of three NSX-T Local Managers would be provisioned to manage the three vCenter Servers.

This is because according to VMware documentation, this is the ideal design of VMware Cloud Foundation domains that the architect should recommend based on the Bill of Material for different vSAN ready nodes. This design can provide optimal performance and availability by using vSAN ready nodes with different disk group configurations for different domains based on their workload characteristics and requirements. The management domain can use vSAN ready nodes with one disk group per node to provide sufficient capacity and redundancy for management components such as vCenter Server and NSX Manager. The workload domains can use vSAN ready nodes with two disk groups per node to provide higher performance and throughput for VI workloads such as VMs and containers.

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"