READ Free Dumps For VMware- 2V0-622
| Question ID 20033 | An administrator has recently upgraded from vSphere 6.0 to 6.5, and can no longer see the software iSCSI named vmhba33.
Which could be the reason for this?
|
| Option A | The upgrade has changed the vmhba name.
|
| Option B | vSphere 6.5 automates iSCSI configurations.
|
| Option C | vSphere 6.5 no longer supports software iSCSI.
|
| Option D | The upgrade has deleted the vmhba.
|
| Correct Answer | A |
Explanation In vSphere 6.5, the name assigned to the iSCSI software adapter is different from the earlier releases. After you upgrade to the vSphere 6.5 release, the name of the existing software iSCSI adapter, vmhbaXX, changes. https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-esxi-vcenter-server-65-release-notes.html#storageissues
| Question ID 20034 | An administrator is trying to vMotion a VM from his datacenter to a recovery site. Which is the maximum allowed RTT (Round-Trip Time) latency between source
and destination host?
|
| Option A | 100 milliseconds
|
| Option B | 150 milliseconds
|
| Option C | 15 milliseconds
|
| Option D | 10 milliseconds
|
| Correct Answer | B |
Explanation Round-Trip Time for Long-Distance vMotion Migration If you have the proper license applied to your environment, you can perform reliable migrations between hosts that are separated by high network round-trip latency times. The maximum supported network round-trip time for vMotion migrations is 150 milliseconds. This round-trip time lets you migrate virtual machines to another geographical location at a longer distance. https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.vcenterhost.doc/GUID-3B41119A-1276-404B-8BFB-A32409052449.html