A three-tier app on AHV uses a database, app server, and web server. During failover, the database must start before the app and web tiers. You need the recovery plan to start the VMs together in the correct order. What should you do?
Select an answer to reveal the explanation.
Short Explanation
Think of recovery plan stages like boarding groups at the gate: group one boards before group two moves. Put the database in the first stage and the app and web tiers in later stages, and the plan powers them on in that order. Consistency groups and categories decide what's protected together, not who boots first.
Full Explanation
A Nutanix Disaster Recovery recovery plan defines its power-on sequence as stages. Each stage holds VMs or categories; when the plan runs, Prism Central powers on everything in the first stage, waits for the configured delay, and then moves to the next. Putting the database VM in stage one and the app and web VMs in later stages makes the plan start the tiers in the required order every time, during both test and real failovers. A consistency group in a protection domain makes several VMs' snapshots crash-consistent with each other so they recover to the same point in time; it says nothing about the order in which they power on. Protection domain settings don't include a staggered power-on delay, and any delay set outside the recovery plan would not coordinate the tiers during failover. A category groups VMs for policy targeting and can be added to a stage, but simply sharing one category puts the VMs in the same stage and starts them together, which is the opposite of what's needed. Exam caveat: the recovery plan unit of order is the stage, with an optional delay between stages; there is no separate dependency-group object. Operational check: run a test failover and confirm in the recovery plan report that the database stage completed before the app and web stages started.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.