VMware VCP6-DCV 2V0-621 Questions & Answers

• Question 11:

  Which condition would cause a vCenter Server installation to fail when installing on a Windows virtual

  machine?

  A. The virtual machine does not have at least four vCPUs.

  B. The virtual machine is running Windows Server 2008.

  C. The virtual machine has an E1000 network device.

  D. The virtual machine does not have 16GB of RAM.

  Correct Answer: B

  The vCenter Server installation or uninstallation process might fail or stop responding on Windows Server

  2008 R1 SP2

  The Windows Installer on Windows Server 2008 R1 SP2 has issues with handling multiple packages.

  Because of these issues the vCenter Server installation might stop responding, or if you attempt to install

  and uninstall vCenter Server a few times, the process might fail.

  Workaround: Apply the patch from Microsoft KB 981669 which addresses the Windows Installer issue.

  Reference: https://www.vmware.com/support/vsphere6/doc/vsphere-esxi-vcenter-server-60-releasenotes.html#compatibility

• Question 12:

  After deploying a vSphere Platform Services Controller (PSC), an administrator is unable to install vCenter

  Server. The error displayed is:

  Could not contact Lookup Service. Please check VM_ssoreg.log.

  Which two actions can be taken to correct this problem? (Choose two.)

  A. Verify that the clocks on the host machines running the PSC, vCenter Server, and the vSphere Web Client are synchronized.

  B. Configure a valid Identity Source for the Platform Services Controller in the vSphere Web Client.

  C. Ensure that there is no firewall blocking port 7444 between the PSC and vCenter Server.

  D. Uninstall and reinstall the Platform Services Controller software.

  Correct Answer: AC

  1.

  Verify that the clocks on the host machines running vCenter Single Sign-On, vCenter Server, and the

  Web Client are synchronized.

  2.

  View the specific log file found in the error message.

  In the message, system temporary folder refers to %TEMP%.

  3.

  Within the log file, search for the following messages.

  The log file contains output from all installation attempts. Locate the last message that shows Initializing

  registration provider...

  

  Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc% 2FGUID-B8D60389-AF95-4368-8AB2-D282CBE0C4A9.html

• Question 13:

  An administrator is unable to start the vCenter Server service. The vpxd.log file shows this service failure:

  [13308 error 'Default' opID=622892-371bf717] CoreDump: Unable to write minidump [13308 error 'Default' opID=622892-371bf717] error -2147024784 : There is not enough space on the disk.

  What is preventing the start of the service?

  A. Insufficient space on the vCenter Server

  B. Insufficient space on the Database Server

  C. Insufficient space on the VMFS volume

  D. Insufficient space on the ESXi ramdisk

  Correct Answer: A

  Symptoms

  1.

  Cannot start VMware VirtualCenter Server service

  2.

  In the vpxd.log file located at C:\ProgramData\VMware\VMware VirtualCenter\Logs\, you see backtraces similar to:

  [VpxdClientAdapter] Got vmacore exception: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full [18244 error 'vpxdvpxdVmomi' opID=HB-host-6161@193472-2b600f1f] [VpxdClientAdapter] Backtrace: --> backtrace[00] rip 000000018018cd7a --> backtrace[01] rip 0000000180106c48 --> backtrace[02] rip 000000018010803e --> backtrace[03] rip 000000018009 [09356 verbose 'VpxProfiler' opID=HB-host-8535@1072225-79714cc6] [1-] [ORM] Update: vim.vm.ConfigInfo, Id: 12892 (took 0 ms) [12016 error 'vpxdvpxdVmomi' opID=HB-host-154@86503-2d0e7772] [VpxdClientAdapter] Got vmacore exception: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full [12016 error 'vpxdvpxdVmomi' opID=HB-host-154@86503-2d0e7772] [VpxdClientAdapter] Backtrace: --> backtrace[00] rip 000000018018cd7a

  Cause This issue occurs because vCenter Server does not have sufficient hard disk space to be allocated for the buffer.

  Reference: https://kb.vmware.com/selfservice/search.do? cmd=displayKCanddocType=kcanddocTypeID=DT_KB_1_1andexternalId=2083927

• Question 14:

  Refer to the Exhibit.

  

  An administrator is attempting to enable Enhanced vMotion Compatibility (EVC), but receives the error

  shown in the Exhibit.

  Which condition would explain the error?

  A. The ESXi hosts are not licensed for EVC.

  B. The administrator does not have privileges to enable EVC.

  C. The ESXi host CPU has the Intel No-Execute feature disabled.

  D. The administrator has turned on Intel Virtualization Technology.

  Correct Answer: C

  Explanation: To resolve the issue, you must enable both No-Execute Memory Protection and Virtualization Technology features in order for EVC to function. Consult the documentation for your hardware for more information.

  To resolve this issue:

  1.

  Enter the BIOS setup (F9 on most systems at boot).

  2.

  Select Advanced Options.

  3.

  Select Processor Options.

  4.

  Change No-Execute Memory Protection to Enabled, if necessary.

  5.

  Change Intel Virtualization Technology to Enabled, if necessary.

  6.

  Reboot the host.

  7.

  Enable EVC in the cluster settings.

  Notes:

  1.

  Hardware Virtualization is called Intel VT on Intel processors and AMD-V on AMD processors.

  2.

  Execute Protection is called Intel eXecute Disable (XD) on Intel processors and AMD No eXecute (NX) on AMD processors.

• Question 15:

  Refer to the Exhibit.

  

  Refer to the Exhibit. The list of devices attached to vmhba1 will be the basis for configuring a VMware Virtual SAN using Manual Mode.

  Based on the exhibit, which two combinations of devices should be used to create Disk Group(s)? (Choose two.)

  A. One Disk Group with one Flash Drive and three HDDs

  B. Two Disk Groups with one Flash Drive and two HDDs each

  C. One Disk Group with one Flash Drive and four HDDs

  D. Two Disk Groups with two Flash Drives and four HDDs each

  Correct Answer: AB

  Explanation: On each ESXi host that contributes its local disks to a Virtual SAN cluster, disks are organized into disk groups. A disk group is a main unit of storage on a host. Each disk group includes one SSD and one or multiple HDDs (magnetic disks). Virtual SAN uses an aggregation of disk groups to back up a single datastore that is created when you enable Virtual SAN. In the disk group, the SSD primarily serves as a read cache write buffer, while the HDDs are used for permanent storage. Typically, a higher SSD to HDD ratio, both in size and quantity, improves performance. Depending on the mode you select when enabling Virtual SAN on a cluster, you can use different ways to organize disks into groups.

  Automatic Mode Virtual SAN claims all available and usable disks and organizes them into default groups with one SSD and one or multiple HDDs. If you add more disks to hosts or add new hosts to the Virtual SAN cluster, all applicable disks are claimed by Virtual SAN. Virtual SAN in automatic mode claims only local disks on the ESXi hosts in the cluster. You can add any remote nonshared disks manually. Manual Mode You must specify hosts and disks on the hosts to be used for the Virtual SAN datastore. You have two methods of organizing disks into disk groups, semi-automatic and manual. When you use the semi-automatic method, Virtual SAN organizes the disks that you specify into default disk groups. Another option is to manually create user-defined disk groups and select disks for each group. When you create a disk group manually, your main consideration should be the ratio of SSD to Raw HDD capacity. Although the ratios depend on use cases and workloads, the best practice is to use SSD capacity of at least 10 percent of the total consumed HDD capacity in each disk group, without counting the protection copies. For example, if the size of your Raw HDD capacity on the disk group is 4TB, the recommended SSD capacity is 400GB.

• Question 16:

  Refer to the Exhibit.

  

  What will be created upon completion of the steps in this wizard?

  A. 100GB VMFS5 datastore with free space available for expansion

  B. 100GB VMFS5 datastore with free space available for a second datastore

  C. 100GB VMFS3 datastore

  D. 200.01 GB VMFS5 datastore

  Correct Answer: A

  Explanation: The datastore size selected is 100GB. On competition of this step, 100 GB VMFS datastore will be created.

• Question 17:

  Refer to the Exhibit.

  

  A vSphere 6.x environment is configured with VMware Virtual Volumes (VVOLs). An administrator accesses the cluster Actions menu, as shown in the Exhibit.

  Which option is used to create a VVOL on an existing VVOL container?

  A. Storage

  B. Deploy OVF Template

  C. New vApp

  D. Settings

  Correct Answer: A

  Explanation: Virtual Volumes is an integration and management framework for external storage that provides finer control at the VM-level, streamlines storage operation and offers flexibility of choice.

  Virtual Volumes implements the core tenets of the VMware SDS vision to enable a fundamentally more efficient operational model for storage in virtualized environments, centering it around the VM rather than on the physical infrastructure. - See more at: http://www.vmware.com/in/products/vsphere/features/virtual-volumes#sthash.tx9IZaOq.dpuf

• Question 18:

  What is the compression algorithm used by vSphere Replication to compress data at the source?

  A. FastLZ

  B. Lz4

  C. Lzr

  D. Lzx

  Correct Answer: A

  Explanation: vSphere Replication 6.0 utilizes the FastLZ compression library. This provides a nice balance of speed, minimal CPU overhead, and compression efficiency. When using vSphere 6.0 and vSphere Replication 6.0 at both the source and target locations, updates are compressed at the source and stay compressed until they are written to storage at the target. In cases where there is a mixed configuration, packets may be decompressed at some point in the replication path. For example, if a vSphere 6.0 host is connecting to a vSphere Replication 5.8 virtual appliance, packets will not be compressed over the network. Another example: vSphere 6.0 replicating to a vSphere Replication 6.0 virtual appliance, which is writing to vSphere 5.5 host storage ?packets are compressed from the source to the vSphere Replication

  6.0 virtual appliance, but are decompressed in the appliance before being written to the vSphere 5.5 storage at the target. Performing this decompression in the vSphere Replication virtual appliance will cause higher vCPU utilization in the appliance. As you can imagine, the most benefit from compression will be realized when running vSphere 6.0 and vSphere Replication 6.0 at both the source and target locations.

  Reference: https://blogs.vmware.com/vsphere/2015/03/vr-60-compression.html

• Question 19:

  What is the maximum number of snapshot instances in vSphere Replication that can be configured to recover a virtual machine at a specific point in time?

  A. 16

  B. 24

  C. 48

  D. 72

  Correct Answer: B

  Explanation: When you configure replication of a virtual machine, you can enable multiple point in time (PIT) instances in the recovery settings in the Configure Replication wizard. vSphere Replication retains a number of snapshot instances of the virtual machine on the target site based on the retention policy that you specify.vSphere Replication supports maximum of 24 snapshot instances. After you recover a virtual machine, you can revert it to a specific snapshot.

  Reference: https://pubs.vmware.com/srm-55/index.jsp?topic=%2Fcom.vmware.srm.admin.doc%2FGUIDF3C8A2E9-183E-4DFF-A7D1-43CAEE584149.html

• Question 20:

  Which keystore would a vSphere Replication administrator use to manually add an additional Certificate Authority certificate?

  A. hms-truststore.jks

  B. hms-keystore.jks

  C. certificates.ks

  D. cacerts.ks

  Correct Answer: A

  vSphere Replication can verify remote server certificates either by verifying the validity of the certificate and the thumbprint or by verifying the thumbprint only. By default, vSphere Replication verifies the thumbprint only. If you select the Accept only SSL certificates signed by a trusted Certificate Authority option in the VAMI, this causes vSphere Replication to verify the validity of the certificate as well as the thumbprint. This means that the certificate authority that issued the certificates for vSphere Replication and vCenter Server must be trusted by vSphere Replication. By default, vSphere replication trusts all certificate authorities that the Java Virtual Machine trusts. You can import additional trusted CA certificates in /opt/ vmware/hms/security/hmstruststore.Jks on the vSphere Replication appliance. To import these certificates, perform these steps:

  1.

  Locate the root certificate authority certificate that was used when generating the vCenter server

  certificates (usually Root64.cer). If you use a Microsoft certificate authority, this can be re-generated by

  performing the mentioned in Creating certificate requests and certificates for vCenter Server 5.1

  components (2037432). Otherwise, you may be able to export the root certificate using the MMC on a

  Windows system.

  2.

  Copy the certificate to your replication appliance.

  For example, /home directory. A utility such as WinSCP can be used for this.

  3.

  Run this command to import the certificate into the HMS truststore:

  /usr/java/default/bin/keytool -import -trustcacerts -alias root -file /home/Root64.cer -keystore /opt/vmware/

  hms/security/hms-truststore.jks -storepass vmware

  4.

  Type yes at the prompt and press enter to complete the certificate import process:

  Trust this certificate? [no]: yes

  5. You see this text which confirms the import was successful: Certificate was added to keystore

  6. Use this command to verify the certificate is now present in the HMS truststore:

  /usr/java/default/bin/keytool -list -keystore /opt/vmware/hms/security/hms-truststore.jks -storepass vmware

  璿

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