An administrator is tasked with creating a new pool of desktops with hardware-accelerated graphics with vMotion support. Which graphic acceleration types can the administrator choose to meet the…

Question

Options

• AVirtual Shared 3D rendering
• BVirtual Shared Direct access 3D
• CVirtual Dedicated Graphics Acceleration
• DVirtual Shared Pass-through Graphics Acceleration

• A
  3% (1)
• B
  9% (3)
• C
  3% (1)
• D
  85% (29)

Explanation

Virtual Shared Pass-through Graphics Acceleration (vSGA) supports hardware-accelerated graphics while preserving vMotion compatibility because the GPU is shared across multiple VMs rather than exclusively assigned to one - the VM is not pinned to a specific host, so live migration remains possible.

Option C (Virtual Dedicated Graphics Acceleration / vDGA) is the most tempting wrong answer: it does use real GPU hardware, but dedicates an entire physical GPU to a single VM via PCIe passthrough, which pins the VM to that host and breaks vMotion entirely.

Option A (Virtual Shared 3D rendering) uses software-based rendering, not hardware GPU acceleration, so it fails the "hardware-accelerated" requirement even though vMotion works fine.

Option B (Virtual Shared Direct access 3D) is a distractor - "direct access" implies a passthrough-style binding that would eliminate vMotion support, similar to vDGA.

Memory tip: The word "Dedicated" is your vMotion killer - whenever you see dedicated/direct/passthrough without "shared," the VM is glued to one host and vMotion is off the table. If it's Shared, the VM floats freely.

No community discussion yet for this question.