A Windows test server ran a stress test program that generated a large amount of throughput. This test resulted in performance slowdowns on production hosts sharing VMFS datastore. What Dell Unity…

Question

Options

• AFile System Quotas
• BHost I/O Limits
• CFAST Cache
• DBandwidth Schedules

• A
  5% (1)
• B
  71% (15)
• C
  14% (3)
• D
  10% (2)

Explanation

Host I/O Limits (B) is correct because this Dell Unity XT feature lets storage administrators cap the IOPS and/or bandwidth that a specific host or LUN can consume, directly preventing a noisy-neighbor situation where one VM's stress test starves other hosts sharing the same VMFS datastore.

Why the distractors are wrong:

• A (File System Quotas) controls storage capacity consumption (disk space), not I/O throughput - it won't throttle a runaway stress test.
• C (FAST Cache) is a read/write caching tier using SSDs to accelerate performance, not restrict it; it actually helps busy workloads go faster, not slower.
• D (Bandwidth Schedules) don't exist as a named Dell Unity XT feature in this context - this is a distractor; tiering schedules (FAST VP) move data between tiers on a schedule but don't cap per-host I/O.

Memory tip: Think of Host I/O Limits as a speed governor on a specific host - just like a car's governor prevents it from going too fast and hogging the road, Host I/O Limits cap one host's throughput so it can't monopolize shared storage resources.

No community discussion yet for this question.