Plan and configure a high availability and disaster recovery environment →mediumMultiple ChoiceObjective-mapped

DP-300 Practice Question: Plan and configure a high availability and disaster recovery environment

Exhibit

Refer to the exhibit.

```json
{
  "properties": {
    "replicationRole": "Secondary",
    "replicationState": "CATCH_UP",
    "replicationLag": "00:00:05"
  }
}
```

You query the sys.dm_geo_replication_link_status dynamic management view for an Azure SQL Database configured with active geo-replication. The exhibit shows the output. What does this indicate about the replication health?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The secondary is fully synchronized with minimal lag.

The replicationLag of 5 seconds is minimal and normal for active geo-replication, indicating the secondary is nearly synchronized. The replicationState 'CATCH_UP' confirms that the secondary is fully caught up with the primary. Options B, C, and D are incorrect: B is wrong because a secondary role is expected in geo-replication; C is wrong because 5 seconds lag is not a problem; D is wrong because the state is CATCH_UP, not SEEDING.

Answer analysis

Option-by-option breakdown

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

✓
The secondary is fully synchronized with minimal lag.
Why this is correct
Correct.
✗
The secondary role indicates a failover has occurred.
Why it's wrong here
Secondary role is normal for geo-replication.
✗
The secondary is 5 seconds behind, indicating a problem.
Why it's wrong here
5 seconds lag is normal.
✗
The replication is in the seeding phase.
Why it's wrong here
State is CATCH_UP, not SEEDING.

Go deeper

DP-300 Practice Question: Plan and configure a high availability and disaster recovery environment

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question