Plan and configure a high availability and disaster recovery environment →mediumMultiple Choice

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

Exhibit

{
  "type": "Microsoft.Sql/servers/databases",
  "apiVersion": "2023-08-01-preview",
  "properties": {
    "requestedBackupStorageRedundancy": "Geo",
    "createMode": "PointInTimeRestore",
    "sourceDatabaseId": "/subscriptions/.../resourceGroups/rg1/providers/Microsoft.Sql/servers/server1/databases/db1",
    "restorePointInTime": "2025-02-15T03:00:00Z"
  }
}

Refer to the exhibit. You are reviewing an ARM template for deploying an Azure SQL Database. The template specifies a point-in-time restore from a source database. The source database is configured with geo-redundant backup storage. You need to ensure that the restored database can be used for disaster recovery in a different region. What is missing from the template to achieve this?

⚠ Common exam trap

DP-300 often tests the distinction between PointInTimeRestore (same region) and GeoRestore (cross-region), tricking candidates into thinking that adding a location property or changing backup redundancy alone enables cross-region recovery.

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

✓

Set 'createMode' to 'GeoRestore' and specify a target server in the desired region.

To restore a geo-redundant backup to a different region, the ARM template must use createMode 'GeoRestore' and point to a target logical server in the desired region. A standard PointInTimeRestore restores to the same region and server, so it cannot satisfy the cross-region DR requirement. GeoRestore is the specific createMode that instructs Azure SQL to pull the geo-replicated backup and materialize the database on the specified target server in the alternate region.

Answer analysis

Option-by-option breakdown

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

✗
Add a 'location' property to the database resource.
Why it's wrong here
The location property sets where the restored database is created, but a cross-region restore additionally requires the geo-restore source parameters; location alone leaves the restore pointing at the original region. It is tempting because location is genuinely needed for any regional deployment.
✗
Set 'zoneRedundant' to true.
Why it's wrong here
Zone redundancy is for high availability, not for geo-restore.
✗
Change 'requestedBackupStorageRedundancy' to 'GeoZone'.
Why it's wrong here
GeoZone is not a valid requestedBackupStorageRedundancy value; the property configures backup replication for the target database, not the cross-region restore source. It is tempting because it names geo-redundancy, which is the correct setting when configuring a database's own backups for regional durability.
✓
Set 'createMode' to 'GeoRestore' and specify a target server in the desired region.
Why this is correct
GeoRestore is the only createMode that restores a geo-redundant backup into a different region, so the template must set createMode to GeoRestore and name a target server in the desired region. This satisfies the cross-region disaster recovery requirement.

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