2V0-01.19 vSphere 6.7 Foundations Exam Practice Questions

VMs appear orphaned when there is a disconnect between vCenter Server and the ESXi host where the VM resides. This commonly occurs after an unsuccessful HA failover event or when VMs are unregistered directly from the ESXi host bypassing vCenter. Unsuccessful vMotion migrations and VM removal from vCenter would not create orphaned VMs. Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-BFD8C9BC-30FB-4A92-AFEC-2FC9FF387920.html

VMs appear orphaned when there is a disconnect between vCenter Server and the ESXi host where the VM resides. This commonly occurs after an unsuccessful HA failover event or when VMs are unregistered directly from the ESXi host bypassing vCenter. Unsuccessful vMotion migrations and VM removal from vCenter would not create orphaned VMs. Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-BFD8C9BC-30FB-4A92-AFEC-2FC9FF387920.html

A 4 vCPU virtual machine with Fault Tolerance requires vSphere Enterprise Plus licensing and a 10 GbE uplink for FT logging network traffic. 4 vCPU FT generates significant network traffic that demands high bandwidth. vSphere Standard license does not support multi-vCPU FT, and 1 GbE is insufficient for 4 vCPU FT logging requirements. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-57929CF0-DA9B-407A-BF2E-E7B72708D825.html

A 4 vCPU virtual machine with Fault Tolerance requires vSphere Enterprise Plus licensing and a 10 GbE uplink for FT logging network traffic. 4 vCPU FT generates significant network traffic that demands high bandwidth. vSphere Standard license does not support multi-vCPU FT, and 1 GbE is insufficient for 4 vCPU FT logging requirements. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-57929CF0-DA9B-407A-BF2E-E7B72708D825.html

For isolating 500 virtual desktops while allowing service communication, VMware recommends Private VLANs and VMware NSX Distributed Firewall. Private VLANs provide network-level isolation while permitting uplink communication, and NSX Distributed Firewall offers granular VM-to-VM and VM-to-service traffic control. vSphere Host Firewall protects ESXi hosts not VMs, and Port Filtering is not a complete isolation solution.

For isolating 500 virtual desktops while allowing service communication, VMware recommends Private VLANs and VMware NSX Distributed Firewall. Private VLANs provide network-level isolation while permitting uplink communication, and NSX Distributed Firewall offers granular VM-to-VM and VM-to-service traffic control. vSphere Host Firewall protects ESXi hosts not VMs, and Port Filtering is not a complete isolation solution.

Dynamic Patch Baselines automatically include patches that meet specific criteria such as severity level, vendor, or product type, and the content changes as new patches become available. Unlike Fixed Patch Baselines which contain a static set of patches, Dynamic Baselines update themselves when new patches match the defined criteria. Host Profiles are for host configuration management, and Upgrade Baselines are used for ESXi host upgrades, not patch management. Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.update_manager.doc%2FGUID-95A71727-B0FA-4144-9E57-2C41640047DD.html

VMware Resource Pools support predefined share levels of High, Normal, and Low, plus Custom shares for user-defined values. These shares determine relative CPU and memory allocation priority when resources are contended. Maximum refers to resource limits not shares, and Average is not a valid VMware share type. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-0F6C6709-A5DA-4D38-BE08-6CB1002DD13D.html

VMware Resource Pools support predefined share levels of High, Normal, and Low, plus Custom shares for user-defined values. These shares determine relative CPU and memory allocation priority when resources are contended. Maximum refers to resource limits not shares, and Average is not a valid VMware share type. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-0F6C6709-A5DA-4D38-BE08-6CB1002DD13D.html

VMware Resource Pools support predefined share levels of High, Normal, and Low, plus Custom shares for user-defined values. These shares determine relative CPU and memory allocation priority when resources are contended. Maximum refers to resource limits not shares, and Average is not a valid VMware share type. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-0F6C6709-A5DA-4D38-BE08-6CB1002DD13D.html

ESXi hosts can synchronize time automatically through the vSphere Web Client time configuration, the vicfg-ntp command-line tool, or the VMware Host Client interface. These methods configure NTP services for ongoing time synchronization. The esxcli hardware clock get command only reads the current clock but does not configure automatic synchronization, and VMware Tools time sync is for VMs, not ESXi hosts.

ESXi hosts can synchronize time automatically through the vSphere Web Client time configuration, the vicfg-ntp command-line tool, or the VMware Host Client interface. These methods configure NTP services for ongoing time synchronization. The esxcli hardware clock get command only reads the current clock but does not configure automatic synchronization, and VMware Tools time sync is for VMs, not ESXi hosts.

ESXi hosts can synchronize time automatically through the vSphere Web Client time configuration, the vicfg-ntp command-line tool, or the VMware Host Client interface. These methods configure NTP services for ongoing time synchronization. The esxcli hardware clock get command only reads the current clock but does not configure automatic synchronization, and VMware Tools time sync is for VMs, not ESXi hosts.