Free 2V0-622 sample questions

Correct answers: Storage DRS is disabled on the virtual disk.; Rules prevent Storage DRS from making migration recommendations.

C, D -- Explanation: Problem A datastore in a datastore cluster cannot either maintenance mode. The Entering Maintenance Mode status remains at 1%. Cause One or more disks on the datastore cannot be migrated with Storage vMotion. This condition can occur in the following instances. Storage DRS is disabled on the disk Storage DRS rules prevent Storage DRS from making migration recommendations for the disk. Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-91 D4FBBC-0677-44DA-B0F2-43A3504F8CA0.html

C, D -- Explanation: Problem A datastore in a datastore cluster cannot either maintenance mode. The Entering Maintenance Mode status remains at 1%. Cause One or more disks on the datastore cannot be migrated with Storage vMotion. This condition can occur in the following instances. Storage DRS is disabled on the disk Storage DRS rules prevent Storage DRS from making migration recommendations for the disk. Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-91 D4FBBC-0677-44DA-B0F2-43A3504F8CA0.html

Correct answer: storage container

Refe re n c e: https://docs.vmware.eom/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-F95694B6-9EBD-4C12-8083-C358AE0E6852.html

Correct answers: Space load balancing among datastore within the datastore cluster.; Initial placement for virtual disks based on space and I/O workload.; I/O load balancing among datastores within the datastore cluster.

A, B, C -- Explanation: When you enable Storage DRS, you enable these functions: Space load balancing among datastores within a datastore cluster I/O load balancing among datastores within a datastore cluster Initial placement for virtual disks based on space and I/O workload Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en US&cmd=displayKC&externalld::::2032910

A, B, C -- Explanation: When you enable Storage DRS, you enable these functions: Space load balancing among datastores within a datastore cluster I/O load balancing among datastores within a datastore cluster Initial placement for virtual disks based on space and I/O workload Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en US&cmd=displayKC&externalld::::2032910

A, B, C -- Explanation: When you enable Storage DRS, you enable these functions: Space load balancing among datastores within a datastore cluster I/O load balancing among datastores within a datastore cluster Initial placement for virtual disks based on space and I/O workload Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en US&cmd=displayKC&externalld::::2032910

Correct answers: Turn on Proactive HA2E; Set the Proactive HA Automation Level to Automated.; Turn on vSphere HA and vSphere DRS.

B, D, E

B, D, E

B, D, E

Correct answers: When there is more than one VM-Host affinity rule in a vSphere DRS cluster, the rules are applied equally.; After creating a VM-Host affinity rule, its ability to function in relation to other rules is not checked.

A, D -- Explanation: If you create more than one VM-Host affinity rule, the rules are not ranked, but are applied equally. Be aware that this has implications for how the rules interact. For example, a virtual machine that belongs to two DRS groups, each of which belongs to a different required rule, can run only on hosts that belong to both of the host DRS groups represented in the rules. When you create a VM-Host affinity rule, its ability to function in relation to other rules is not checked. So it is possible for you to create a rule that contacts with the other rules you are using. When two VM-Host affinity rules conflict, the older one takes precedence and the newer rule is disabled. DRS only tries to satisfy enabled rules and disabled rules are ignored. Reference: https://docs.vmware.eom/enA/Mware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-793013E2-0976-43B7-9A00-340FA76859D0.html

A, D -- Explanation: If you create more than one VM-Host affinity rule, the rules are not ranked, but are applied equally. Be aware that this has implications for how the rules interact. For example, a virtual machine that belongs to two DRS groups, each of which belongs to a different required rule, can run only on hosts that belong to both of the host DRS groups represented in the rules. When you create a VM-Host affinity rule, its ability to function in relation to other rules is not checked. So it is possible for you to create a rule that contacts with the other rules you are using. When two VM-Host affinity rules conflict, the older one takes precedence and the newer rule is disabled. DRS only tries to satisfy enabled rules and disabled rules are ignored. Reference: https://docs.vmware.eom/enA/Mware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-793013E2-0976-43B7-9A00-340FA76859D0.html

Correct answers: Configuration; FQDN

B, D -- Reference: https://docs.vmware.eom/enA/Mware-vSphere/6.5/com.vmware.vsDhere.upgrade.doc/GUID-5E19B79A-AE4F-497A-9047-3E9AAC1D7767.htrnl

B, D -- Reference: https://docs.vmware.eom/enA/Mware-vSphere/6.5/com.vmware.vsDhere.upgrade.doc/GUID-5E19B79A-AE4F-497A-9047-3E9AAC1D7767.htrnl

Correct answers: Support for 512e disks; Automatic space reclamation

B, D

B, D

Correct answers: Reduced memory consumption.; Reduced consumption of extra CPU cycles.; Prevent packet flooding inside the vSwitch.

A, B, D -- Reference: https://geekfluent.com/2016/11/29/whats-new-in-vmware-vsphere-6-5/

A, B, D -- Reference: https://geekfluent.com/2016/11/29/whats-new-in-vmware-vsphere-6-5/

A, B, D -- Reference: https://geekfluent.com/2016/11/29/whats-new-in-vmware-vsphere-6-5/

Correct answers: Full File Clone; Reserve Space

A, B

A, B

Correct answer: The content library is optimized for syncing over HTTP.

Explanation: This optimization option comes with limitations:- Once a library is published as optimized for syncing over HTTP (streaming optimized), you cannot revert it back (unpublish) to a local library-A streaming optimized published library cannot be used to deploy VMs. Reference: http://docs.hol.vmware.com/HQL-2017/hol-1710-sdc-6 html en/