Configure and manage automation of tasks →easyMultiple ChoiceObjective-mapped

DP-300 Configure and manage automation of tasks Practice Question

Exhibit

Refer to the exhibit.
```json
{
  "properties": {
    "description": "Automated backup retention policy",
    "policyType": "Default",
    "retentionDays": 35,
    "backupIntervalInHours": 12,
    "geoRedundantBackup": "Enabled"
  }
}
```

You are reviewing an Azure SQL Database automated backup retention policy. The exhibit shows the current configuration. You need to ensure that the database can be restored to a point in time within the last 7 days at a granularity of 1 minute. Which of the following is a limitation of the current configuration?

⚠ Common exam trap

Candidates often confuse the purpose of backup intervals. The 12-hour interval shown is for full/differential backups, not transaction logs. Transaction log backups are taken frequently (every 5-10 minutes) and are responsible for point-in-time restore granularity.

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 retention period is too short to support point-in-time restore.

The current configuration shows a backup retention period of only 5 days, which is less than the required 7 days for point-in-time restore. With a retention period shorter than 7 days, you cannot restore to a point within the last 7 days. The backup interval of 12 hours is for full backups and does not affect point-in-time restore granularity, as transaction log backups are taken every 5-10 minutes, enabling 1-minute granularity.

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 interval of 12 hours does not allow 1-minute granularity for point-in-time restore.
Why it's wrong here
PITR granularity is limited by backup frequency.
✓
The retention period is too short to support point-in-time restore.
Why this is correct
Retention of 35 days exceeds 7 days needed.
✗
The policy must specify a minimum retention of 30 days for point-in-time restore.
Why it's wrong here
No such requirement.
✗
Geo-redundant backup must be disabled for point-in-time restore to work.
Why it's wrong here
Geo-redundancy does not affect PITR.

Go deeper

DP-300 Configure and manage automation of tasks Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question