Which changes to Storage Optimization should be used on the Exchange container to enhance I/O performance?

An administrator deploys Exchange on a Nutanix cluster.

The administrator creates two containers with RF2 configuration:

• One container for Exchange

• One container for the other VMs

The Exchange VM is experiencing I/O performance issues.

Which changes to Storage Optimization should be used on the Exchange container to enhance I/O performance?
A . No data reduction
B . Post process Deduplication only
C . Inline compression and EC-X
D . Inline compression and Deduplication

View Answer

Answer: A

Explanation:

For the Exchange VM experiencing I/O performance issues, the recommended storage optimization change is Option A, "No data reduction." Exchange, as an application, is highly sensitive to latency and typically does not benefit significantly from data reduction technologies like deduplication or compression, which can introduce additional processing overhead and potentially worsen performance issues.

By configuring the container for Exchange with no data reduction, the system maximizes I/O performance by eliminating any additional processing that could delay data access. This setup ensures that Exchange has the fastest possible access to its data, which is crucial for its performance.

Reference: This recommendation aligns with best practices for Exchange storage on Nutanix, as detailed in the

Nutanix best practices guide for deploying Microsoft Exchange, where it advises against using data reduction features for databases requiring high I/O throughput.