Virtual Networking
Free VMware Certified Professional - Data Center Virtualization (vSphere 8) practice — 6 questions on Virtual Networking, with explanations. No sign-up. Full 12-question mixed test →
A vSphere 8 cluster uses Network I/O Control version 3 on a distributed switch shared by vMotion, management, and virtual machine traffic. During peak load, vMotion migrations are timing out because VM traffic consumes all available bandwidth on the 10GbE uplinks. The administrator must guarantee that vMotion always receives at least 2 Gbps, even during congestion, without capping the maximum bandwidth any traffic type can burst to. Which NIOC configuration should be applied to the vMotion system traffic type?
NIOC v3 reservations guarantee a minimum amount of bandwidth to a traffic type that is enforced even under contention, and reserved bandwidth is subtracted from the pool available to other traffic types — this is the only mechanism that guarantees a floor rather than just a relative priority.
vCenter Server for a customer environment is unreachable due to a database corruption issue, but the operations team must urgently connect a temporary troubleshooting VM to an existing distributed port group directly from the ESXi host's local UI while vCenter is being rebuilt. Which port binding type must have been configured on that distributed port group in advance to allow this?
Ephemeral binding assigns ports on-demand and is the only binding type that allows a VM to be connected to a distributed port group directly through the ESXi host (via the host client or API) when vCenter Server is unavailable, since the port is created/removed dynamically without requiring vCenter to hold the assignment.
An administrator is migrating uplinks from a manually configured EtherChannel (static) NIC team using the 'Route based on IP hash' teaming policy to a proper LACP Link Aggregation Group (LAG) on a distributed switch, backed by physical switches configured for dynamic LACP. After creating the LAG and moving the physical NICs into it, which additional step is required on the port group's teaming and failover policy for LACP to function correctly?
When using a LAG, the port group's failover order must specify the LAG itself as the active uplink (with standalone uplinks moved to unused); vSphere automatically applies 'Route based on IP hash' load balancing internally for LAG traffic, so the teaming policy option is greyed out and does not need to be manually selected.
A security team requires that VMs on a tenant's secondary VLAN segment be able to communicate with each other directly (peer-to-peer) and also reach the default gateway on the primary VLAN, but must NOT be able to communicate with VMs on a different secondary VLAN segment within the same private VLAN structure. Which private VLAN (PVLAN) secondary type should be assigned to this port group?
A Community secondary PVLAN allows member ports to communicate with each other and with promiscuous ports (such as the gateway) on the primary VLAN, but not with ports in other secondary PVLANs (isolated or other community segments) — matching the stated requirement exactly.
After enabling jumbo frames (MTU 9000) end-to-end for a new IP storage VMkernel adapter, administrators intermittently see storage performance degrade and vMotion operations occasionally fail with fragmentation-related errors, but only for traffic traversing one specific physical uplink. Which built-in vSphere Distributed Switch feature should be enabled first to automatically identify the root cause without manually checking every switch port?
vDS Health Check specifically validates VLAN trunking configuration, MTU consistency between the vDS and the connected physical switch ports, and teaming/failover configuration mismatches across each uplink — directly surfacing per-uplink MTU mismatches, which matches the symptom of a single uplink causing fragmentation.
An administrator is configuring multi-NIC vMotion across two 10GbE physical uplinks (vmnic2 and vmnic3) to load-balance and accelerate a large vMotion migration. Two VMkernel adapters (vmk1 and vmk2) are created on the same distributed port group family for vMotion. Which configuration correctly enables true multi-NIC vMotion load balancing across both uplinks?
VMware's documented multi-NIC vMotion design requires two separate port groups, each overriding the teaming/failover order so that one physical uplink is Active and the other is explicitly Unused (not Standby); each VMkernel adapter is then bound to a different port group, so each vMotion VMkernel interface deterministically uses a distinct uplink, enabling true parallel throughput across both NICs.
Ready for the real thing?
The full course has two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed answer explanations.
Start my full course on Udemy →