AZ-305 Design business continuity solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create a Recovery Services vault, then define a backup policy, then assign the VM to the vault, then enable backup, then test the backup.

  Why this is correct

  This is the correct order because you must first create the vault to store backups, define the policy that specifies the schedule and retention, assign the VM to the vault to associate it, enable backup to start protecting the VM, and finally test to verify the backup works.

• ✗

  Create a Recovery Services vault, then assign the VM to the vault, then define a backup policy, then enable backup, then test the backup.

  Why it's wrong here

  Assigning a VM to a Recovery Services vault before defining a backup policy is invalid because the policy defines the backup schedule, retention range, and snapshot settings that must exist before a VM can be associated with the vault. Without a policy, the vault has no protection configuration to apply, so the assignment step cannot complete correctly. The policy must be created first to provide the necessary parameters for the VM's backup lifecycle.

• ✗

  Create a Recovery Services vault, then define a backup policy, then enable backup, then assign the VM to the vault, then test the backup.

  Why it's wrong here

  Enabling backup is not an independent operation; it is the action that ties a specific VM to a vault and a backup policy, so executing it before the VM has been assigned leaves the backup scope undefined. In the Azure portal, the enable-backup workflow is where you choose the VM, select the vault, and pick the policy, which requires the VM to already be registered in the vault. A policy may exist, but until the VM is associated and the enable command runs, no protection is active.

• ✗

  Create a Recovery Services vault, then define a backup policy, then assign the VM to the vault, then test the backup, then enable backup.

  Why it's wrong here

  Testing a backup before enabling it is logically impossible because no initial backup job has run, and therefore the vault contains no recovery points to validate or restore. The test step—whether checking a recovery point or performing a test restore—requires at least one successful backup execution after enablement. As a result, the enable-backup step must occur before any validation, and placing the test earlier breaks the dependency chain.

Go deeper

Related to this question