VMware VCP6-DCV 2V0-621 Questions & Answers

• Question 51:

  An administrator is configuring resource pools for a vSphere 6.x cluster. The cluster has these characteristics:

  1.

  Five ESXi 6.x hosts

  2.

  Six cores per host

  3.

  70 virtual machines with 1 vCPU each

  The administrator configures three resource pools and places the virtual machines into the pools, as follows:

  1.

  Production pool ?High Share value with 40 virtual machines

  2.

  Infrastructure pool ?Medium Share value with 20 virtual machines

  3.

  Development pool ?Low Share value with 10 virtual machines

  Given this configuration, what is the expected performance for each group of virtual machines during contention?

  A. Virtual machines in the Production pool will perform two times as well as those in the Infrastructure pool.

  B. Virtual machines in the infrastructure pool will perform four times as well as those in the Development pool.

  C. Virtual machines in all resource pools will perform equally.

  D. Virtual machines in the Development pool will perform two times as well as those in the Infrastructure pool.

  Correct Answer: C

• Question 52:

  Refer to the Exhibit.

  

  What will be the result of selecting the highlighted device?

  A. Datastore will grow up to 200.01GB using the remaining free space on the device.

  B. Datastore will add 200.01GB by adding the device as a second extent.

  C. The device size can be expanded to be larger than 200.01 GB in size.

  D. The device is not suitable for this operation.

  Correct Answer: A

  When you need to create new virtual machines on a datastore, or when the virtual machines running on this datastore require more space, you can dynamically increase the capacity of a VMFS datastore.(200 GB) Use one of the following methods: -Add a new extent. An extent is a partition on a storage device, or LUN. You can add up to 32 new extents of the same storage type to an existing VMFS datastore. The spanned VMFS datastore can use any of all its extents at any time. It does not need to fill up a particular extent before using the next one. -Grow an extent in an existing VMFS datastore, so that it fills the available adjacent capacity. Only extents with free space immediately after them are expandable. https://kb.vmware.com/kb/1017662

• Question 53:

  A device's vStorage API for Array Integration (VAAI) support status command line output shows:

  naa.500253825002a865 VAAI Plugin Name: ATS Status: unsupported Clone Status: unsupported Zero Status: supported Delete Status: unsupported

  What is the corresponding VAAI support status in the vSphere Web Client?

  A. Unknown

  B. Supported

  C. Not supported

  D. Unsupported

  Correct Answer: A

  : If you go to Host > Configuration > Storage, you can see the Hardware Acceleration Status in the panel on the right side.

  For each storage device and datastore, the vSphere Client displays the hardware acceleration support status in the Hardware Acceleration column of the Devices view and the Datastores view.

  The status values are Unknown, Supported, and Not Supported. The initial value is Unknown. The status changes to Supportedafter the host successfully performs the offload basic operations. If the offload operation fails, the status changes to Not Supported.

  To determine if your storage device supports VAAI, test the Full Copy VAAI primitive:

  1.

  Using the vSphere Client, browse the datastore and locate a virtual disk (VMDK) of at least 4 MB that is

  not in use.

  2.

  Copy the virtual disk to a new file.

  3.

  Check the Hardware Acceleration status to verify that it changes from Unknown to either Supported or

  Not Supported.

  Note: VAAI primitives can also be tested by creating a virtual machine with at least one new virtual disk, or

  cloning a virtual machine.

  Can I check the VAAI status from the command line?

  On ESXi 5.x

  To check the VAAI status, run this command:

  # esxcli storage core device vaai status get

  You see output similar to:

  mpx.vmhba1:C0:T1:L0 VAAI Plugin Name: ATS Status: unsupported Clone Status: unsupported Zero Status: unsupported Delete Status: unsupported

  mpx.vmhba1:C0:T0:L0 VAAI Plugin Name: ATS Status: unsupported Clone Status: unsupported Zero Status: unsupported Delete Status: unsupported

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

• Question 54:

  Which two solutions require Physical Mode Raw Device Mapping (RDM)? (Choose two.)

  A. Direct access to the storage array device

  B. Virtual Machine Snapshots

  C. Hardware Acceleration

  D. Guest Clustering across ESXi hosts

  Correct Answer: AD

  Explanation: A-) Note: RDM is not available for direct-attached block devices or certain RAID devices. You

  cannot map a disk partition as RDM. RDMs require the mapped device to be a whole LUN.(storage array

  device) D-) Guest Clustering----- Physical mode is useful while running SAN management agents or other

  SCSI target-based software in the virtual machine.

  Physical mode also allows virtual-to-physical clustering for cost-effective high availability.

  Virtual Machine Snapshots are not available when the RDM is used in physical compatibility mode.

  You can use this mode for Physical-to-virtual clustering and cluster-across-boxes.

  VMFS5 supports greater than 2 TB disk size for RDMs in physical compatibility mode only. These

  restrictions apply:

  You cannot relocate larger than 2 TB RDMs to datastores other than VMFS5.

  You cannot convert larger than 2 TB RDMs to virtual disks, or perform other operations that involve RDM

  to virtual disk conversion. Such operations include cloning.

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

  language=en_USandcmd=displayKCandexternalId=1037959

• Question 55:

  What is the command to list multipathing modules on an ESXi 6.x host?

  A. esxcli storage core list plugin --plugin-class=MP

  B. esxcli storage core list plugin --class-plugin=MP

  C. esxcli storage core plugin list --plugin-class=MP

  D. esxcli storage core plugin list --class-plugin=MP

  Correct Answer: C

  

  Reference: https://pubs.vmware.com/vsphere50/index.jsp?topic=%2Fcom.vmware.vcli.ref.doc_50% 2Fesxcli_storage.html

• Question 56:

  Which two statements are true regarding Storage Multipathing Plug-Ins? (Choose two.)

  A. The default Path Selection Policy is VMW_PSP_MRU for iSCSI or FC devices.

  B. The default Path Selection Policy is VMW_PSP_FIXED for iSCSI or FC devices.

  C. VMW_PSP_MRU is typically selected for ALUA arrays by default.

  D. VMW_PSP_FIXED is typically selected for ALUA arrays by default.

  Correct Answer: BC

  : By default, the VMware NMP supports the following PSPs:

  VMW_PSP_MRU The host selects the path that it used most recently. When the path becomes unavailable, the host selects an alternative path. The host does not revert back to the original path when that path becomes available again. There is no preferred path setting with the MRU policy. MRU is the default policy for most active-passive storage devices. Displayed in the vSphere Client as the Most Recently Used (VMware) path selection policy. VMW_PSP_FIXED The host uses the designated preferred path, if it has been configured. Otherwise, it selects the first working path discovered at system boot time. If you want the host to use a particular preferred path, specify it manually. Fixed is the default policy for most active-active storage devices. Note If the host uses a default preferred path and the path's status turns to Dead, a new path is selected as preferred. However, if you explicitly designate the preferred path, it will remain preferred even when it becomes inaccessible.

  Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc% 2FGUID-B7AD0CA0-CBE2-4DB4-A22C-AD323226A257.html

• Question 57:

  Which two tasks does the Pluggable Storage Architecture (PSA) perform? (Choose two.)

  A. Handles I/O queueing to the logical devices.

  B. Handles physical path discovery, but is not involved in the removal.

  C. Handles physical path discovery and removal.

  D. Handles I/O queueing to FC storage HBAs.

  Correct Answer: AC

  :

  the PSA performs the following tasks:

  Loads and unloads multipathing plug-ins.

  Hides virtual machine specifics from a particular plug-in.

  Routes I/O requests for a specific logical device to the MPP managing that device.

  Handles I/O queueing to the logical devices.

  Implements logical device bandwidth sharing between virtual machines.

  Handles I/O queueing to the physical storage HBAs.

  Handles physical path discovery and removal.

  Provides logical device and physical path I/O statistics.

  Reference: https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%

  2FGUID-C1C4A725-8BE4-4875-919E-693812961366.html

• Question 58:

  Which statement is true for the Path Selection Plug-In VMW_PSP_MRU?

  A. VMW_PSP_MRU is default for a majority of active-active and active-passive arrays.

  B. VMW_PSP_MRU will remain on the selected path even if the state were to change.

  C. VMW_PSP_MRU is recommended for Virtual SAN.

  D. VMW_PSP_MRU will have no preferred path setting for the Plug-In.

  Correct Answer: D

  VMW_PSP_MRU The host selects the path that it used most recently. When the path becomes unavailable, the host selects an alternative path. The host does not revert back to the original path when that path becomes available again. There is no preferred path setting with the MRU policy. MRU is the default policy for most active-passive storage devices.

  Reference: https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc% 2FGUID-B7AD0CA0-CBE2-4DB4-A22C-AD323226A257.html

• Question 59:

  Where is a Virtual SAN Fault Domain configured?

  A. VMware Virtual SAN Cluster configuration

  B. VMware High Availability Cluster configuration

  C. Distributed Resource Scheduler configuration

  D. Datacenter Advanced Settings configuration

  Correct Answer: A

  Procedure

  1 Navigate to the Virtual SAN cluster in the vSphere Web Client.

  2 Click the Manage tab and click Settings.

  3 Under Virtual SAN, click Fault Domains and Stretched Cluster.

  

  4 Click the Create a new fault domain icon ( ).

  5 Type the fault domain name.

  6 From the Show drop-down menu, select Hosts not in fault domain to view the list of hosts that are not

  assigned to a fault domain or select Show All Hosts to view all hosts in the cluster.

  7 Select one or more hosts to add to the fault domain.

  A fault domain cannot be empty. You must select at least one host to include in the fault domain.

  8 Click OK.

  The selected hosts appear in the fault domain

  Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.virtualsan.doc

  %2FGUID-C365ACE8-7485-4463-A12C-71D1917A4930.html

• Question 60:

  An administrator created a six node Virtual SAN cluster, created a fault domain, and moved three of the six nodes into that domain.

  A node that is a member of the fault domain fails.

  What is the expected result?

  A. The remaining two fault domain members are treated as failed.

  B. The remaining two fault domain members stay protected by the domain.

  C. One of the non-member nodes will be automatically added to the fault domain.

  D. VMware High Availability will restart virtual machines on remaining nodes in the domain.

  Correct Answer: A

  Defines the number of host and device failures a virtual machine object can tolerate. For n failures tolerated, n+1 copies of the virtual machine object are created and 2*n+1 hosts contributing storage are required. When provisioning a virtual machine, if you do not choose a storage policy, Virtual SAN assigns this policy as the default virtual machine storage policy. Default value is 1. Maximum value is 3. If fault domains are configured, 2n+1 fault domains with hosts contributing capacity are required. A host, which is not part of any fault domain is considered as its own single host fault domain. Default value is 1. Maximum value is 3. NOTE If you do not want Virtual SAN to protect a single mirror copy of virtual machine objects, you can specify the Number of failures to tolerate=0. However, the host might experience unusual delays when entering maintenance mode. The delay occurs because Virtual SAN has to evacuate the object from the host for the maintenance operation to complete successfully. Setting the Number of failures to tolerate=0 means that your data is unprotected, and you might lose data when the Virtual SAN cluster encounters a device failure. NOTE When creating a new storage policy, if you do not specify any value for Number of failures to tolerate, by default, Virtual SAN creates a single mirror copy of the virtual machine objects and tolerates only one failure. However, in the event of a multiple component failures your data might be at risk. link: https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/virtual-san-60-administrationguide.pdf