Changing Backup Schedule and Retention Without Re-Onboarding
A virtual machine is already protected by Azure Backup. The business wants the VM backed up every day at 11:00 PM and wants daily recovery points retained for 30 days, without re-onboarding the VM. What should the administrator modify?
Quick Answer
The answer is to modify the backup policy associated with the protected VM. Azure Backup decouples the backup schedule and retention rules from the resource itself through a policy object, meaning you can adjust the backup time to 11:00 PM and set daily recovery point retention to 30 days by simply editing the existing policy—no need to stop protection or re-onboard the VM. On the AZ-104 exam, this tests your understanding that policies are reusable templates applied to vault items; a common trap is thinking you must create a new vault or reconfigure the backup, which wastes time and risks data gaps. Remember, policies control when and how long, not where—the vault stays the same. For a memory tip: think of the policy as a thermostat—you adjust the temperature (schedule and retention) without replacing the whole HVAC system.
⚠ Common exam trap
Test-takers frequently think changing the backup schedule or retention requires re-onboarding the VM or creating a new vault, but Azure Backup allows in-place policy modification for already protected resources.
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
✓
Modify the backup policy associated with the protected VM
Azure Backup uses backup policies to define the backup schedule and retention rules for protected resources. By modifying the existing policy associated with the VM, you can change the backup time to 11:00 PM and set daily recovery point retention to 30 days without needing to re-onboard the VM or create a new vault.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a new Recovery Services vault and re-register the VM
Why it's wrong here
A new vault is unnecessary for changing retention or schedule, and re-registering adds avoidable operational work.
When this WOULD be correct
This option would be correct if the question stated that the VM is not currently protected by Azure Backup and needs to be onboarded to a new vault with a specific policy, or if the existing vault is in a different region or subscription that cannot be used.
- ✓
Modify the backup policy associated with the protected VM
Why this is correct
Backup schedule and retention are controlled by the backup policy in the Recovery Services vault. Updating that policy changes how future recovery points are created and retained for the protected VM. This is the correct operational object to edit because the VM is already onboarded and the requirement is to adjust policy settings, not the vault itself.
- ✗
Install a new VM extension to change retention behavior
Why it's wrong here
VM extensions are not used to define Azure Backup schedules or retention periods for Recovery Services vault protection.
When this WOULD be correct
If a VM is not backing up properly due to a missing or corrupted backup extension, reinstalling the extension can restore backup functionality without changing the policy.
- ✗
Take a manual snapshot of the VM disk every night
Why it's wrong here
Snapshots are not the same as Azure Backup policy-based protection and do not provide the same retention management or restore workflow.
When this WOULD be correct
If the question asked for a temporary, ad-hoc backup outside of the existing policy (e.g., before a risky change) and the business does not require automated retention or scheduling, a manual snapshot would be appropriate.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓Modify the backup policy associated with the protected VMCorrect answer▾
Why this is correct
Backup schedule and retention are controlled by the backup policy in the Recovery Services vault. Updating that policy changes how future recovery points are created and retained for the protected VM. This is the correct operational object to edit because the VM is already onboarded and the requirement is to adjust policy settings, not the vault itself.
✗Create a new Recovery Services vault and re-register the VMWrong answer — click to see why▾
Why this is wrong here
Creating a new Recovery Services vault and re-registering the VM is unnecessary because the existing vault and backup policy can be modified to meet the new schedule and retention requirements without re-onboarding.
★ When this WOULD be the correct answer
This option would be correct if the question stated that the VM is not currently protected by Azure Backup and needs to be onboarded to a new vault with a specific policy, or if the existing vault is in a different region or subscription that cannot be used.
Why candidates choose this
Candidates may think that changing the backup schedule or retention requires a new vault or re-registration, not realizing that existing backup policies can be edited and applied to protected VMs.
✗Install a new VM extension to change retention behaviorWrong answer — click to see why▾
Why this is wrong here
Installing a new VM extension does not change backup retention or schedule; Azure Backup policies control retention and frequency, not VM extensions.
★ When this WOULD be the correct answer
If a VM is not backing up properly due to a missing or corrupted backup extension, reinstalling the extension can restore backup functionality without changing the policy.
Why candidates choose this
Candidates may think that backup behavior is controlled by VM-level extensions, confusing the backup extension with policy settings.
✗Take a manual snapshot of the VM disk every nightWrong answer — click to see why▾
Why this is wrong here
Taking a manual snapshot does not integrate with Azure Backup's retention policy or schedule; it requires manual effort and does not satisfy the requirement for automated daily backups with 30-day retention.
★ When this WOULD be the correct answer
If the question asked for a temporary, ad-hoc backup outside of the existing policy (e.g., before a risky change) and the business does not require automated retention or scheduling, a manual snapshot would be appropriate.
Why candidates choose this
Candidates may think manual snapshots are a quick way to achieve the desired retention without understanding that Azure Backup policies automate scheduling and retention, making manual snapshots inefficient and non-compliant with the stated requirements.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Managed Identities for Azure Resources
Key term
Azure Backup
Azure Backup is a cloud-based service from Microsoft that protects your data by creating and storing backups of files, folders, virtual machines, databases, and entire servers in the Azure cloud.
Key term
Policy
A policy is a set of rules or guidelines that defines how an organization manages, secures, and operates its IT systems and services.
About these practice questions
Courseiva writes every AZ-104 question from scratch — 1,049 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AZ-104
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A virtual machine is already protected by Azure Backup. The current policy runs daily at 23:00 and keeps daily recovery points for 30 days. The business now wants the same schedule but wants new daily recovery points retained for 90 days. No new vault or re-registration should occur. What should the administrator do?
hard- A.Create a new Recovery Services vault and enable backup again with the longer retention period.
- ✓ B.Edit the existing backup policy and change the daily retention for future recovery points.
- C.Take nightly managed disk snapshots because snapshots automatically inherit the Recovery Services vault retention period.
- D.Change the vault redundancy setting to increase the number of retained recovery points.
Why B: Azure Backup allows you to modify an existing backup policy to change the retention duration for future recovery points without creating a new vault or re-registering the VM. By editing the policy and setting the daily retention to 90 days, all new daily recovery points will be retained for the longer period, while existing recovery points remain unaffected by the change.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 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-104 exam.