VMware VMware Certifications 2V0-621 Questions & Answers

• Question 211:

  Which three logs can be reviewed to troubleshoot a vCenter Server upgrade failure? (Choose three.)

  A. vminst.log

  B. vim-vcs-msi.log

  C. pkgmgr.log

  D. vc-upgrade.log

  E. firstboot.log

  Correct Answer: ABC

  Retrieve Installation Logs Manually You can retrieve the installation log files manually for examination. Procedure 1 Navigate to the installation log file locations. %PROGRAMDATA%\VMware\vCenterServer\logs directory, usually C:\ProgramData\VMware\vCenterServer\logs %TEMP% directory, usually C:\Users\username\AppData\Local\Temp The files in the %TEMP% directory include vminst.log, pkgmgr.log, pkgmgr-comp-msi.log, and vim-vcsmsi.log.

  2 Open the installation log files in a text editor for examination.

  Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUIDCF80C555-BFB1-4FF1-B4E6-6935D424838E.html

• Question 212:

  An administrator is unable to patch an ESXi 6.x host using VMware Update Manager.

  What is an alternative option for patching a host?

  A. Upload the offline bundle to a datastore and execute the command esxcli software vib install -d to apply it manually.

  B. Upload the vib to a datastore and execute the command esxcli software vib install -d to apply it manually.

  C. Upload the offline bundle to a datastore and execute the command esxupdate install -v to apply it manually.

  D. Upload the vib to a datastore and execute the command esxupdate install -v to apply it manually.

  Correct Answer: A

  Update a Host with Individual VIBs You can update a host with VIBs stored in a software depot that is accessible through a URL or in an offline ZIP depot. Important If you are updating ESXi from a zip bundle in a VMware-supplied depot, either online from the VMware Web site or downloaded locally, VMware supports only the update method specified for VMware-supplied depots in the topic Upgrade or Update a Host with Image Profiles. The esxcli software vib update and esxcli software vib install commands are not supported for upgrade operations. See Differences Between vSphere Upgrades and Updates and Upgrade or Update a Host with Image Profiles

  Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID1E773360-CB1C-4BC2-B2A4-B73AB5706FAF.html

• Question 213:

  An administrator has migrated a vCenter Server Appliance from version 5.5 to version 6.x. During the migration, the administrator selected DHCP for the appliance and obtained a hostname from the DHCP server. The administrator adjusts the hostname after the migration and uses a static IP and hostname.

  What should the administrator do immediately after this change to prevent service failures?

  A. Regenerate the SSL certificates.

  B. Re-register components to Single Sign-On.

  C. Update the /etc/hosts file.

  D. Execute the command services.restart vmware-vpxd.

  Correct Answer: A

  This is a known issue affecting vCenter Server 6.0.

  Currently, there is no resolution.

  To work around this issue, regenerate the SSL certificates on the vCenter Server 5.x before upgrading to

  6.0.

  To regenerate the SSL certificates on the vCenter Server 5.x before upgrading to 6.0,

  LinkKB: https://kb.vmware.com/selfservice/microsites/search.do?

  language=en_USandcmd=displayKCandexternalId=2110943

• Question 214:

  An administrator is unable to upgrade a vCenter Server Appliance from version 5.1 Update 2 to version

  6.0.

  What is a likely reason for this?

  A. vCenter Server Appliance 6.0 does not support upgrades from version 5.1 Update 2.

  B. vCenter Server Appliance must be joined to an Active Directory domain before upgrading to version

  6.0.

  C. vCenter Server Appliance 5.1 Update 2 uses an incompatible database for upgrading to version 6.0.

  D. vCenter Server Appliance 6.0 must be upgraded using the vSphere Web Client.

  Correct Answer: A

  If your current vCenter Server Appliance version is earlier than 5.1 Update 3, you must upgrade to 5.1 Update 3 or later before upgrading to vCenter Server Appliance 6.0. Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID66836F60-A095-4749-86C9-1DAFB5D21070.html

• Question 215:

  Refer to the Exhibit.

  

  An administrator is using the esxtop command to troubleshoot storage performance issues on a virtual machine. The esxtop capture is shown in the Exhibit.

  Based on the exhibit, which two statements are true? (Choose two.)

  A. The iSCSI device is experiencing high latency.

  B. The ESXi kernel is experiencing high latency.

  C. The Guest OS is experiencing high latency and response time.

  D. The NFS device is experiencing high latency.

  Correct Answer: AC

  Using esxtop to identify storage performance issues for ESX / ESXi (multiple versions) (1008205)

  Note: In ESXi 5.x and later, you may see messages indicating that performance has deteriorated. For more

  information, see Storage device performance deteriorated (2007236).

• Question 216:

  Which two scenarios could cause Storage DRS to be disabled on a Virtual Disk (VMDK)? (Choose two.)

  A. The VMDK is an independent disk.

  B. The virtual machine has vSphere Fault Tolerance enabled.

  C. The VMDK is hosted on NFS storage.

  D. The virtual machine has a CD-ROM/ISO image connected.

  Correct Answer: AB

  Storage DRS is Disabled on a Virtual Disk Even when Storage DRS is enabled for a datastore cluster, it might be disabled on some virtual disks in the datastore cluster. Problem

  You have enabled Storage DRS for a datastore cluster, but Storage DRS is disabled on one or more virtual

  machine disks in the datastore cluster.

  Cause

  The following scenarios can cause Storage DRS to be disabled on a virtual disk.

  1.

  A virtual machine's swap file is host-local (the swap file is stored in a specified datastore that is on the host). The swap file cannot be relocated and Storage DRS is disabled for the swap file disk.

  2.

  A certain location is specified for a virtual machine's .vmx swap file. The swap file cannot be relocated and Storage DRS is disabled on the .vmx swap file disk.

  3.

  The relocate or Storage vMotion operation is currently disabled for the virtual machine in vCenter Server (for example, because other vCenter Server operations are in progress on the virtual machine). Storage DRS is disabled until the relocate or Storage vMotion operation is re-enabled in vCenter Server.

  4.

  The home disk of a virtual machine is protected by vSphere HA and relocating it will cause loss of vSphere HA protection.

  5.

  The disk is a CD-ROM/ISO file.

  6.

  If the disk is an independent disk, Storage DRS is disabled, except in the case of relocation or clone placement.

  7.

  If the virtual machine has system files on a separate datastore from the home datastore (legacy), Storage DRS is disabled on the home disk. If you use Storage vMotion to manually migrate the home disk, the system files on different datastores will be all be located on the target datastore and Storage DRS will be enabled on the home disk.

  8.

  If the virtual machine has a disk whose base/redo files are spread across separate datastores (legacy), Storage DRS for the disk is disabled. If you use Storage vMotion to manually migrate the disk, the files on different datastores will be all be located on the target datastore and Storage DRS will be enabled on the disk.

  9.

  The virtual machine has hidden disks (such as disks in previous snapshots, not in the current snapshot). This situation causes Storage DRS to be disabled on the virtual machine.

  10.

  The virtual machine is a template.

  11.

  The virtual machine is vSphere Fault Tolerance-enabled.

  12.

  The virtual machine is sharing files between its disks.

  13.

  The virtual machine is being Storage DRS-placed with manually specified datastores

  Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc% 2FGUID-B749AAA0-7B67-4A79-BEDC-395DFEC9FC60.html

• Question 217:

  An administrator attempts to place a Storage DRS enabled Datastore into Maintenance Mode. The task never completes, and the Entering Maintenance Mode status remains at 1%.

  Which two actions should the administrator take to resolve this problem? (Choose two.)

  A. Set the Storage DRS advanced option IgnoreAffinityRulesForMaintenance = 1.

  B. Set the Storage DRS advanced option IgnoreAffinityRulesForMaintenance = 0.

  C. Disable Storage DRS affinity rules associated with this datastore cluster.

  D. Enable Storage DRS affinity rules associated with this datastore cluster.

  Correct Answer: AC

  Explanation: Problem

  A datastore in a datastore cluster cannot enter 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.

  Solution

  If Storage DRS is disabled, enable it or determine why it is disabled. See Storage DRS is Disabled on a

  Virtual Disk for reasons why Storage DRS might be disabled. If Storage DRS rules are preventing Storage

  DRS from making migration recommendations, you can remove or disable particular rules.

  In the vSphere Client inventory, right-click the datastore cluster and select Edit Settings.

  Select Rules and click the rule.

  Click Remove.

  Click OK.

  Alternatively, if Storage DRS rules are preventing Storage DRS from making migration recommendations,

  you can set the Storage DRS advanced option IgnoreAffinityRulesForMaintenance to 1.

  In the vSphere Client inventory, right-click the datastore cluster and select Edit Settings.

  Select SDRS Automation and click Advanced Options.

  Enter 1 in the Value column for IgnoreAffinityRulesForMaintenance.

  Click OK.

  Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%

  2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-91D4FBBC-0677-44DA-B0F243A3504F8CA0.html

• Question 218:

  An administrator creates a Private VLAN with a Primary VLAN ID of 2. The administrator than creates three Private VLANs as follows:

  1.

  Marketing

  2.

  PVLAN ID. 4

  3.

  PVLAN Type. Isolated

  4.

  Accounting

  5.

  PVLAN ID. 5

  6.

  PVLAN Type. Community

  7.

  Secretary

  8.

  PVLAN ID. 17

  9.

  PVLAN Type. Isolated

  Users in the Accounting PVLAN are reporting problems communicating with servers in the Marketing PVLAN.

  Which two actions could the administrator take to resolve this problem? (Choose two.)

  A. Change the PVLAN type for the Accounting network to Promiscuous.

  B. Change the PVLAN ID for the Accounting network to 2.

  C. Change the PVLAN type for Marketing network to Promiscuous.

  D. Change the PVLAN ID for Accounting network to 4.

  Correct Answer: AB

  Explanation: Please refer to this link for understanding network connectivity issues in detail: https:// kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=1004109

• Question 219:

  An administrator tries to capture network traffic for a virtual machine, but cannot see the expected traffic in the packet capture tool.

  Which step can resolve the problem?

  A. Migrate the virtual machine to a Distributed Virtual Switch.

  B. Enable Promiscous Mode on the relevant port group.

  C. Modify the default value of MAC Address changes.

  D. Enable Forged Transmits on the virtual machine.

  Correct Answer: B

  Explanation: When promiscuous mode is enabled at the portgroup level, objects defined within that portgroup have the option of receiving all incoming traffic on the vSwitch. Interfaces and virtual machines within the portgroup will be able to see all traffic passing on the vSwitch, but all other portgroups within the same virtual switch do not.

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

• Question 220:

  After configuring a Virtual SAN cluster, an administrator using the vSphere Web Client notices that the Virtual SAN datastore is smaller than expected. The cluster contains:

  1.

  Three ESXi hosts

  2.

  Each host has one 10GB SDD

  3.

  Each host has one 100GB HDD

  Why would the Virtual SAN datastore show as 100GB instead of 300GB?

  A. There is a network problem with the Virtual SAN vmkernel ports.

  B. The Virtual SAN VASA provider is disabled.

  C. vSphere High Availability is enabled on the Virtual SAN cluster.

  D. The Virtual SAN cluster must be managed using the vSphere Web Client.

  Correct Answer: A

  Explanation: Here we have three ESXI hosts (each with 100GB HDD) which makes the complete storage to 300 GB. It generally shows 100GB instead of 300GB because the three hosts are not able to connect properly due to network issues.