A Nutanix administrator protects a set of AHV VMs in a protection domain. Compliance requires one monthly snapshot to be retained for 12 months, but snapshots are being deleted after seven days. Which action enforces the required governance?

Snapshot retention is a governance control applied to the protection domain's snapshot schedule. It tells the data protection service which local and remote snapshots must survive automatic cleanup, based on the retention intervals you configure. When a compliance requirement says one monthly point must persist for twelve months, the correct response is to configure the protection domain's snapshot retention policy so those monthly points are protected from premature deletion. Increasing replication frequency, including NearSync, changes how often recovery points are replicated but does not define how long snapshots are retained; it can even create more points while still allowing older required points to age out. Creating another protection domain and disabling snapshot scheduling avoids the problem rather than enforcing policy, and it removes the very snapshots needed for recovery. Metro availability provides synchronous protection for low RPO scenarios, not snapshot retention governance, so it does not guarantee that monthly recovery points remain available for a year. Exam caveat: on the exam, distinguish replication mode from retention policy; RPO drives frequency, while retention drives deletion. Operational check: list the protection domain's snapshot schedule and confirm a monthly retention interval is enabled with the required count before reporting compliance.