Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. VMware
  5. 2V0-21.23

VMware 2V0-21.23 Exam
VMware vSphere 8.x Professional (Page 4 )

Updated On: 12-Feb-2026
Page 4 of 22
PDF with 110 Questions

During the staging of a patch on a vCenter Server Appliance, an error was encountered and the process stopped. An administrator resolved the root cause and is ready to continue with the staging of the patch.
From the vCenter Management Interface, which action should the administrator take to continue the process from the point at which the error occurred?

  1. Use the Stage and Install option to resume the staging.
  2. Use the Resume option to resume the staging.
  3. Use the Unstage option to restart the staging.
  4. Use the Stage Only option to restart the staging.

Answer(s): B

Explanation:

docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.upgrade.doc/GUID-FF533442- 66F0-4797-976D-1DA99102DD0A.html



An administrator is adding a new ESXi host to an existing vSphere cluster. When selecting the cluster, the administrator Is unable to use the Cluster Quickstart workflow to add and configure the additional host.
What could be the root cause of this issue?

  1. The administrator has previously dismissed the Cluster Quickstart workflow.
  2. The administrator must manually add the host to the cluster before using the Cluster Quickstart workflow.
  3. The administrator has not been assigned the required permissions to use the Cluster Quickstart workflow.
  4. The administrator must enable the Cluster Quickstart workflow option in VMware vCenter.

Answer(s): A

Explanation:

Option A is correct because it indicates that the administrator has previously dismissed the Cluster Quickstart workflow, which will prevent them from using it to add and configure an additional host.

To use the Cluster Quickstart workflow again, the administrator must enable it in the cluster settings.
Option B is incorrect because the administrator does not need to manually add the host to the cluster before using the Cluster Quickstart workflow, as this is one of the steps in the workflow.
Option C is incorrect because the administrator does not need any special permissions to use the Cluster Quickstart workflow, as long as they have permissions to perform cluster operations.
Option D is incorrect because there is no option to enable the Cluster Quickstart workflow in VMware vCenter, as this is a feature of vSphere clusters.


Reference:

https://docs.vmware.com/en/VMware- vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-9F9E3F8C-0E2B-4B6A-8C5C- 3F8E5F6B4E9D.html



A company has two sites: Site A and Site B. The administrator would like to manage the VMware vCenter inventories in both sites from a single vSphere Client session.
Which vCenter feature must be configured?

  1. VMware Certificate Authority
  2. VMware Site Recovery Manager
  3. vCenter Single Sign-On
  4. Enhanced Linked Mode

Answer(s): D

Explanation:

Option D is correct because it indicates that Enhanced Linked Mode must be configured to allow the administrator to manage the VMware vCenter inventories in both sites from a single vSphere Client session. Enhanced Linked Mode allows multiple vCenter Server instances to share information such as tags, licenses, roles, permissions, and policies.
Option A is incorrect because VMware Certificate Authority is a service that provides certificates for vSphere components and does not affect inventory management.
Option B is incorrect because VMware Site Recovery Manager is a solution that provides disaster recovery and business continuity for vSphere environments and does not affect inventory management.
Option C is incorrect because vCenter Single Sign-On is a service that provides authentication and authorization for vSphere components and does not affect inventory management.


Reference:

https://docs.vmware.com/en/VMware- vSphere/7.0/com.vmware.vcenter.install.doc/GUID-9F9E3F8C-0E2B-4B6A-8C5C-3F8E5F6B4E9D.html



An administrator plans to update the Supervisor cluster and has noticed some of the Tanzu Kubemetes Grid clusters are running an incompatible version.

Which action must the administrator take before proceeding with the Supervisor cluster update?

  1. Update all Tanzu Kubernetes Grid clusters to the latest version prior to the Supervisor cluster update.
  2. No action is needed - Tanzu Kubernetes Grid clusters will be updated automatically as part of the update process.
  3. No action is needed - Incompatible Tanzu Kubernetes Grid clusters can be manually updated after the Supervisor cluster update.
  4. Update incompatible Tanzu Kubernetes Grid clusters prior to the Supervisor cluster update.

Answer(s): D

Explanation:

Option D is correct because it indicates that the administrator must update incompatible Tanzu Kubernetes Grid clusters prior to the Supervisor cluster update, as this will ensure that there are no compatibility issues or disruptions during or after the update process.
Option A is incorrect because it is not necessary to update all Tanzu Kubernetes Grid clusters to the latest version prior to the Supervisor cluster update, as some clusters may already be compatible with the new version.
Option B is incorrect because Tanzu Kubernetes Grid clusters will not be updated automatically as part of the update process, as they require manual intervention from the administrator.
Option C is incorrect because incompatible Tanzu Kubernetes Grid clusters cannot be manually updated after the Supervisor cluster update, as they may become inaccessible or unstable due to compatibility issues.


Reference:

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID- 9F9E3F8C-0E2B-4B6A-8C5C-3F8E5F6B4E9D.html
https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-maintenance/GUID- 292482C2-A5FA-44B5-B26E-F887A91BB19D.html
If a Tanzu Kubernetes Grid cluster is incompatible with vSphere 8, upgrade the cluster before proceeding with the system upgrade.



Which three vSphere features are still supported for Windows-based virtual machines when enabling vSphere's -virtualization-based security feature? (Choose three.)

  1. vSphere vMotion
  2. PCI passthrough
  3. vSphere High Availability (HA)
    D, vSphere Fault Tolerance
  4. vSphere Distributed Resources Scheduler (DRS)
  5. Hot Add of CPU or memory

Answer(s): A,C,E

Explanation:

Option A, C and E are correct because they indicate that vSphere features such as vMotion, High Availability (HA) and Distributed Resource Scheduler (DRS) are still supported for Windows-based virtual machines when enabling vSphere's virtualization-based security feature, which provides enhanced protection for guest operating systems and applications against various attacks.
Option B is incorrect because PCI passthrough is not supported for Windows-based virtual machines when enabling vSphere's virtualization-based security feature, as this feature requires direct access to physical devices that cannot be shared or protected by hypervisor mechanisms.
Option D is incorrect because Fault Tolerance is not supported for Windows-based virtual machines when enabling vSphere's virtualization-based security feature, as this feature requires identical execution states for primary and secondary virtual machines that cannot be guaranteed by hypervisor mechanisms.
Option F is incorrect because Hot Add of CPU or memory is not supported for Windows-based virtual machines when enabling vSphere's virtualization-based security feature, as this feature requires dynamic changes to virtual hardware configuration that cannot be handled by hypervisor mechanisms.


Reference:

https://docs.vmware.com/en/VMware- vSphere/7.0/com.vmware.vsphere.security.doc/GUID-A2A4371A-B888-404C-B23F- C422A8C40F54.html






Post your Comments and Discuss VMware 2V0-21.23 exam prep with other Community members:

Join the 2V0-21.23 Discussion