In a hybrid Nutanix cluster, an application experiences sporadic latency spikes. Analysis shows that a small subset of frequently accessed blocks resides on HDDs while less frequently accessed data occupies SSDs. You need to ensure that hot data automatically migrates to the SSD tier without manual intervention or application changes. Which AOS storage feature provides this behavior?
Select an answer to reveal the explanation.
Short Explanation
Think of your storage like a library: bestsellers stay up front, archives go in the back. AOS Curator moves hot blocks to SSD and cold blocks to HDD automatically, so you don't have to touch the VM. The trap is confusing this with QoS or EC-X, which control limits or capacity efficiency, not placement.
Full Explanation
Nutanix AOS uses a distributed storage pool where data blocks can be placed on different media types. In hybrid clusters, Curator evaluates access patterns and promotes frequently accessed blocks to SSD while demoting infrequently accessed blocks to HDD. This keeps hot workload data on faster media without requiring the administrator to move disks or change the VM. Requiring manual placement of a virtual disk on an SSD-only container is wrong because it bypasses distributed optimization and prevents automatic promotion or demotion as access patterns change. Erasure coding is wrong because it is a capacity efficiency technique that stores data and parity across nodes; it reduces used capacity rather than deciding whether blocks belong on SSD or HDD. Quality of service limits are wrong because they cap IOPS or throughput to control noisy-neighbor impact, but they do not relocate data between storage tiers. Exam caveat: tiering is about placement of hot and cold blocks, not compression, deduplication, or performance limits. Operational check: confirm the storage pool includes both SSD and HDD domains and review Prism storage statistics to verify hot data is landing on the faster tier.