VMware 5V0-31.22 Practice Test - Questions Answers, Page 8

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.

The correct tool to use for replacing the vSAN Witness appliance for a VMware Cloud Foundation stretched vSAN cluster is the vSphere Client.According to the VMware Cloud Foundation documentation1, you can replace or change the vSAN witness host for a stretched cluster using the vSphere Client without affecting life cycle operations of SDDC Manager. You need to select a new host to use as the vSAN witness host, claim disks on the new witness host, and review the configuration.

vSphere Update Manager is not the correct tool, because it is used for patching and upgrading ESXi hosts, not for replacing vSAN witness hosts2

SDDC Manager is not the correct tool, because it does not have a workflow for replacing vSAN witness hosts.You need to use the vSphere Client for this task1

vSAN PowerCLI is not the correct tool, because it is a PowerShell module that provides cmdlets for managing and automating vSAN environments, not for replacing vSAN witness hosts3

These are valid use cases for multiple clusters in a workload domain according to VMware documentation. A workload domain with multiple availability zones each containing clusters can provide high availability and disaster recovery by distributing workloads across different physical locations within a region. A workload domain with multiple clusters in one rack can provide scalability and flexibility by allowing different configurations and policies for different clusters within a single logical unit. Two clusters forming one stretched workload domain can provide resiliency and fault tolerance by synchronizing data across two sites within a region.

This is because according to VMware documentation, this is what an administrator must register as an external component to complete this task of configuring scheduled backups for the SDDC Manager. SFTP server is one of the supported backup targets for SDDC Manager backups. The administrator can register an SFTP server by navigating to the SDDC Manager UI > Administration > Backup > Site Settings and clicking Register External.

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 domain1.

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

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 them1.

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.

Based on VCF Domain Requirement and vSAN Cluster Practice, 4x Nodes will be a Managemnet Domain (Min. Requirement 4 Nodes) other 4x Nodes (with 1 Disk Group) and 8x Nodes (with 2 Disk Groups) seperate 2x Workload Domain because vSAN Best Pratices same cluster should be same numebr disk group and same number of Cache and Capacity (same size) each host .

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 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 Networking Requirements for vSAN1, the maximum network latency between the two main sites for stretched clusters is 5 ms RTT (round-trip time). This means that the latency between any two nodes in different availability zones should not exceed 5 ms.

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-design/GUID-11177D00-C8BE-4CEC-B997-659CC03B6D12.html