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

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 documentation1, 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 Remediate1

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 automatically1

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 immediately1

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 segment12

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=212

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 failures12

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=212

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

The option that should be enabled in the Planning and Preparation Workbook to address this issue is C) Identity and Access Management for VMware Cloud Foundation. According to the VMware Cloud Foundation documentation1, Identity and Access Management for VMware Cloud Foundation is a prerequisite for deploying Developer Ready Infrastructure using VMware Cloud Foundation. Identity and Access Management for VMware Cloud Foundation provides a centralized identity and access management service for the SDDC components and workloads, using Workspace ONE Access as the identity provider. If this option is not enabled in the Planning and Preparation Workbook, the Developer Ready Infrastructure using VMware Cloud Foundation option will be excluded and display an error.

A) Stretched Cluster for Management Domain is not a correct option, because it is not related to the deployment of Developer Ready Infrastructure using VMware Cloud Foundation. Stretched Cluster for Management Domain is an optional feature that allows you to stretch the management domain across two availability zones for high availability and disaster recovery purposes2

B) Clustered Workspace ONE Access is not a correct option, because it is not required for deploying Developer Ready Infrastructure using VMware Cloud Foundation. Clustered Workspace ONE Access is an optional feature that allows you to deploy a highly available Workspace ONE Access instance using vRealize Suite Lifecycle Manager. This feature is only available when Identity and Access Management for VMware Cloud Foundation is enabled3

D) Stretched Cluster for Workload Domain is not a correct option, because it is not related to the deployment of Developer Ready Infrastructure using VMware Cloud Foundation. Stretched Cluster for Workload Domain is an optional feature that allows you to stretch a VI workload domain across two availability zones for high availability and disaster recovery purposes4

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-A56D8E59-A549-4624-BC61-4A92710F9FA1.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.