This workload stores MP4 video files, which are typically large, sequential, and already compressed. For data with those characteristics, additional compression work often provides little benefit and can create unnecessary processing overhead. The best optimization is to disable compression for that workload through a storage policy so cluster resources are not wasted trying to compress data that is unlikely to shrink meaningfully. ( Nutanix Portal ) The other choices are weaker for this scenario. Capacity deduplication is generally most beneficial for repeated blocks or common-image patterns, not unique media streams. Erasure Coding is a capacity- efficiency feature, but on a small 3-node cluster and for a write-heavy recording pattern, it is not the primary performance optimization answer. Moving the data to Files changes the access method, but it does not address the specific inefficiency already identified in the storage settings. Nutanix exams often test whether the administrator can match the data service to the workload profile. Since MP4 content is already compressed, removing unnecessary compression overhead is the most targeted and sensible answer, making D correct. ( Nutanix Portal )

To receive an alert earlier, the administrator must lower the threshold at which the alert's warning state is triggered. Nutanix alerting works by comparing utilization against configured warning and critical thresholds.
If the threshold is lowered, the system reaches it sooner, which gives the administrator more lead time before the environment becomes capacity-constrained. Among the given options, the one that directly performs that function is decreasing the Storage Container Space Usage Exceeded alert Warning threshold, which is option C.
The other choices are weaker or misaligned. There is no meaningful "increase frequency" adjustment that changes when capacity is considered low; it would only change how often checks occur, not the trigger point.
Changing the critical threshold does not provide earlier warning notice, which is what the question asks for.
The wording also points more naturally to a threshold-based action rather than enabling a different alert family. In Nutanix monitoring, earlier warnings come from making the warning trigger more conservative.
Therefore C is the best answer because it causes the alert to fire at a lower usage percentage and provides earlier operational notice.

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.

When Prism Central is scaled out for resiliency, the design goal is not only to have multiple Prism Central VMs, but also to ensure they are not placed together in a way that creates a common point of failure. Nutanix documentation around anti-affinity policies explains that VM-VM anti-affinity is used to keep selected VMs from running on the same host. In a scaled-out Prism Central deployment, this placement separation is the logical next step to strengthen resiliency, because it prevents the Prism Central instances from collapsing onto the same physical host and failing together during a node outage. ( Nutanix ) The other options are either unrelated or not the primary required follow-up. Witness Service is associated with Metro Availability and DR designs, not with the baseline requirement of distributing Prism Central VMs after scale-out. Protection Domain protection may be useful in some cases, but it does not solve co-location risk. HA reservations on the hosting Prism Element cluster address restart capacity, not placement diversity.
The most direct resiliency improvement after scaling out Prism Central is to enforce separation between the Prism Central VMs. That is why D is the best answer. ( Nutanix )

Nutanix Foundation documentation explains that Standalone Foundation can be used for imaging or re- imaging nodes, including bare-metal imaging scenarios where the target nodes do not already have a host operating system. This matches the scenario exactly: the new node has no operating system, and the administrator needs a deployment tool to image it into the cluster. Since IPMI is not configured, a centrally managed remote bare-metal workflow like Foundation Central is less appropriate than directly using Standalone Foundation for node imaging. ( Nutanix ) The other options fit different situations. Phoenix ISO is generally associated with recovery and low-level reinstallation paths rather than the normal first-choice imaging workflow for adding a new node in an expansion scenario. Discovery OS is not the intended answer for cluster imaging itself. Foundation Central is designed to orchestrate many deployments at scale, but the question is about imaging a specific new bare- metal node without existing out-of-band configuration. Nutanix documentation describes Standalone Foundation as a supported answer for exactly this type of node imaging task, so D is correct. ( Nutanix )