AZ-305 Design business continuity solutions Practice Question
Exhibit
{
"type": "Microsoft.RecoveryServices/vaults/replicationFabrics/replicationProtectionContainers/replicationProtectedItems",
"apiVersion": "2022-10-01",
"name": "myContainer/myProtectedItem",
"properties": {
"policyId": "myPolicy",
"protectedItemType": "Microsoft.Compute/virtualMachines",
"replicationHealth": "Normal",
"failoverHealth": "Normal",
"testFailoverState": "None",
"recoveryPlan": null,
"currentRecoveryPoint": {
"recoveryPointId": "latest",
"recoveryPointTime": "2025-12-01T10:30:00Z"
},
"providerSpecificDetails": {
"instanceType": "A2A",
"multiVmGroupName": null,
"multiVmGroupId": null,
"recoveryBootDiagStorageAccountId": null
}
}
}Refer to the exhibit. You are reviewing an Azure Site Recovery replicated item for a VM. The replication health is Normal, and the last recovery point is at 10:30 AM. The primary region experiences a failure at 10:35 AM. You initiate a failover at 10:40 AM. What is the maximum potential data loss?
⚠ Common exam trap
Many exam-takers confuse the time between the last recovery point and the failover initiation (10 minutes) with the actual data loss window, which is bounded by the failure time, not the failover time.
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
✓
5 minutes of data
The last recovery point was at 10:30 AM, and the failover was initiated at 10:40 AM. Since the failure occurred at 10:35 AM, any data written between 10:30 AM and 10:35 AM (5 minutes) that was not yet replicated to the recovery point is lost. Azure Site Recovery replicates asynchronously, so the maximum potential data loss equals the time between the last successful recovery point and the failure event.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
5 minutes of data
Why this is correct
The recovery point created at 10:30 is the most recent point that can be used for failover. Since the failure occurred at 10:35, all changes made between 10:30 and 10:35 are not replicated to the recovery point and are therefore lost. This matches Azure Site Recovery's typical 5-minute Recovery Point Objective (RPO) for asynchronous replication, so the maximum data loss is exactly the 5-minute gap between the last consistent recovery point and the failure time.
- ✗
15 minutes of data
Why it's wrong here
A 15-minute loss would imply that the last available recovery point was at 10:20, leaving data from 10:20 through 10:35 unprotected. However, the exhibit shows that a valid recovery point exists at 10:30, so all data committed before 10:30 is available and can be restored. Therefore, the actual loss is confined to the 5-minute window after 10:30, not the 15 minutes spanning multiple earlier recovery points.
- ✗
0 minutes of data
Why it's wrong here
This option would require Azure Site Recovery to provide synchronous replication with zero Recovery Point Objective, meaning every write is immediately applied to the replica before the source acknowledges the request. In practice, Azure Site Recovery uses asynchronous replication with a periodic recovery point creation lag, so there is always a short interval of data at the source that has not yet been replicated. The exhibit confirms data loss occurred, so a zero-loss outcome is impossible.
- ✗
10 minutes of data
Why it's wrong here
If you mistakenly assume the last recovery point is 10:25, you would calculate a 10-minute loss from 10:25 to 10:35. However, the exhibit clearly shows the last recovery point is 10:30, not 10:25. Since the failure happened at 10:35, the unreplicated window is only from 10:30 to 10:35, giving exactly 5 minutes of data loss—not the 10 that would follow from misreading the recovery point timeline.
Go deeper
Related to this question
Learn chapter
Event-Driven Architecture with Event Grid and Service Bus
Key term
Azure Site Recovery
Azure Site Recovery is a Microsoft Azure service that keeps your business applications and data running by automatically replicating them to a secondary location and failing over if the primary site goes down.
Key term
Disaster Recovery Design
Disaster Recovery Design is the process of planning and implementing strategies to restore IT systems and data after a catastrophic failure, ensuring business continuity with minimal downtime and data loss.
About these practice questions
This AZ-305 question is part of Courseiva's 795-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-305 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-305 exam.