Question 880
Three protected Azure VMs form a billing service: `sql-db` must finish startup before `api-core`, and a web frontend must start last. All three already replicate to the same Azure Site Recovery target region. During a failover the operator also needs an approved manual check after database startup and before the API tier starts. Which configuration supports this ordered dependency workflow?
Explanation
Correct Answer
Site Recovery recovery plans group protected VMs in an explicit startup order and can insert manual instructions or supported automation runbooks. Put SQL first, validate database readiness, then start API and web groups and rehearse the steps in a test failover.
Incorrect Answers
A single recovery-plan group starts its included machines together rather than enforcing the required sequential tier readiness. The database's success cannot be verified before the API runs if everything is in one group with no intervening action.
Backup retention controls how long backup recovery points are kept. It does not specify failover sequence, insert human actions, or coordinate startup of already Site Recovery-replicated VMs.
Correct DNS helps users reach recovered services but does not order VM starts or enforce a database-readiness gate. Recovery-plan group configuration is the mechanism that expresses this dependency in the failover workflow.