AZ-104 Manage Azure Identities and Governance 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.

• ✓

  Step 1: Create a Recovery Services vault, Step 2: Configure source and target settings, Step 3: Install the Mobility service agent on on-premises machines, Step 4: Enable replication, Step 5: Test failover

  Why this is correct

  The Recovery Services vault must exist first because it stores replication configuration and credentials needed by the Mobility service. Configuring source and target settings defines the replication topology and identifies the vault registration endpoint. Installing the Mobility service agent on each on-premises machine requires the vault registration to occur; after registration, replication can be enabled. Only after replication is healthy can a test failover validate the recovery plan without impacting production.

• ✗

  Step 1: Install the Mobility service agent on on-premises machines, Step 2: Create a Recovery Services vault, Step 3: Configure source and target settings, Step 4: Enable replication, Step 5: Test failover

  Why it's wrong here

  Installing the Mobility service agent before creating a Recovery Services vault is invalid because the agent must be registered to a vault during installation; without the vault, there are no credentials or configuration server details to connect to. After installation, you cannot retroactively register the agent to a vault without reinstalling or reconfiguring it. Thus vault creation and source/target configuration must happen first to provide the registration endpoint and replication infrastructure.

• ✗

  Step 1: Create a Recovery Services vault, Step 2: Configure source and target settings, Step 3: Enable replication, Step 4: Install the Mobility service agent on on-premises machines, Step 5: Test failover

  Why it's wrong here

  You cannot enable replication before the Mobility service agent is installed on each on-premises machine because Azure Site Recovery relies on that agent to communicate with the configuration server and to perform initial replication of the virtual disks. Without the agent, the machine is not discoverable, and no replication health is reported. The agent installation is a prerequisite step that must be completed after source/target settings but before enabling the replication policy.

• ✗

  Step 1: Create a Recovery Services vault, Step 2: Configure source and target settings, Step 3: Install the Mobility service agent on on-premises machines, Step 4: Test failover, Step 5: Enable replication

  Why it's wrong here

  Testing failover before enabling replication is logically impossible because a test failover requires an existing replication relationship with a synchronized recovery point. Since replication has not been enabled, the source machine has never been copied to the target, so there is nothing to fail over to. Enabling replication must be the fourth step, and test failover the final validation step only after initial replication is healthy.

Go deeper

Related to this question