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

"You can remove NSX Edge nodes from an NSX Edge Cluster that you created with SDDC Manager if you need to scale down to meet business needs.

Prerequisites

-The NSX Edge cluster must be available in the SDDC Manager inventory and must be Active.

-The NSX Edge node must be available in the SDDC Manager inventory.

-The NSX Edge cluster must be hosted on one or more vSphere clusters from the same workload domain.

-The NSX Edge cluster must contain more than two NSX Edge nodes.

-The NSX Edge cluster must not be federated or stretched.

-If the NSX Edge cluster was deployed with a Tier-0 Service High Availability of Active-Active, the NSX Edge cluster must contain two or more NSX Edge nodes with two or more Tier-0 routers (SR component) after the NSX Edge nodes are removed.

-If selected edge cluster was deployed with a Tier-0 Service High Availability of Active-Standby, you cannot remove NSX Edge nodes that are the active or standby node for the Tier-0 router."

These three statements accurately answer the manager’s question about NSX Edge nodes. Here is a brief explanation for each statement:

B. They can only be removed if the NSX Edge cluster is available in the SDDC Manager inventory and is active. This is a prerequisite for removing NSX Edge nodes from an NSX Edge cluster using SDDC Manager. If the NSX Edge cluster is not available or not active, you cannot remove NSX Edge nodes from it1

C. They can only be removed if the NSX Edge cluster is not stretched. This is another prerequisite for removing NSX Edge nodes from an NSX Edge cluster using SDDC Manager. If the NSX Edge cluster is stretched across different sites, you cannot remove NSX Edge nodes from it using SDDC Manager. You need to use the VMware Cloud Foundation NSX-T Edge Cluster Deployment Removal Tool instead12

E. They can only be removed if the NSX Edge node is available in the SDDC Manager inventory. This is also a prerequisite for removing NSX Edge nodes from an NSX Edge cluster using SDDC Manager. If the NSX Edge node is not available in the SDDC Manager inventory, you cannot remove it using SDDC Manager. You need to delete it from the NSX-T Manager UI instead13

A. They can be removed at any time if they are in a powered-off state. This is not a correct statement, because powering off the NSX Edge nodes does not affect their removal process using SDDC Manager. You can remove NSX Edge nodes that are powered on or powered off, as long as they meet the other prerequisites1

D. They can be removed if there are at least two nodes in the NSX Edge cluster. This is not a correct statement, because the minimum number of nodes in an NSX Edge cluster depends on the Tier-0 service high availability mode that was selected during the deployment. If the mode was Active-Active, you need at least two nodes in the NSX Edge cluster after removing any nodes. If the mode was Active-Standby, you need at least one node in the NSX Edge cluster after removing any nodes1

F. They can only be removed if the NSX Edge node was deployed from NSX-T Manager directly. This is not a correct statement, because the question is about removing NSX Edge nodes that were deployed using SDDC Manager, not NSX-T Manager directly. If the NSX Edge node was deployed from NSX-T Manager directly, you cannot remove it using SDDC Manager, but you can delete it from the NSX-T Manager UI.

References: 1: Remove Edge Nodes from an NSX Edge Cluster - VMware Docs 2: VMware Cloud Foundation NSX-T Edge Cluster Deployment Removal Tool (78635) | VMware KB 3: Delete the Failed NSX Edge Node from the NSX Manager Cluster - VMware Docs

A. Generate Certificate Signing Requests from SDDC Manager - In order to replace the self-signed certificates with third-party signed certificates, the Certificate Signing Requests (CSRs) need to be generated. This can be done from the SDDC Manager UI.

C. Create and package the certificates in a domain_name.tar.gz file - After the CSRs are generated, they can be used to obtain third-party signed certificates from a certificate authority. Once the certificates are obtained, they need to be packaged in a domain_name.tar.gz file and uploaded to SDDC Manager.

Generate Certificate Signing Requests (CSRs) from SDDC Manager for each component that requires a certificate1. You can do this from the SDDC Manager UI or using an API call1.

Have the CSRs signed by a third-party Certificate Authority of your choice1. You can use any external provider that meets your security policy requirements.

Create and package the certificates in a domain_name.tar.gz file according to the naming convention and folder structure specified by SDDC Manager1. You can use any compression tool that supports gzip format.

Upload and install the certificates using SDDC Manager UI or API1. You can also verify and troubleshoot the certificate installation using SDDC Manager.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-80431626-B9CD-4F21-B681-A8F5024D2375.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 .

This is because according to VMware documentation, this is one of the methods that meets these requirements and is supported for vCenter Server with VMware Cloud Foundation. vCenter HA provides high availability by creating an active-passive cluster of three vCenter Server nodes (one active, one passive, one witness). It also optimizes hardware utilization by allowing resource sharing among different workload domains through Enhanced Linked Mode (ELM).

To change the password of the SDDC Manager super user account, the administrator should follow these steps:

Log in to the SDDC Manager UI as a user with the ADMIN role.

Go to Administration > Security > Password Management.

Select the SDDC Manager account from the component drop-down menu.

Click Rotate Now button.

This is the recommended method for changing the password of the SDDC Manager super user account, as documented in the VMware Cloud Foundation Administration Guide: https://docs.vmware.com/en/VMware-Cloud-Foundation/index.html

"When more capacity is needed, scaling the consolidated design is an option but a much better design option for a larger scale is to use workload domains. After you reach 8 or 10 nodes in the consolidated design, consider migrating to a standard design. If you migrate to a standard design, the default small vCenter Server Appliance size should be enough for most designs."

 According to the VMware Cloud Foundation documentation1, a consolidated architecture is suitable for smaller deployments that have 6 or fewer nodes, while a standard architecture is recommended for larger deployments that have more than 6 nodes. A consolidated architecture has some limitations and trade-offs compared to a standard architecture, such as less scalability, flexibility, and isolation. Therefore, if the customer’s workload demand increases and requires more capacity, migrating to a standard architecture should be considered.

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

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.