VMware VCP6-DCV 2V0-621 Questions & Answers

• Question 231:

  Which three troubleshooting actions should an administrator take to address slow performance when deploying a virtual machine template? (Choose three.)

  A. Increase network throughput by adding additional uplinks to the vSwitch.

  B. Change the destination datastore or volume for the virtual machine template.

  C. Configure a Provisioning Traffic vmkernel port to perform the deployment operation.

  D. Reduce the size of the virtual machine template's virtual disk.

  E. Deploy the virtual machine template to the cluster and allow Distributed Resource Scheduler to register the virtual machine.

  Correct Answer: ABC

  Validate that each troubleshooting step below is true for your environment. Each step will provide instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

  1.

  Verify if the slow deployment is specific to one template or if it affects all templates. To properly test this, VMware recommends to create a brand new template and test the deployment. This provides a clean test of the environment. For more information if template deployment is slow for a single template, see Deploying a single template is slow in vCenter Server (1004028).

  2.

  If you are using ESX (not applicable to ESXi), verify that no processes are over utilizing the resources on the ESX Service Console. For more information, see Checking for resource starvation of the ESX Service Console (1003496).

  3.

  Verify that the network configuration on the ESX/ESXi host is optimized for the best performance, including speed and duplex settings. For more information, see Configuring the speed and duplex of an ESX/ESXi host network adapter (1004089).

  4.

  Verify that the firmware on the RAID controller or HBA is up to date. For more information, see Checking your firmware and BIOS levels to ensure compatibility with ESX/ESXi (1037257).

  5.

  Verify that the local storage or SAN array is configured correctly. For more information, see Slow ESX/ ESXi performance caused by misconfigured local storage or SAN array (1006602).

  6.

  Verify on ESX/ESXi 4.1 and above if the storage array devices in the environment support the hardware acceleration functionality and if they are responding correctly to VAAI primitives. If there is no VAAI support on the array cloning or Storage vMotion may fail at 18%. For more information see Cloning or Storage vMotion fails at 18% with the error: Failed to clone: Connection timed out (1029244).

  For further information on VAAI, see:

  1.

  vStorage APIs for Array Integration FAQ (1021976)

  2.

  Disabling the VAAI functionality in ESX/ESXi (1033665)

  Note: If your problem still exists after trying the steps in this article, please:

  1.

  Gather the VMware Support Script Data. For more information, see Collecting diagnostic information for VMware products (1008524).

  2.

  File a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request.

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

• Question 232:

  What are two reasons why a local flash device would be unavailable for use with Virtual SAN? (Choose two.)

  A. It has a VMFS datastore present.

  B. It is in use by the vFlash Read Cache feature.

  C. It is smaller than the minimum capacity required for Virtual SAN usage.

  D. It does not have any partitions created.

  Correct Answer: AB

  Local Flash Devices Are Unavailable for Use with Virtual SAN or Virtual Flash A local flash device becomes unavailable for virtual flash resource or Virtual SAN configuration when it is formatted with VMFS or any other file system. Problem When you attempt to configure either Virtual SAN or virtual flash resource, a local flash disk does not appear on the list of disks to be used. Cause This problem might occur when a local flash intended for use with either feature has been already formatted with VMFS. Neither Virtual SAN nor virtual flash can share the flash disk with VMFS or any other file system. Also, because virtual flash and Virtual SAN are mutually exclusive consumers of flash disks, both features cannot share the same flash disk. If the flash disk is already claimed by one feature, for example Virtual SAN, you are not be able to use it for another, such as virtual flash, unless you release the disk. Solution Use only unformatted flash disks for virtual flash resource and Virtual SAN configuration.

  1.

  Avoid formatting the flash disks with VMFS during ESXi installation or Auto Deploy.

  2.

  If the flash disk is already formatted with VMFS, remove the VMFS datastore. For information see the vSphere Storage documentation.

  3.

  To use the flash disk as a virtual flash resource, do not claim this disk for Virtual SAN. If the disk is claimed by Virtual SAN, remove the disk from Virtual SAN. The flash disk is released from Virtual SAN and becomes available on the list of disks to use with virtual flash. For information about removing disks from Virtual SAN, see the Administering VMware Virtual SAN documentation.

  4.

  If you intend to use the flash disk with Virtual SAN, do not use the disk for a virtual flash resource. If the flash disk is used as the virtual flash resource, remove the virtual flash configuration. The disk becomes available for Virtual SAN. See the vSphere Storage documentation.

  Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc% 2FGUID-A17F5D39-C1F3-47B1-9645-5C247412F370.html

• Question 233:

  What is the name of the command line utility that checks for VMFS5 metadata corruption?

  A. vmkfstools --check

  B. voma

  C. vmfsanalyzer

  D. esxcli vmfs check

  Correct Answer: B

  In ESXi 5.1, VMware introduced the vSphere On-disk Metadata Analyzer (VOMA) for performing VMFS file system metadata checks. This utility scans the VMFS volume metadata and highlights any inconsistencies to which you may be required to open a support request.

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

• Question 234:

  What are three reasons why a virtual machine might fail to power on? (Choose three.)

  A. The virtual machine is running on an ESXi host which has an expired license.

  B. The virtual machine is running on a datastore which has insufficient disk space for the .vswp file.

  C. The virtual machine is in a cluster with vSphere HA Admission control enabled.

  D. The virtual machine has a disconnected network adapter.

  E. The virtual machine does not have a Virtual Hard Disk assigned.

  Correct Answer: ABC

  When a virtual machine fails to power on, a reason may be logged to the vmware.log file for the virtual machine, to the management agent logs, or presented in the client. Review any messages and consider these points:

  1.

  The virtual machine monitor may be asking a question to be answered during startup. A virtual machine may pause the power-on task at 95% to obtain additional information from the administrator. For more information, see Powering on a virtual machine pauses at 95% while waiting for a question to be answered (1027096).

  2.

  Creating a new power-on task may fail if another task for the virtual machine or other component is already in progress, and multiple concurrent tasks on the object are not permitted. For more information, see:

  1.

  Collecting information about tasks in VMware ESX and ESXi (1013003)

  2.

  vCenter operation times out with the error: Operation failed since another task is in progress (1004790).

  3.

  A virtual machine may fail to power on if licensing requirements are not met. For more information, see:

  1.

  Cannot Power on Virtual Machines, "Not enough licenses installed to perform the operation" Error Message (7114568)

  2.

  The Managing ESX/ESXi and vCenter Server Licenses section of the Datacenter Administration Guide for vSphere 4 or higher

  3.

  The VirtualCenter and ESX Server Licensing Overview section of the Installation Guide for VMware Infrastructure 3

  4.

  The virtual machine may be configured to reserve physical memory on the host, but the host memory is over-committed and the required memory is unavailable. For more information, see:

  1.

  Virtual machine does not power on when there is high CPU reservation (1001637)

  2.

  Powering on a virtual machine fails with the error: memoryAllocation.reservation (1036914).

  5. The virtual machine may be starting in a VMware High Availability cluster with strict admission control enabled, and there are insufficient resources to guarantee failover for all virtual machines. For more information, see:

  1.

  Implications of enabling or disabling VMware HA strict admission control when using DRS and VMware DPM (1007006)

  2.

  Diagnosing insufficient fail over capacity on a VMware High Availability Cluster (1003717)

  3.

  Automating High Availability (HA) Services with VMware HA whitepaper

  6.

  A file required for starting the virtual machine, such as a virtual disk or swap file, may be unavailable or missing. For more information, see Investigating virtual machine file locks in ESX/ESXi (10051).

  7.

  The virtual machine may have been previously suspended and making use of CPU features which are unavailable or incompatible with the CPU features available on this host. The virtual machine cannot be started without the required features. For more information, see:

  1.

  Powering on a virtual machine from a suspend state or reverting to a snapshot fails (1038218)

  2.

  Virtual machines fail to power on due to a suspend state from an incompatible CPU type (1000241)

  3.

  To retain the suspended state, move the virtual machine back to the host it was originally suspended on

  and power-on the virtual machine there.

  4.

  To discard the suspend state, and power on the virtual machine in a crash-consistent manner, see

  Unable to power on a suspended virtual machine using vSphere Client (1004606).

  8.

  The virtual machine may require both a VT-capable CPU and the VT feature to be enabled in the host

  system's BIOS. This is true for all 64-bit virtual machines. If the VT feature is unavailable, the virtual

  machine may produce the message msg.cpuid.noLongmode. For more information, see Enabling VT on

  Intel EM64T Systems for ESX Server 3 (3282933).

  9.

  The virtual machine may require another CPU feature which is unavailable on this host. The virtual

  machine may produce a message similar to msg.cpuid., identifying the specific feature it

  has been configured to require. Move the virtual machine back to the host which has the required CPU

  features, or edit the virtual machine's configuration to remove the requirement.

  10.

  The virtual machine may start, but quickly fail with an error during startup. Review the contents of the

  vmware.log file in the virtual machine's directory for any errors or warnings, and search the Knowledge

  Base for the error or warning.

  Base your troubleshooting on the specific messages seen in the logs. For more information, see:

  1.

  Determining why a virtual machine was powered off or restarted (1019064)

  2.

  Interpreting virtual machine monitor and executable failures (1019471)

  11.

  If the virtual machine does successfully power on, but the guest OS doesn't start correctly, there may

  be an incompatibility between the virtual hardware and drivers within the guest OS. For example, a missing

  SCSI driver may be required for booting. For more information, see Windows virtual machine configured to

  use a BusLogic SCSI controller reports that the operating system does not support the controller

  (2007603).

  12.

  If the guest OS, or a driver or application within the virtual machine experiences a problem during

  startup, the guest OS may become unresponsive. Continue troubleshooting. For more information, see

  Troubleshooting unresponsive guest operating system issues (1007818).

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

• Question 235:

  What is the minimum Virtual Hardware version required for vFlash Read Cache?

  A. Version 8

  B. Version 9

  C. Version 10

  D. Version 11

  Correct Answer: C

  Virtual Machines vSphere Flash Read Cache is available only to virtual machines with hardware version 10 (VMX-10). All legacy virtual machine hardware must be upgraded to hardware version 10 to use Virtual Flash Read Cache.

  Reference: https://www.vmware.com/files/pdf/vSphere_55_Flash_Read_Cache_Whats_New_WP.pdf

• Question 236:

  An administrator is troubleshooting a virtual machine that has unexpectedly powered off.

  Which two logs should be used to troubleshoot the issue? (Choose two.)

  A. vmware.log

  B. hostd.log

  C. syslog.log

  D. shell.log

  Correct Answer: AB

• Question 237:

  An administrator notices that one virtual machine is in an orphaned state.

  What are two reasons that a virtual machine can appear as orphaned? (Choose two.)

  A. A VMware High Availability host failure has occurred.

  B. The virtual machine was unregistered directly on the host.

  C. The ESXi host is disconnected.

  D. The user does not have privilege to access the virtual machine.

  Correct Answer: AB

  Explanation: Please refer to the following link to understand more about the Orphaned State: https:// kb.vmware.com/selfservice/microsites/search.do?language=en_USandcmd=displayKCandexternalId=1003742

• Question 238:

  An administrator is observing slow performance of the vCenter Inventory Service and observes the entries from the wrapper.log file:

  Exception in thread "tomcat-exec-2" java.lang.OutOfMemoryError: Java heap spaceException in thread "http-bio-0.0.0.0-10443-Acceptor-0" java.lang.OutOfMemoryError: Java heap space

  What should the administrator do to resolve the problem?

  A. Increase the memory resources of the vCenter Server.

  B. Increase the values using cloudvm-ram-size.

  C. Increase the memory resouces of the Platform Services Controller.

  D. Increase the wrapper.java.maxmemory value in wrapper.conf.

  Correct Answer: A

  Cause This issue is occurs if the allocated JVM maximum memory heap is too low for the VMware Inventory service, VMware Profile-Driven Storage service, or VMware VirtualCenter Web Management service. Several core vCenter Server services use individual configuration files (wrapper.conf) to determine the JVM maximum heap size that each service can use. The VMware Inventory service, VMware Profile-Driven Storage service, and VMware VirtualCenter Web Management service rely on the JVM maximum memory heap configured in their individual wrapper.conf file and play a critical role in the functionality of vCenter Server. Note: If vCenter Server 5.5 has recently been updated beyond 5.5 U2, see Upgrading VMware vCenter Server 5.5 to 5.5 U2 or later reduces the JVM maximum memory heap size (2114669). Resolution This is a known issue affecting vCenter Server 5.x. To resolve this issue, manually set the inventory size. To change the JVM maximum memory heap size for a Windows installed vCenter Server 5.x, see, see Configuring Tomcat server settings in VMware vCenter Server 5.1 and 5.5 (2021302). To manually set the inventory size in vCenter Server Appliance 5.x:

  1.

  Log in to vCenter Server Appliance administration interface (VAMI) URL:

  https://vCenter_Server_FQDN\IP:5480

  2.

  Click the Services tab.

  3.

  Change the Inventory Size to Medium or Large, depending on your environment.

  Note: The system memory may need to be increased when changing this setting. For more information on environment sizing, see theConfigure Inventory Size for the VMware vCenter Server Appliance section of the Configuring Hosts and vCenter Server guide.

  4.

  Restart the VMware Profile-Driven Storage Service and VMware Inventory Service. For more information, see Stopping, starting, or restarting vCenter Server Appliance services (2054085).

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

• Question 239:

  An administrator is troubleshooting network communications between the vCenter Server and the ESXi 6.x host.

  Which log shows the interaction events between these components?

  A. /var/log/syslog.log

  B. /var/log/hostd.log

  C. /var/log/vpxa.log

  D. /var/log/fdm.log

  Correct Answer: C

  When an ESXi 5.1 / 5.5 host is managed by vCenter Server 5.1 and 5.5, two components are installed, each with its own logs:

  1.

  /var/log/vpxa.log: vCenter Server vpxa agent logs, including communication with vCenter Server and the Host Management hostd agent.

  2.

  /var/log/fdm.log: vSphere High Availability logs, produced by the fdm service. For more information, see the vSphere HA Security section of the vSphere Availability Guide.

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

• Question 240:

  After successfully adding a new ESXi 6.x host to vCenter Server, an administrator sees it as Not Responding in the vSphere Web Client interface a few minutes later.

  If the issue is caused by a network firewall blocking traffic, which port must be opened to correct this specific problem?

  A. 443 (TCP)

  B. 443 (UDP)

  C. 902 (TCP)

  D. 902 (UDP)

  Correct Answer: D

  Port: 902 (Default) Purpose: Host access to other hosts for migration and provisioning Authentication traffic for ESXi and remote console traffic (xinetd/vmware-authd) vSphere Client access to virtual machine consoles (UDP) Status update (heartbeat) connection from ESXi to vCenter Server Traffic Type Incoming and outgoing TCP, outgoing UDP

  Reference: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc_50% 2FGUID-ECEA77F5-D38E-4339-9B06-FF9B78E94B68.html