AZ-305 Practice Question: Design identity, governance, and monitoring solutions

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 the vault, then ensure network connectivity, then install the provider and agent, then create and apply a replication policy, then enable replication.

  Why this is correct

  This is the correct order because you must first create a Recovery Services vault to store replication data, then ensure network connectivity between Hyper-V and Azure, install the necessary provider and agent, configure a replication policy to define replication settings, and finally enable replication for the VMs.

• ✗

  Install the provider and agent, then create the vault, then ensure network connectivity, then create and apply a replication policy, then enable replication.

  Why it's wrong here

  This order fails at the very first dependency: the Azure Site Recovery provider installation is not merely a file copy; it performs an interactive registration against a specified Recovery Services vault and retrieves vault credentials. Since no vault exists yet, there is no registration endpoint, so the provider setup will terminate and no Hyper-V site object will be created in Azure. A Recovery Services vault must be provisioned first, and outbound connectivity from the Hyper-V host to the ASR endpoints must be confirmed before the provider and agent can successfully register.

• ✗

  Create the vault, then ensure network connectivity, then create and apply a replication policy, then install the provider and agent, then enable replication.

  Why it's wrong here

  Creating the vault and confirming connectivity are correct up front, but creating/applying a replication policy before installing the provider is premature because a policy can only be applied to a registered Hyper-V site. The Hyper-V site does not exist in the vault until the provider/agent is installed and completes registration, which then triggers site discovery. Without a registered site, the 'apply' step has no target, so the correct order is to install the provider/agent first, let it register the site, and only then create and apply the replication policy.

• ✗

  Enable replication, then create the vault, then ensure network connectivity, then install the provider and agent, then create and apply a replication policy.

  Why it's wrong here

  This order starts with the final operational step, which cannot run in isolation. The Enable Replication wizard reads the target vault, the configured replication policy, and the discovered source host; none of these exist if the vault has not been created and the provider has not been installed. Additionally, enabling replication triggers initial replication traffic, so the Hyper-V host must already have the provider/agent running and be registered to a vault. Therefore, this step must come last, after the vault, connectivity, provider/agent, and policy are all in place.

Go deeper

Related to this question