VMware 2V0-621 Online Practice Questions and Exam Preparation

VMware 2V0-621 Online Questions & Answers

• Question 1:

  An administrator is able to manage an ESXi 6.x host connected to vCenter Server using the vSphere Web Client but is unable to connect to the host directly.

  Which action should the administrator take to correct this behavior?

  A. Restart management agents on the ESXi host.
  B. Disable Lockdown Mode on the ESXi host through vCenter Server.
  C. Disable the ESXi firewall with the command esxcli network firewall unload.
  D. Reboot the ESXi host.
  B. Disable Lockdown Mode on the ESXi host through vCenter Server.

  ---

  explanation:

  ESXi 6.0:

  Starting with vSphere 6.0, you can select normal Lockdown mode or strict Lockdown mode, which offer different degrees of lockdown.

  Normal Lockdown mode:

  In normal lockdown mode the DCUI service is not stopped. If the connection to the vCenter Server is lost and access through the vSphere Web Client is no longer available, privileged accounts can log in to the ESXi host's Direct Console

  Interface and exit lockdown mode. Only these accounts can access the Direct Console User Interface:

  Accounts in the Exception User list for lockdown mode who have administrative privileges on the host. The Exception Users list is meant for service accounts that perform very specific tasks. Adding ESXi administrators to this list defeats the

  purpose of lockdown mode.

  Users defined in the DCUI.Access advanced option for the host. This option is for emergency access to the Direct Console Interface in case the connection to vCenter Server is lost. These users do not require administrative privileges on the

  host.

  Strict Lockdown mode:

  In strict lockdown mode the DCUI service is stopped. If the connection to vCenter Server is lost and the vSphere Web Client is no longer available, the ESXi host becomes unavailable unless the ESXi Shell and SSH services are enabled and

  Exception Users are defined. If you cannot restore the connection to the vCenter Server system, you have to reinstall the host.

  For more information on Lockdown mode in vSphere 6.0, see the Lockdown Mode section in the vSphere Security Guide.

  To enable or disable Lockdown mode from the DCUI:

  1.

  Log directly in to the ESXi host.

  2.

  Open the DCUI on the host.

  3.

  Press F2 for Initial Setup.

  4.

  Press Enter to toggle the Configure Lockdown Mode setting.

  To enable or disable Lockdown mode from the vSphere Web Client:

  1.

  Browse to the host in the vSphere Web Client inventory.

  2.

  Click the Manage tab and click Settings.

  3.

  Under System, select Security Profile.

  4.

  In the Lockdown Mode panel, click Edit.

  5.

  Click Lockdown Mode and select one of the lockdown mode options.

  Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=1008077

• Question 2:

  An administrator connects to an ESXi 6.x host console in order to shutdown the host.

  Which option in the Direct Console User Interface would perform this task?

  A. Press the F12 key
  B. Press the F2 key
  C. Press Alt + F1 simultaneously
  D. Press Alt + F2 simultaneously
  A. Press the F12 key

  ---

  explanation:

  ESXi 4.x/5.x/6.0

  1.

  From the Direct Console User Interface (DCUI) screen, press F12 to view the shutdown-related options for the ESXi host.

  Press F2 to shut down.

  Press F11 to reboot.

  2.

  From Local or Remote Tech Support Mode, or from an SSH session, run one of these commands:

  Run the reboot command to restart the host.

  Run the poweroff command to shut down the host.

  Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=1013193

• Question 3:

  An administrator decides to change the root password for an ESXi 6.x host to comply with the company's security policies.

  What are two ways that this can be accomplished? (Choose two.)

  A. Use the Direct Console User Interface to change the password.
  B. Use the passwd command in the ESXi Shell.
  C. Use the password command in the ESXi Shell.
  D. Use the vSphere client to update local users.
  A. Use the Direct Console User Interface to change the password.
  B. Use the passwd command in the ESXi Shell.

  ---

  explanation:

  Limit ESXi Access By default, the ESXi Shell and SSH services are not running and only the root user can log in to the Direct Console User Interface (DCUI). If you decide to enable ESXi or SSH access, you can set timeouts to limit the risk of unauthorized access. ESXi enforces password requirements for direct access from the Direct Console User Interface, the ESXi Shell, SSH, or the vSphere Client. Reference: https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-security-guide.pdf

• Question 4:

  Which command shows the Physical Uplink status for a vmnic?

  A. esxcli network ip get
  B. esxcli network nic list
  C. esxcli network vmnic list
  D. esxcli network ifconfig get
  B. esxcli network nic list

  ---

  explanation:

  Command:

  network nic list

  Description:

  This command will list the Physical NICs currently installed and loaded on the system.

  Reference: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vcli.ref.doc_50%2Fesxcli_network.html

• Question 5:

  An administrator notices that the time on an ESXi 6.x host is incorrect.

  Which two actions should the administrator take to correct this issue? (Choose two.)

  A. Modify the time for the host using the vSphere client.
  B. Correct the NTP settings in the /etc/ntp.conf file.
  C. Configure NTP from the Direct Console User Interface.
  D. Use the vicfg-ntp command from the vSphere Management Appliance.
  A. Modify the time for the host using the vSphere client.
  B. Correct the NTP settings in the /etc/ntp.conf file.

  ---

  explanation:

  Resolution

  To configure NTP on ESX/ESXi 4.1 and ESXi 5.x hosts using the vSphere Client:

  1.

  Connect to the ESX/ESXi host using the vSphere Client.

  2.

  Select a host in the inventory.

  3.

  Click the Configuration tab.

  4.

  Click Time Configuration.

  5.

  Click Properties.

  6.

  Click Options.

  7.

  Click NTP Settings.

  8.

  Click Add.

  9.

  Enter the NTP Server name. For example, pool.ntp.org.

  Note: When entering the multiple NTP Server names, use a comma (,) followed by a space ( ) between the entries.

  10.

  Click OK.

  11.

  Click the General tab.

  12.

  Click Start automatically under Startup Policy.

  Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=2012069

• Question 6:

  An ESXi 6.x host in the vCenter Server inventory has disconnected due to an All Paths Down (APD) situation. An administrator has corrected the APD issue on the host, but it still remains disconnected. What action should the administrator take next?

  A. Select Restart Management Agents from the DCUI.
  B. Execute esxcli system settings advanced set -d /Scsi/FailVMIOonAPD.
  C. Modify the advanced parameter /Disk/ApdTokenRetryCount.
  D. Enable the advanced parameter /Misc/APDHandlingEnable.
  A. Select Restart Management Agents from the DCUI.

  ---

  explanation:

  All-Paths-Down (APD)

  1.

  A datastore is shown as unavailable in the Storage view

  2.

  A storage adapter indicates the Operational State of the device as Dead or Error

  3.

  All paths to the device are marked as Dead

  4.

  You are unable to connect directly to the ESXi host using the vSphere Client

  5.

  The ESXi host shows as Disconnected in vCenter Server

  6.

  In the /var/log/vmkernel.log file, you see entries similar to:

  cpu1:2049)WARNING: NMP: nmp_IssueCommandToDevice:2954:I/O could not be issued to device "naa.60a98000572d54724a34642d71325763" due to Not found cpu1:2049)WARNING: NMP: nmp_DeviceRetryCommand:133:Device

  "naa.60a98000572d54724a34642d71325763": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device. cpu1:2049)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device

  "naa.60a98000572d54724a34642d71325763" is blocked. Not starting I/O from device. cpu1:2642)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.60a98000572d54724a34642d71325763" - issuing

  command 0x4124007ba7c0 cpu1:2642)WARNING: NMP: nmpDeviceAttemptFailover:658:Retry world failover device "naa.60a98000572d54724a34642d71325763" - failed to issue command due to Not found (APD), try again... cpu1:2642)

  WARNING: NMP: nmpDeviceAttemptFailover:708:Logical device "naa.60a98000572d54724a34642d71325763": awaiting fast path state update... cpu0:2642)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device

  "naa.60a98000572d54724a34642d71325763" - issuing command 0x4124007ba7c0 cpu0:2642)WARNING: NMP: nmpDeviceAttemptFailover:658:Retry world failover device "naa.60a98000572d54724a34642d71325763" - failed to issue

  command due to Not found (APD), try again... cpu0:2642)WARNING: NMP: nmpDeviceAttemptFailover:708:Logical device "naa.60a98000572d54724a34642d71325763": awaiting fast path state update...

  A restart of the management agents may show these errors:

  Not all VMFS volumes were updated; the error encountered was 'No connection'.

  Errors:

  Rescan complete, however some dead paths were not removed because they were in use by the system. Please use the 'storage core device world list' command to see the VMkernel worlds still using these paths. Error while scanning

  interfaces, unable to continue. Error was Not all VMFS volumes were updated; the error encountered was 'No connection'.

  You may also see that the device is no longer listed:

  cpu17:10107)WARNING: Vol3: 1717: Failed to refresh FS 4beb089b-68037158-2ecc-00215eda1af6 descriptor: Device is permanently unavailable cpu17:10107)ScsiDeviceIO: 2316: Cmd(0x412442939bc0) 0x28, CmdSN 0x367bb6 from

  world 10107 to dev "eui.00173800084f0005" failed H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

  cpu17:10107)Vol3: 1767: Error refreshing PB resMeta: Device is permanently unavailable

  Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=2004684

• Question 7:

  An administrator is unable to see performance statistics for only the Past Week performance data. The vCenter Server is using a Microsoft SQL Server Database. What are three likely causes contributing to this issue? (Choose three.)

  A. Performance statistics are turned off.
  B. The Past Day rollup job is not present.
  C. The stats_rollup_1_proc is not present.
  D. The VMware Performance Charts Service is stopped.
  E. The JDBC URL is incorrect in the vcdb.properties file.
  A. Performance statistics are turned off.
  B. The Past Day rollup job is not present.
  C. The stats_rollup_1_proc is not present.

  ---

  explanation:

  Please refer to this link to troubleshoot this issue: https://kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=1004382

• Question 8:

  An administrator wants to allow users to login to the vSphere Web Client using the Use Windows session authentication check box for faster authentication. Which three requirements must be met for this feature to be available and functional? (Choose three.)

  A. Install the vSphere Web Client Integration browser plug-in on the vCenter Server and Platform Services Controller machines.
  B. Install the vSphere Web Client Integration browser plug-in on each workstation from where a user will sign in.
  C. The users must be signed into Windows using Active Directory user accounts.
  D. The administrator must create a valid Identity Source in Single Sign-On for the users domain.
  E. The administrator must create a valid Single Sign-On Identity Source using Integrated Windows Authentication.
  B. Install the vSphere Web Client Integration browser plug-in on each workstation from where a user will sign in.
  C. The users must be signed into Windows using Active Directory user accounts.
  D. The administrator must create a valid Identity Source in Single Sign-On for the users domain.

  ---

  explanation:

  Procedure

  1 Navigate to the vSphere Web Client login page.

  2 If the Use Windows session authentication check box is not available,

  click Download the Client Integration Plug-in at the bottom of the login page.

  3 If the browser blocks the installation by issuing certificate errors or by running a pop-up blocker,

  follow the Help instructions for your browser to resolve the problem.

  4 Close other browsers if you are prompted to do so.

  After installation, the plug-in is available for all browsers.

  5 Exit and restart your browser.

  After the restart, you can select the Use Windows session authentication check box.

  Reference:

  https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-C7BF3BD5-76E6-406F-8CF1-309D31F1DEBA.html

• Question 9:

  When attempting to connect to a vCenter Server, an administrator observes the following at the top of the vSphere Web Client:

  Could not connect to one or more vCenter Server Systems:https://vCenter.corp.com:443/sdk

  What three reasons could be preventing the vSphere Web Client from communicating with this vCenter Server? (Choose three.)

  A. The vCenter Server machine is not responding via the network.
  B. An incorrect entry for this vCenter Server exists in the Single Sign-On service.
  C. The SSL certificates do not match the FQDN address for the server.
  D. The Platform Services Controller is external to this vCenter Server.
  E. The DNS entry for the vCenter Server is incorrect.
  A. The vCenter Server machine is not responding via the network.
  B. An incorrect entry for this vCenter Server exists in the Single Sign-On service.
  C. The SSL certificates do not match the FQDN address for the server.

  ---

  explanation:

  This issue occurs in these situations:

  1.

  During the re-installation of vCenter Server, it is possible to have the same vCenter Server registered more than once to Single Sign-On (SSO).

  2.

  With a previous install of vCenter Server, SSL certificates are not overwritten or removed properly during an upgrade or re-installation.

  Note: If there are previous issues with the certificates, they may not be exposed until the installation and use of the 5.1 Web Client.

  Before proceeding with the steps in the Resolution section, ensure that you are not experiencing the issue identified in vSphere Web Client 5.1 reports this SSL warning after an installation or upgrade: Failed to verify the SSL certificate for

  one or more vCenter Server Systems (2036505).

  Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=2050273

• Question 10:

  Which three ports are used by the vSphere Web Client when connecting directly to an ESXi 6.x host? (Choose three.)

  A. 443 TCP
  B. 902 TCP and UDP
  C. 903 TCP
  D. 5480 TCP
  E. 9443 TCP and UDP
  A. 443 TCP
  B. 902 TCP and UDP
  C. 903 TCP

  ---

  explanation:

  

  Reference: https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-installation-setup-guide.pdf