Design business continuity solutions →hardMultiple ChoiceObjective-mapped

AZ-305 Design business continuity solutions Practice Question

Exhibit

{
  "type": "Microsoft.Web/sites",
  "apiVersion": "2022-09-01",
  "name": "myapp",
  "location": "[resourceGroup().location]",
  "kind": "app",
  "properties": {
    "siteConfig": {
      "alwaysOn": true,
      "minTlsVersion": "1.2"
    },
    "backup": {
      "enabled": true,
      "storageAccountUrl": "https://mybackups.blob.core.windows.net/backups?sv=2020-08-04&ss=b&srt=sco&sp=rwdl&se=2025-12-31T23:59:59Z&st=2023-01-01T00:00:00Z&spr=https&sig=...",
      "schedule": {
        "frequencyInterval": 1,
        "frequencyUnit": "Day",
        "retentionPeriodInDays": 30
      }
    }
  }
}

Refer to the exhibit. This ARM template configures backup for an Azure App Service web app. The backup is scheduled daily. What is the primary limitation of this backup strategy in meeting a disaster recovery RPO of 4 hours?

⚠ Common exam trap

The trap here is that candidates may focus on the storage account being in the same region (a common disaster recovery concern) or the retention period, but the core issue is that the daily backup frequency cannot meet a 4-hour RPO.

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 backup frequency is 1 day, resulting in an RPO of up to 24 hours

The backup frequency is set to 1 day, meaning the most recent backup could be up to 24 hours old. To meet a Recovery Point Objective (RPO) of 4 hours, you need backups taken at least every 4 hours. Azure App Service backup does not support sub-daily scheduling natively; you would need to use Azure Backup or custom logic to achieve a 4-hour RPO.

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 backup storage account is in the same region as the web app
Why it's wrong here
The storage account region does not affect RPO; it only determines the physical location and redundancy of the backup blob, impacting durability and cross-region disaster recovery. Azure App Service actually requires the backup storage account to be in the same region as the app, so this is a valid, normal configuration. Because RPO is governed exclusively by how often recovery points are captured, placing the storage account in the same region does nothing to reduce the 24-hour window caused by the daily backup schedule.
✓
The backup frequency is 1 day, resulting in an RPO of up to 24 hours
Why this is correct
A daily backup schedule means that at any given time, the most recent recoverable point can be up to 24 hours old, so the effective RPO is 24 hours. To satisfy a 4-hour RPO, backups must be taken at least every 4 hours—for example, six scheduled backups per day—or supplemented by more frequent manual backups. Since the requirement states a maximum RPO of 4 hours, the daily frequency is the specific reason this ARM template configuration fails.
✗
The retention period of 30 days is too short
Why it's wrong here
Retention period determines how long backup copies are retained before deletion, which affects how far back in time you can restore, not the age of the newest recoverable point. A 30-day retention means you can restore to any daily backup from the past month, but the most recent daily backup is still at most 24 hours old. Thus, the retention setting does not alter the recovery point freshness and has no impact on the RPO calculation.
✗
The backup does not include the web app configuration
Why it's wrong here
The App Service backup feature includes the web app's content, configuration, app settings, and connection strings in the backup payload, so the statement itself is factually incorrect. Even if configuration were excluded, the absence of configuration data would affect restore completeness, not the time interval between backups. RPO measures the maximum acceptable data loss in terms of time between recovery points, so the content scope of a backup is irrelevant to the 24-hour RPO problem.

Go deeper

AZ-305 Design business continuity solutions Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question