A Nutanix admin protects a multi-VM web/database workload on AHV. The external backup tool must create application-consistent backups, and related VMs must be captured together. What should be configured?
Select an answer to reveal the explanation.
Short Explanation
Think of backing up a busy database like taking a group photo: if someone blinks, you don't get a usable picture. You need quiescing to pause writes and a consistency group so all VMs are captured together. Snapshots alone just give you a blurry crash-consistent mess.
Full Explanation
Application-consistent backups require the backup workflow to pause or quiesce application I/O and group related VMs so their snapshots represent a single transactional point. In a Nutanix multicloud estate, the backup integration should coordinate quiescing of supported workloads and a consistency group for multi-VM applications, producing a recoverable state for the entire service rather than a collection of independent crash-consistent snapshots. Retention settings only decide how long snapshots are kept; they do not make a snapshot application-consistent. NearSync replication reduces recovery point objective by frequently replicating data, but it is a data-protection transport, not a mechanism for pausing application writes during backup. Redundancy features such as RF2 and erasure coding protect stored data against disk or node failures, yet they operate at storage durability level and do not coordinate VMs or quiesce databases. Exam caveat: on the exam, application consistency is about coordinated write quiescing and group membership, not snapshot frequency. Operational check: confirm the backup tool reports application-consistent status and that all VMs in the workload share the same consistency group before relying on a restore.