A company is performing a P2V conversion of all developer machines to a VDI. Which of the following should the administrator configure to ensure disk throughput is not saturated by one machine or…

Question

Options

• AEach VM to use a virtual SCSI adapter
• BDisk I/O monitoring on the VMs
• CDCB on the FC fabric
• DDisk I/O throttling on the VMs

• A
  12% (5)
• B
  7% (3)
• C
  2% (1)
• D
  78% (32)

Explanation

Disk I/O throttling (D) allows an administrator to set maximum read/write limits per virtual machine, preventing any single VM from monopolizing the shared physical storage - a problem commonly called the 'noisy neighbor' effect. In a VDI environment where many VMs share the same underlying storage infrastructure, one VM running a heavy disk operation (e.g., a build process on a developer machine) could starve others. Throttling enforces fair usage policies at the VM level. Using a virtual SCSI adapter (A) can improve VM disk performance overall but does not cap or control how much I/O any one VM can consume. Disk I/O monitoring (B) is observational only - it identifies saturation after the fact but does not prevent it. DCB (Data Center Bridging) on an FC fabric (C) is a network-level quality-of-service mechanism for Fibre Channel over Ethernet, not a per-VM disk I/O control mechanism. Disk I/O throttling is the correct administrative control to enforce fair disk throughput across VMs.

No community discussion yet for this question.