VMware 2V0-21.23 Practice Test - Questions Answers, Page 2

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/VMwarevSphere/ 7.0/com.vmware.vsphere.vcenterhost.doc/GUID-9F9E3F8C-0E2B-4B6A-8C5C- 3F8E5F6B4E9D.html

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/VMwarevSphere/ 7.0/com.vmware.vcenter.install.doc/GUID-9F9E3F8C-0E2B-4B6A-8C5C-3F8E5F6B4E9D.html

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

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/VMwarevSphere/ 7.0/com.vmware.vsphere.security.doc/GUID-A2A4371A-B888-404C-B23FC422A8C40F54. html

Option A is correct because it allows the administrator to clone a VM to the content library as a VM template type, which can be used to create and manage different versions of these templates in the content library. Option B is incorrect because it requires the administrator to convert a VM to a template in the vCenter inventory first, which is an extra step. Option C is incorrect because it requires the administrator to export a VM to an OVF template and import it into the content library, which are extra steps. Option D is incorrect because it requires the administrator to convert a VM to a template in the vCenter inventory and clone it to the content library, which are extra steps.

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

Option B, D and E are correct because they allow the administrator to replace the machine SSL certificates, the VMware Certificate Authority (VMCA) certificate and the solution user certificates with custom certificates generated from the Enterprise CA, which will ensure that all certificates are trusted by the Enterprise CA and minimize the ongoing management overhead of replacing certificates. Option A is incorrect because replacing the VMCA certificate with a self-signed certificate generated from the VMCA will not ensure that the certificate is trusted by the Enterprise CA. Option C is incorrect because replacing the machine SSL certificates with trusted certificates generated from the VMCA will not ensure that the certificates are trusted by the Enterprise CA. Option F is incorrect because replacing the solution user certificates with trusted certificates generated from the VMCA will not ensure that the certificates are trusted by the Enterprise CA.

Reference: https://docs.vmware.com/en/VMwarevSphere/ 7.0/com.vmware.vsphere.security.doc/GUID-A2A4371A-B888-404C-B23FC422A8C40F54.html

Option B is correct because it allows the administrator to create a cold clone of the physical server using VMware vCenter Converter, which will create an image of the guest OS and application that can be moved to this remote data center without requiring network connectivity or affecting the application's data. Option A is incorrect because creating a hot clone of the physical server using VMware vCenter Converter will require network connectivity and may affect the application's data due to changes during conversion. Option C is incorrect because restoring the guest OS from a backup will require network connectivity and may not include the latest changes in the application. Option D is incorrect because using storage replication to replicate the guest OS and application will require network connectivity and may not be feasible for a physical server. Reference:

https://docs.vmware.com/en/vCenter-Converter-Standalone/6.2/com.vmware.convsa.guide/GUID-9F9E3F8C-0E2B-4B6A-8C5C-3F8E5F6B4E9D.html

Option C is correct because it indicates that vCenter Single Sign-On with Active Directory (Windows Integrated Authentication) as the identity source is the best SSO solution for VMware vCenter based on the criteria, as this solution supports Enhanced Link Mode groups, supports only one Active Directory domain as the identity source, delegates password and account lockout policies to Active Directory, and supports token-based authentication. Option A is incorrect because vCenter Identity Provider Federation with Active Directory Federation Services as the identity provider is not necessary for a single Active Directory domain scenario and may introduce additional complexity and overhead. Option B is incorrect because vCenter Single Sign-On with Active Directory over LDAP as the identity source does not support token-based authentication and may require additional configuration for password and account lockout policies. Option D is incorrect because vCenter Identity Provider Federation with Active Directory over LDAP as the identity provider does not support token-based authentication and may introduce additional complexity and overhead.

Reference: https://docs.vmware.com/en/VMwarevSphere/ 7.0/com.vmware.vcenter.install.doc/GUID-A2A4371A-B888-404C-B23F-C422A8C40F54.html

https://docs.vmware.com/en/vSphere-Replication/8.7/com.vmware.vsphere.replication- admin.doc/GUID-C249300C-2BC0-4128-88B5-046C3DE6BC5B.html