VMware 2V0-621 Exam Questions & Answers

Correct Answer: A

The default Hardware Version of the vRealize Operations Manager virtual machine is 7, limiting the maximum vCPUs selection to 8. You can upgrade the Hardware Version of the Analytics machine to increase the vCPU limit. Theoretically, the performance of PVM should be similar or better than HVM. But, this trend tends to break when the vCPU count increases from 20 vCPUS. This problem is counter intuitive and is only observed in case of vCPUs being greater than 20 physical cores. We classify this problem as sleepy lock anomaly, which occurs due to the usage of paravirtual interface in the ticket spinlock implementation that has been introduced to solve the Lock Holder Preemption problem without the architectural support (i.e. Pause Loop Exiting). Take steps to analyze the scalability behavior of VMs with high core count (till 80 core). Our preliminary study suggests that besides cache contention bottleneck, the usage of ticket spinlock is another culprit for the degradation. We will take a step further and will try to analyze the scalability characteristics of these monster VMs by running other benchsuites from Mosbench. https://www.vmware.com/support/pubs/vrealize-automation-pubs.htm

Correct Answer: BCD

Securing System Traffic

Take appropriate security measures to prevent unauthorized access to the management and system traffic

in your vSphere environment. For example, isolate the vMotion traffic in a separate network that includes

only the ESXi hosts that participate in the migration. Isolate the management traffic in a network that only

network and security administrators are able to access. For more information, see vSphere Security and

vSphere Installation and Setup.

System Traffic Types

You should dedicate a separate VMkernel adapter for every traffic type. For distributed switches, dedicate

a separate distributed port group for each VMkernel adapter.

Management traffic

Carries the configuration and management communication for ESXi hosts, vCenter Server, and host-tohost High Availability traffic. By default, when you install the ESXi software, a vSphere Standard switch is

created on the host together with a VMkernel adapter for management traffic. To provide redundancy, you

can connect two or more physical NICs to a VMkernel adapter for management traffic.

vMotion traffic

Accommodates vMotion. A VMkernel adapter for vMotion is required both on the source and the target

hosts. The VMkernel adapters for vMotion should handle only the vMotion traffic. For better performance,

you can configure multiple NIC vMotion. To have multi NIC vMotion, you can dedicate two or more port

groups to the vMotion traffic, respectively every port group must have a vMotion VMkernel adapter

associated with it. Then you can connect one or more physical NICs to every port group. In this way,

multiple physical NICs are used for vMotion, which results in greater bandwidth.

Note

vMotion network traffic is not encrypted. You should provision secure private networks for use by vMotion

only.

Provisioning traffic

Handles the data that is transferred for virtual machine cold migration, cloning, and snapshot creation.

IP storage traffic and discovery

Handles the connection for storage types that use standard TCP/IP networks and depend on the VMkernel

networking. Such storage types are software iSCSI, depended hardware iSCSI, and NFS. If you have two

or more physical NICs for iSCSI, you can configure iSCSI multipathing.ESXi hosts support only NFS

version 3 over TCP/IP. To configure a software FCoE (Fibre Channel over Ethernet) adapter, you must

have a dedicated VMkernel adapter. Software FCoE passes configuration information though the Data

Center Bridging Exchange (DCBX) protocol by using the Cisco Discovery Protocol (CDP )VMkernel

module.

Fault Tolerance traffic

Handles the data that the primary fault tolerant virtual machine sends to the secondary fault tolerant virtual

machine over the VMkernel networking layer. A separate VMkernel adapter for Fault Tolerance logging is

required on every host that is part of a vSphere HA cluster.

vSphere Replication traffic

Handles the outgoing replication data that the source ESXi host transfers to the vSphere Replication

server. Dedicate a VMkernel adapter on the source site to isolate the outgoing replication traffic.

vSphere Replication NFC traffic

Handles the incoming replication data on the target replication site.

Virtual SAN traffic

Every host that participates in a Virtual SAN cluster must have a VMkernel adapter to handle the Virtual

SAN traffic.

Reference:

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

2FGUID-D4191320-209E-4CB5-A709-C8741E713348.html

Correct Answer: BCD

Procedure

1 Navigate to the vSphere Web Client login page.

2 If the Use Windows session authentication check box is not available,

click Download the Client Integration Plug-in at the bottom of the login page.

3 If the browser blocks the installation by issuing certificate errors or by running a pop-up blocker,

follow the Help instructions for your browser to resolve the problem.

4 Close other browsers if you are prompted to do so.

After installation, the plug-in is available for all browsers.

5 Exit and restart your browser.

After the restart, you can select the Use Windows session authentication check box.

Reference:

https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUIDC7BF3BD5-76E6-406F-8CF1-309D31F1DEBA.html