Question No: 71 – (Topic 2)

A vSphere 5.x implementation contains two ESXi hosts, ESXi01and ESXi02. There is a virtual machine quot;VM21quot; connected to the Production port group on ESXi01.

ESXi01 has the following switch configuration.

vSwitch0, single uplink to 10.1.20.0/24 Production port group

VMkernel port for vMotion VMKernel port for management

vSwitch1, single uplink to 10.1.40.0/24 Engineering port group

VMKernel port for NFS storage

ESXi02 has the following switch configuration.

vSwitch0, single uplink to 10.1.20.0/24 Engineering port group

VMkernel port for vMotion VMKernel port for management

vSwitch1, single uplink to 10.1.40.0/24 Production port group

VMKernel port for NFS storage

Which two statements are true about this configuration? (Choose two.)

vMotion is not available between the two hosts

If VM21 is migrated to ESXi02 it will not be available on the network

The virtual machine can be vMotion migrated to the target host.

Broadcasts from the Production port group will not reach the Engineering port group.

Answer: B,D Explanation:

If VM21 is migrated to ESXi 02, then according to the information provided, it will not be available on the network. Likewise, broadcasts from production port group will not reach engineering port group.

Question No: 72 – (Topic 2)

Which network settings are only available with vSphere Distributed Switches?

Question No: 77 – (Topic 2)

Multiple vSphere virtual switches can be configured to use the same uplink.

vSphere virtual switches must be configured with at least one uplink.

Multiple vSphere virtual switches cannot be configured to use the same uplink.

Answer: A,D Explanation:

VMware Virtual Networking Concepts, page 6. Some virtual switches should not connect to a physical network and thus have no uplink port. If you attempt to assign an uplink port, (previously assigned to a switch), to a second switch, the uplink will be disconnected from the first switch before being connected to the second.

Question No: 78 – (Topic 2)

A virtual machine, VM21, will be migrated between two ESXi 5.x hosts, labeled ESXi01 and ESXi02. Each host has two vSphere Standard Switches (vSS), configured as follows:

vSwitch0 has a portgroup labeled Management and a portgroup labeled vMotion.

vSwitch0 on ESXi01 has a single uplink attached to the 10.1.20.0/24 network.

vSwitch0 on ESXi02 has a single uplink attached to the 10.1.20.0/24 network.

Each host has a vSwitch1 with a Production portgroup used by virtual machine traffic.

Each vSwitch1 has an uplink attached to the 10.1.40.0/24 network. What is true about migrating VM21 to the new host?

vMotion would be supported in this configuration.

Storage vMotion would not be supported in this configuration.

vMotion would not be supported in this configuration.

Storage vMotion would be supported if the storage device supports VAAI.

Answer: A Explanation:

As per the configuration shown in the question, vmotion will be supported without any problem.

Question No: 79 – (Topic 2)

Click the Exhibit button.

An administrator has been tasked with adding a newly installed uplink to vSwitch1. Based on the exhibit, what is a true statement about this environment?

The server does not have available vSwitches to be assigned to this uplink.

The available uplinks are not compatible with a standard vSwitch.

The host needs a driver installed for the newly installed uplink.

The current uplinks cannot be attached because they are in use by other port groups.

Answer: C

Explanation: as you can see that the Next button is greyed out. This means the host needs driver installed on the newly installed uplink. Once the driver in installed, the Next button will become active.

Question No: 80 – (Topic 2)

Which settings are required for virtual machine guest tagging for VLAN 100 in a vSphere

5.x environment?

Port Group configured for VLAN 100, physical switch configured as a VLAN trunk

Port Group configured for VLAN 4095, physical switch configured as a VLAN trunk

A VLAN ID, which restricts port group traffic to a logical Ethernet segment within the physical network, is optional. For a port group to reach port groups located on other VLANs, the VLAN ID must be set to 4095. If you use VLAN IDs, you must change the port group labels and VLAN IDs together so that the labels properly represent connectivity.

If you enter 0 or leave the option blank, the port group can see only untagged (non-VLAN) traffic. If you enter 4095, the port group can see traffic on any VLAN while leaving the VLAN tags intact.