nerdexam
Nutanix

NCP-MCI-6.10 · Question #95

An administrator is tasked with ensuring the resiliency of Tier-1 workloads. As such, the administrator creates a Protection Policy with a crash-consistent snapshot period that meets RPO while…

The correct answer is B. Enable Reverse Retention within the Protection Policy Schedule. Reverse Retention is a Nutanix Protection Policy feature that addresses exactly this scenario. Normally, if a DR event occurs and replication temporarily stops, the local site continues taking snapshots but the retention count may drop below the target as older recovery points…

Secure and Protect Data

Question

An administrator is tasked with ensuring the resiliency of Tier-1 workloads. As such, the administrator creates a Protection Policy with a crash-consistent snapshot period that meets RPO while maintaining 10 recovery points locally and 5 at DR location. Since it is difficult to quantify how long a DR event will last, management wants the Tier-1 workloads to always have 10 recovery points locally. How can this be achieved logically and most efficiently?

Options

  • AChange retentions within the Protection Policy to be 10 at both locations and Save Schedule.
  • BEnable Reverse Retention within the Protection Policy Schedule.
  • CUtilize a script that executes an API to take the requisite number of recovery points post- DR.
  • DPost DR, recreate the Protection Policy with new/updated values.

How the community answered

(25 responses)
  • A
    8% (2)
  • B
    72% (18)
  • C
    4% (1)
  • D
    16% (4)

Explanation

Reverse Retention is a Nutanix Protection Policy feature that addresses exactly this scenario. Normally, if a DR event occurs and replication temporarily stops, the local site continues taking snapshots but the retention count may drop below the target as older recovery points age out. When Reverse Retention is enabled, the local site automatically compensates by retaining additional recovery points to maintain the configured minimum count (10 in this case) regardless of how long the DR event lasts. This is more efficient than Options A (changing both locations to 10 changes DR behavior), C (scripting adds unnecessary complexity and risk), or D (recreating the policy post-DR is reactive and manual).

Topics

#Protection Policy#Disaster Recovery#Snapshot Retention#Reverse Retention

Community Discussion

No community discussion yet for this question.

Full NCP-MCI-6.10 Practice