Free 2V0-01.19 sample questions

Correct answer: Dynamic Patch Baselines

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

Correct answers: Custom; Normal; Low

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

Correct answers: Select the host in the vSphere Web Client, navigate to Configure > System > Time Configuration and click the Edit button.; Use the vicfg-ntp command.; Log in to the VMware Host Client, navigate to Host > Manage > Time & date and click Edit settings.

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.

Correct answers: Primary DNS server; Default gateway; Secondary DNS server

The ESXi DCUI Test Management Network feature pings the Primary DNS server, Default gateway, and Secondary DNS server to verify network connectivity. These are critical network infrastructure components for basic host communication. NTP and DHCP servers are not included in this specific DCUI test, which focuses on core DNS resolution and gateway connectivity. Reference: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsa.doc_10%2FGUID-B14C1BD3-AB4E-4A5F-AAEB-8A2856B19FC1.html

The ESXi DCUI Test Management Network feature pings the Primary DNS server, Default gateway, and Secondary DNS server to verify network connectivity. These are critical network infrastructure components for basic host communication. NTP and DHCP servers are not included in this specific DCUI test, which focuses on core DNS resolution and gateway connectivity. Reference: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsa.doc_10%2FGUID-B14C1BD3-AB4E-4A5F-AAEB-8A2856B19FC1.html

The ESXi DCUI Test Management Network feature pings the Primary DNS server, Default gateway, and Secondary DNS server to verify network connectivity. These are critical network infrastructure components for basic host communication. NTP and DHCP servers are not included in this specific DCUI test, which focuses on core DNS resolution and gateway connectivity. Reference: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsa.doc_10%2FGUID-B14C1BD3-AB4E-4A5F-AAEB-8A2856B19FC1.html

Correct answers: Send a notification email.; Migrate VM.; Run a command.

vSphere alarm actions include sending notification emails, running custom commands or scripts, and migrating VMs to different hosts. These are fundamental alarm response capabilities for automated incident response. Shutdown Guest and Restart Guest are not standard vSphere alarm actions - these would be performed through other vSphere operations or custom scripts. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.monitoring.doc/GUID-8F833B44-E675-406D-BFC1-64FB08EF6DFD.html

vSphere alarm actions include sending notification emails, running custom commands or scripts, and migrating VMs to different hosts. These are fundamental alarm response capabilities for automated incident response. Shutdown Guest and Restart Guest are not standard vSphere alarm actions - these would be performed through other vSphere operations or custom scripts. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.monitoring.doc/GUID-8F833B44-E675-406D-BFC1-64FB08EF6DFD.html

vSphere alarm actions include sending notification emails, running custom commands or scripts, and migrating VMs to different hosts. These are fundamental alarm response capabilities for automated incident response. Shutdown Guest and Restart Guest are not standard vSphere alarm actions - these would be performed through other vSphere operations or custom scripts. Reference: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.monitoring.doc/GUID-8F833B44-E675-406D-BFC1-64FB08EF6DFD.html

Correct answer: The VM share value (%Shares) adjusts to the Resource Pool.

When adding a VM to a Resource Pool, the VM inherits the Resource Pool share configuration and its share value percentage adjusts relative to the pool total. The VM reservation and limits do not automatically change when moved to a Resource Pool - these are separate configuration parameters that remain as configured on the VM unless explicitly modified.