VMware Updated 2V0-11.25 Exam Questions and Answers by malachi

In a VMware Cloud Foundation (VCF) environment, when adding a new cluster to an existing VI workload domain, the new cluster must use the same principal storage as the existing cluster. Since the existing cluster is using NFS, the available storage options for the new cluster would be NFS or vSAN, depending on the configuration.

To resolve the issue of disconnected accounts in SDDC Manager after password changes, the administrator must navigate to the Password Management section in the SDDC Manager UI. From there, the administrator can select the affected account, click the vertical ellipsis (three dots), and choose Update to enter the new password for that account, ensuring SDDC Manager is synced with the correct credentials.

Comprehensive and Detailed Explanation From Exact Extract:

After an NSX Edge cluster is deployed into a workload domain, SDDC Manager provides built‑in operations to adjust the cluster size. According to theVMware Cloud Foundation 5.2documentation:

“After you create an NSX Edge cluster, you can use SDDC Manager toexpand or shrinkit by adding or deleting NSX Edge nodes.”

Breakdown of options:

B. Expand– You canaddone or more Edge nodes to increase the cluster size.

E. Shrink– You canremoveEdge nodes to decrease the cluster size.

These two actions are the only supported cluster scaling operations available in SDDC Manager post-deployment. Other operations—such as Redeploy, Sync, or Delete—are not available via the UI for a deployed Edge cluster and are either manual or unsupported in that context.

Summary:

Selected choicesBandEmatch the documented capability to scale an NSX Edge cluster via SDDC Manager.

No other operations (A, C, D) are supported for an existing Edge cluster through the UI.

Comprehensive and Detailed Explanation From Exact Extract:

When troubleshooting high CPU usage on the SDDC Manager VM, the recommended diagnostic steps are:

Login to SDDC Manager using console with root credentials, run the top command to identify any services that may be consuming high %CPU (B):The official documentation instructs administrators to use system monitoring commands such as top or htop within the SDDC Manager appliance to determine if specific processes or services are causing elevated CPU usage. This helps pinpoint the root cause inside the VM.

Review the CPU usage of the ESXi management domain hosts to identify any that are overcommitted (D):High CPU usage within the SDDC Manager VM could also result from overall CPU contention on the physical ESXi hosts. Checking host-level CPU usage can help determine if the underlying infrastructure is contributing to the performance issue. The documentation emphasizes reviewing host resource metrics to ensure the management cluster is not overcommitted.

Other options such as rebooting the VM, upgrading vSphere, or modifying DRS settings are not recommended as initial diagnostic steps according to official guidance. Rebooting or changing configurations without proper analysis may disrupt services or not address the root cause.