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

This is because according to VMware documentation1, 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 clusters2. The minimum requirement for creating an NSX-T edge cluster is two edge nodes34. The size of the edge nodes depends on the throughput and features required, but for high availability, large size is recommended5.

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

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.

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

This is because according to VMware documentation1, 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 image2. You can download ESXi software and VIBs from VMware or third-party sources and upload them to VIA for creating custom images3.

According to VMware Cloud Foundation Specialist (v2) Exam1, 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”.

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.

According to vSphere with Tanzu Architecture1, a Spherelet is a component that runs as a VIB on all Supervisor Cluster ESXi hosts configured with the vSphere Networking Stack. It enables an ESXi hypervisor to act as a Kubernetes master node or a Kubernetes worker node, depending on the role assigned by the Supervisor Cluster control plane.

This is because a network pool is a collection of subnets within an layer-2 network domain that includes information about subnets reserved for the vMotion and NFS networks that are required for adding a host to the SDDC Manager inventory2. The other options are not correct because they either include vSAN network, which is not needed for external NFS or VMFS on FC storage2, or they do not include NFS network, which is needed for external NFS storage1.

https://infohub.delltechnologies.com/l/dell-storage-with-vmware-cloud-foundation-1/vmware-cloud-foundation-network-pool-configuration

When adding new hosts to an existing VI workload domain in VMware Cloud Foundation, the new hosts must meet the following requirements:

A. The host uses the same storage type as the existing cluster hosts. D. The host uses the same network pool.

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"