2V0-21.23 Exam Dumps - VMware vSphere 8.x Professional

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. References: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.install.doc/GUID-9F9E3F8C-0E2B-4B6A-8C5C-3F8E5F6B4E9D.html

When configuring vCenter High Availability (HA), two of the requirements for the active, passive, and witness nodes are that network latency must be less than 10 milliseconds, which ensures reliable communication between them; and they must have a minimum of a 1 Gbps network adapter, which provides sufficient bandwidth for data replication.

References: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-F01B2F12-C5BB-4C5C-B468-F3C70CA43635.html

https://www.stevenbright.com/2022/03/deploy-salt-minions-automatically-using-vmware-tools/

Two use cases for VMware Tools are direct deployment of the Aria Automation Config minion and ability to shut down a virtual machine remotely. Direct deployment of the Aria Automation Config minion is a feature that allows the administrator to deploy a configuration management agent to a virtual machine using VMware Tools. This feature enables automation and orchestration of virtual machine configuration tasks. Ability to shut down a virtual machine remotely is a feature that allows the administrator to gracefully power off a virtual machine from the vSphere Client or other VMware products. This feature requires VMware Tools to be installed and running on the guest operating system. References: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vmwaretools.doc/GUID-28C39A00-743B-4E23-9681-66254A15C2A0.html

The administrator should take these three steps to perform an update to vSphere clusters that are running vSAN:

• Configure vSphere Lifecycle Manager with an image for the cluster, which allows the administrator to specify the desired ESXi version and firmware for the hosts in the cluster.
• Register the vendor hardware management system as a vCenter Server extension, which allows the administrator to update the firmware on the hosts using vSphere Lifecycle Manager. The vendor hardware management system can also provide the firmware updates to vSphere Lifecycle Manager, so there is no need to download them from the vendor website separately.
• Run a hardware compatibility check using vSphere Lifecycle Manager, which verifies that the new software and firmware versions are compatible with the vSAN Hardware Compatibility List.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-4A626993-A829-495C-9659-F64BA8B560BD.html

To ensure a successful migration of an encrypted VM to a secure environment, the administrator needs to ensure that the source and destination vCenter instances share the same Key Management Server (KMS), which provides encryption keys for both environments; and ensure that the VM is encrypted before attempting the migration, which allows preserving its encryption status during vMotion.

References: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-F8F105EC-A6EA-4F4A-AF5E-E091B1629B27.html https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-C3FFBF62-D6BF-4A5E-B3FD-BFF622AC2ED9.html

Two actions that are required to ensure VM1 continues to run when esx01 is placed into maintenance mode are enabling fully automated DRS on the cluster, which allows balancing the workload across hosts and migrating VMs without user intervention; and manually live migrating VM1 to another host within the cluster using vSphere vMotion, which allows moving a running VM without downtime.

References: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-F01B2F12-C5BB-4C5C-B468-F3C70CA43635.html https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-F01B2F12-C5BB-4C5C-B468-F3C70CA43635.html

https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-lifecycle-manager/GUID-9A20C2DA-F45F-4C9B-9D17-A89BCB62E6EF.html

A vSphere Lifecycle Manager image can consist of the following four elements:

ESXi base image

The base image contains an image of VMware ESXi Server and additional components, such as drivers and adapters that are necessary to boot a server. The base image is the only mandatory element in a vSphere Lifecycle Manager image. All other elements are optional.

Vendor add-on

The vendor add-on is a collection of software components that OEMs create and distribute. The vendor add-on can contain drivers, patches, and solutions.

Firmware and drivers add-on

The firmware and drivers add-on is a special type of vendor add-on designed to assist in the firmware update process. The firmware and drivers add-on contains firmware for a specific server type and corresponding drivers. To add a firmware and drivers add-on to your image, you must install the hardware support manager plug-in provided by the hardware vendor for the hosts in the respective cluster.

Independent components

The component is the smallest discrete unit in an image. The independent components that you add to an image contain third-party software, for example drivers or adapters.