2V0-621 Online Practice Questions and Answers

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

Correct Answer: ACE

"%RDY"

The percentage of time the world was ready to run.

A world in a run queue is waiting for CPU scheduler to let it run on a PCPU. %RDY accounts the

percentage of this time. So, it is always smaller than 100%.

+Q: How do I know CPU resource is under contention?+

+A: %RDY is a main indicator. But, it is not sufficient by itself.+

+If a "CPU Limit" is set to a VM's resource settings, the VM will be deliberately held from scheduled to a

PCPU when it uses up its allocated CPU resource. This may happen even when there is plenty of free

CPU cycles. This time deliberately held by scheduler is shown by "%MLMTD", which will be describe next.

Note that %RDY includes %MLMTD. For, for CPU contention, we will use "%RDY - %MLMTD". So, if "%

RDY - %MLMTD" is high, e.g., larger than 20%, you may experience CPU contention.+

+What is the recommended threshold? Well, it depends. As a try, we could start with 20%. If your

application speed in the VM is OK, you may tolerate higher threshold. Otherwise, lower.+

+Q: How do we break down 100% for the world state times?+

+A: A world can be in different states, either scheduled to run, ready to run but not scheduled, or not ready

to run (waiting for some events).+ 100% = %RUN + %READY + %CSTP + %WAIT.

+Check the description of %CSTP and %WAIT below.+

+Q: What does it mean if %RDY of a VM is high?+

+A: It means the VM is possibly under resource contention. Check "%MLMTD" as well. If "%MLMTD" is

high, you may raise the "CPU limit" setting for the VM. If "%RDY - %MLMTD" is high, the VM is under CPU

contention.+

"%MLMTD"

The percentage of time the world was ready to run but deliberately wasn't scheduled because that would

violate the "CPU limit" settings.

Note that %MLMTD is included in %RDY.

+Q: What does it mean if %MLMTD of a VM is high?+

+A: The VM cannot run because of the "CPU limit" setting. If you want to improve the performance of this

VM, you may increase its limit. However, keep in mind that it may reduce the performance of others.+

"%CSTP"

The percentage of time the world spent in ready, co-deschedule state. This co-deschedule state is only

meaningful for SMP VMs. Roughly speaking, ESX CPU scheduler deliberately puts a VCPU in this state, if

this VCPU advances much farther than other VCPUs.

+Q: What does it mean if %CSTP is high?+

+A: It usually means the VM workload does not use VCPUs in a balanced fashion. The VCPU with high %

CSTP is used much more often than the others. Do you really need all those VCPUs? Do you pin the guest

application to the VCPUs?+ Reference:

https://communities.vmware.com/docs/DOC-9279

Correct Answer: C

Give the VMKernel port a label (e.g. iSCSI - if it will purley be used for iSCSI).

Enter the VLAN ID if the pNICs connected to the vSwitch are trunk ports and you have a specific VLAN for

this traffic (e.g. a dedicated storage VLAN).

Now if the port will only be used for storage services (iSCSI and NFS).

If the port will be used for all VMkernel services (iSCSI, NFS, vMotion and FT), tick the additional boxes to

allow this port to be used also for those services, Assigned the FT (IP Address)

Clustering is configured to give you, the administrator of an environment, a form of fault tolerance, and

VMware has taken this concept to a whole other level. Although VMware does not call FT clustering, it

functions the same in that FT will failover the primary virtual machine to a secondary virtual machine.

VMware Fault Tolerance (FT) is based on vLockstep technology and provides zero downtime, zero data

loss, and continuous availability for your applications.

Next,

?Always assign a reasonably high relative share for the Fault Tolerance

resource pool because FT is a very latency-sensitive traffic type.

Correct Answer: BD

B-) NOTE If you use the Specify Failover Hosts admission control policy and designate multiple failover hosts, DRS does not attempt to enforce VM-VM affinity rules for virtual machines that are running on failover hosts. D-) vSphere HA and DRS Affinity Rules If you create a DRS affinity rule for your cluster, you can specify how vSphere HA applies that rule during a virtual machine failover. The two types of rules for which you can specify vSphere HA failover behavior are the following: n VM anti-affinity rules force specified virtual machines to remain apart during failover actions. n VM-Host affinity rules place specified virtual machines on a particular host or a member of a defined group of hosts during failover actions. When you edit a DRS affinity rule, select the checkbox or checkboxes that enforce the desired failover behavior for vSphere HA. n HA must respect VM anti-affinity rules during failover -- if VMs with this rule would be placed together, the failover is aborted. https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60availability-guide.pdf

Correct Answer: BC

Three of the pre-established roles are permanent, meaning that the privileges associated with that role cannot be modified. These permanent roles are available to a stand-alone ESX or ESXi server, or to vCenter Server. The remaining eight are sample roles which can be modified as needed. These eight roles are exclusive to vCenter Server. Below are the pre-established roles:

1.

No Access: A permanent role that is assigned to new users and groups. Prevents a user or group from viewing or making changes to an object

2.

Read-Only: A permanent role that allows users to check the state of an object or view its details, but not make changes to it

3.

Administrator: A permanent role that enables a user complete access to all of the objects on the server. The root user is assigned this role by default, as are all of the users who are part of the local Windows Administrators group associated with vCenter Server. At least one user must have administrative permissions in VMware.

4.

Virtual Machine Administrator: A sample role that allows a user complete and total control of a virtual machine or a host, up to and including removing that VM or host

5.

Virtual Machine Power User: A sample role that grants a user access rights only to virtual machines; can alter the virtual hardware or create snapshots of the VM

6.

Virtual Machine User: Grants user access rights exclusively to VMs. The user can power on, power off, and reset the virtual machine, as well as run media from the virtual discs.

7.

Resource Pool Administrator: Allows the user to create resource pools (RAM and CPU reserved for use) and assign these pools to virtual machines

8.

Datacenter Administrator: Permits a user to add new datacenter objects

9.

VMware Consolidated Backup User: Required to allow VMware Consolidated Backup to run

10.Datastore Consumer: Allows the user to consume space on a datastore 11.Network Consumer: Allows the user to assign a network to a virtual machine or a host

Reference: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.security.doc/GUID-18071E9AEED1-4968-8D51-E0B4F526FDA3.html

Correct Answer: AB

Reference: http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.dcadmin.doc_41/ vsp_dc_admin_guide/managing_users_groups_roles_and_permissions/ r_default_roles_for_esx_esxi_and_vcenter_server.html

Correct Answer: B

Reference:

https://www.vmware.com/pdf/vsphere6/r60/vsphere-60-configuration-maximums.pdf

Correct Answer: A

Domain alias

(Optional) The domain's NetBIOS name.

Reference:

https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUIDB23B1360-8838-4FF2-B074-71643C4CB040.html

Correct Answer: AB

A-) Storage I/O Control was introduced in vSphere 4.1, taking storage resource controls built into vSphere to a much broader level. In vSphere 5, Storage I/O Control has been enhanced with support for NFS data stores and clusterwide I/O shares. Check vmware.com esxi versions enhancements, for further troubleshooting https://kb.vmware.com/kb/1022091 B-) If hosts are not licensed at the appropriate level, the option to enable Storage I/O control is grayed out. Check: https://kb.vmware.com/kb/2021530

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