350-401 Question #1311: Real Exam Question with Answer & Explanation

Question

What is a concern when implementing virtual switching in a hypervisor?

Options

• Avirtual CPU data bus bandwidth limitations
• Bincorrect duplex, speed, and negotiation configuration for virtual interfaces
• Cbroadcast domain isolation meeting corporate security policies
• Dpacket forwarding across multiple virtual collision domains

Explanation

A primary concern when implementing virtual switching in a hypervisor is the potential for virtual CPU and data bus bandwidth limitations, as all network traffic must traverse the hypervisor's resources.

Common mistakes.

• B. Virtual interfaces within a hypervisor do not have configurable duplex, speed, or negotiation settings in the same way physical network interfaces do; these are handled abstractly by the hypervisor's networking stack.
• C. Virtual switches inherently support broadcast domain isolation through features like VLANs, and while misconfiguration can be an issue, the capability itself is a strength, not a fundamental implementation concern.
• D. Packet forwarding across multiple virtual collision domains (which are standard for switched virtual networks) is a function of the virtual switch, and while performance is a consideration, the concern is the underlying resource constraints (like CPU) affecting that forwarding, not the existence of multiple collision domains itself.

Concept tested. Hypervisor virtual networking performance

Reference. https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/best-practices-for-running-hyper-v-on-windows-server

No community discussion yet for this question.