Exam NCP-MCI-7.5 Topic 1 Question 5 Discussion
Actual exam question for Nutanix's NCP-MCI-7.5 exam
Question #: 5
Topic #: 1
Question #: 5
Topic #: 1
An administrator manages a shared AHV environment where Dev workloads must not exceed 2,000 IOPS per VM during business hours to prevent noisy-neighbor impact on Prod.
The administrator already uses categories to group VMs (for example, category Env=Dev) and wants a scalable approach that applies consistent throttling to all current and future Dev VMs without configuring each VM individually.
Which approach best meets the requirement?
The administrator already uses categories to group VMs (for example, category Env=Dev) and wants a scalable approach that applies consistent throttling to all current and future Dev VMs without configuring each VM individually.
Which approach best meets the requirement?
Suggested Answer: B Vote an answer
Nutanix documents Storage QoS as the correct mechanism to throttle VM I/O and prevent noisy-neighbor behavior. Nutanix also documents that storage policies in Prism Central apply to Categories, and that QoS settings such as throttled IOPS can be defined in the storage policy itself. That means the administrator can create one policy, set the IOPS cap, and apply it to the category assigned to Dev VMs. Current and future VMs with that category then inherit the same behavior without one-by-one configuration. That is exactly the scalable model described in option B.
The other options do not meet the requirement as cleanly. Replication factor affects resilience, not IOPS governance. Cloning one VM's QoS is not a robust policy framework for future operations, especially when category-based automation already exists. Compression changes storage efficiency and sometimes performance characteristics, but it does not function as an enforceable per-VM IOPS cap. Because Nutanix explicitly ties QoS throttling to storage policies and category-based assignment, B is the documented and most maintainable answer.
The other options do not meet the requirement as cleanly. Replication factor affects resilience, not IOPS governance. Cloning one VM's QoS is not a robust policy framework for future operations, especially when category-based automation already exists. Compression changes storage efficiency and sometimes performance characteristics, but it does not function as an enforceable per-VM IOPS cap. Because Nutanix explicitly ties QoS throttling to storage policies and category-based assignment, B is the documented and most maintainable answer.
by Ira at Jul 17, 2026, 04:59 AM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).