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

{
  "properties": {
    "partnerRegions": [
      {
        "location": "westus",
        "replicationRole": "Secondary"
      }
    ],
    "instanceFailoverGroupReadWriteEndpoint": {
      "failoverPolicy": "Automatic",
      "failoverGracePeriodMinutes": 60
    },
    "secondaryType": "Geo",
    "zoneRedundant": false
  },
  "type": "Microsoft.Sql/locations/instanceFailoverGroups"
}

Refer to the exhibit. You have an Azure SQL Managed Instance configured with the failover group properties shown. The primary region experiences an outage. After 30 minutes, the failover group has not failed over. You need to force failover immediately. What should you do?

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

✓

Use the Switch-AzSqlDatabaseFailoverGroup cmdlet with -AllowDataLoss.

When the failover group has an automatic failover policy and the primary region experiences an outage, the automatic failover will only occur after the grace period (typically 1 hour) expires. Since only 30 minutes have passed, the failover has not yet triggered automatically. To force an immediate failover, you can use the Switch-AzSqlDatabaseFailoverGroup cmdlet with the -AllowDataLoss parameter, which initiates a forced failover that may result in data loss. Option A is incorrect because changing the failover policy to Manual does not force a failover; it only changes the policy for future failovers. Option B is incorrect because setting secondaryType to Standby is not relevant to initiating a failover. Option D is incorrect because waiting for the grace period to expire would eventually result in automatic failover, but the requirement is to force failover immediately.

Answer analysis

Option-by-option breakdown

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

✗
Change the failover policy to Manual and then fail over.
Why it's wrong here
Changing policy does not initiate failover; you still need to invoke failover.
✗
Set the secondaryType to Standby.
Why it's wrong here
This does not initiate failover.
✓
Use the Switch-AzSqlDatabaseFailoverGroup cmdlet with -AllowDataLoss.
Why this is correct
Even though automatic failover is waiting for the grace period, you can force failover with data loss.
✗
Wait for the grace period to expire.
Why it's wrong here
The requirement is to fail over immediately.

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