On a hybrid AHV cluster with Prism Central, a database VM needs low latency while many file-share VMs need capacity. You must apply storage settings that balance performance and capacity. Which combination best matches the workload classes?
Select an answer to reveal the explanation.
Short Explanation
Think of SSD on a hybrid cluster as the VIP section: you don't hand out VIP passes to everybody. You give the database Flash Mode so it stays on SSD, and you compress the file shares where saving space matters most. Turning one feature on for everything wastes what it's good at.
Full Explanation
Matching each workload to the feature built for it is the point here. Flash Mode, available on hybrid clusters and enabled per VM or per vDisk, keeps that VM's data on the SSD tier instead of letting it be tiered down to HDD, which protects read latency for the database. Compression reduces the capacity consumed by data such as file shares, and on Nutanix it can be applied through container settings or a Prism Central storage policy associated with those VMs by category. Compression costs little CPU and is widely recommended, but applying it everywhere doesn't address the database's need for SSD residency. Enabling Flash Mode for every VM uses up the limited SSD share reserved for it and lets low-value file data push out the database blocks that need it. Deduplication helps when many blocks are identical, such as full-clone desktops, and disabling Flash Mode for the database removes the protection the latency-sensitive VM needs most. Exam caveat: Flash Mode applies only to hybrid clusters; Prism Central storage policies set encryption, compression, QoS throttling and replication factor, not caching. Operational check: compare database read latency and file-share capacity savings in Prism before and after the change.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.