Azure Backup Weekly Retention Rule: Keep Weekly Backups for 52 Weeks
Exhibit
Recovery Services vault > Backup policy: Policy-Prod Backup schedule: Daily at 01:00 UTC Retention: - Daily recovery points: 30 days - Weekly recovery points: not configured - Monthly recovery points: not configured Business requirement: retain one weekly recovery point for 1 year
Based on the exhibit, compliance requires one backup every week to be kept for 52 weeks, in addition to the daily backups already configured. What should you change in the backup policy?
Quick Answer
The answer is to add a weekly retention rule that keeps one weekly recovery point for 52 weeks. This directly satisfies the compliance requirement because Azure Backup policies allow you to define separate retention rules for different frequencies—daily, weekly, monthly, and yearly—without interfering with each other. By adding a weekly rule that retains a single recovery point per week for the full 52-week period, you ensure that each weekly backup is preserved for a year while the existing daily backups remain untouched. On the AZ-104 exam, this scenario tests your understanding of Azure Backup’s granular retention policy configuration, often appearing as a multiple-choice or exhibit-based question where a common trap is to mistakenly extend the daily retention period or add a monthly rule instead. Remember the key distinction: daily rules handle short-term retention, while weekly rules are for long-term compliance like this 52-week requirement. A helpful memory tip is “weekly for the year, daily for the near”—weekly rules cover the full-year retention, leaving daily rules for shorter-term recovery needs.
⚠ Common exam trap
Many candidates confuse retention duration with backup frequency, mistakenly thinking that increasing daily retention to 365 days will satisfy the weekly requirement, when in fact it would retain all daily backups instead of just one per week.
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
✓
Add a weekly retention rule that keeps one weekly recovery point for 52 weeks.
The requirement is to retain one weekly backup for 52 weeks, in addition to the existing daily backups. Adding a weekly retention rule that keeps one recovery point per week for 52 weeks directly satisfies this requirement by ensuring that each weekly backup is retained for the full year, while daily backups remain unaffected. This is the correct approach because Azure Backup allows granular retention policies with multiple rules for different frequencies (daily, weekly, monthly, yearly).
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the daily retention from 30 days to 365 days.
Why it's wrong here
Longer daily retention increases the number of daily recovery points kept, but it does not specifically create one weekly recovery point pattern for compliance.
When this WOULD be correct
This would be correct if the compliance requirement was to retain all daily backups for 52 weeks (e.g., for audit purposes requiring daily point-in-time recovery for a full year).
- ✓
Add a weekly retention rule that keeps one weekly recovery point for 52 weeks.
Why this is correct
The requirement is specific: keep one backup each week for a year. That is a weekly retention requirement, not just longer daily retention. Adding a weekly retention rule to the Azure Backup policy satisfies the compliance need while preserving the existing daily backups for operational recovery.
- ✗
Change the vault to use soft delete so backups are retained for 52 weeks.
Why it's wrong here
Soft delete protects backup items from accidental deletion, but it does not define backup schedule or retention periods for weekly compliance copies.
When this WOULD be correct
If the question required protecting against accidental deletion of backups and retaining deleted backups for 52 weeks for compliance, then enabling soft delete with a retention duration of 52 weeks would be correct.
- ✗
Create a metric alert to warn the team when backups are older than seven days.
Why it's wrong here
A metric alert can notify people about a condition, but it does not change retention behavior or create the required weekly recovery points.
When this WOULD be correct
This option would be correct if the question asked for a method to monitor backup compliance and alert the team when backups are not being taken within the required timeframe, such as ensuring a backup is taken every seven days.
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.
✓Add a weekly retention rule that keeps one weekly recovery point for 52 weeks.Correct answer▾
Why this is correct
The requirement is specific: keep one backup each week for a year. That is a weekly retention requirement, not just longer daily retention. Adding a weekly retention rule to the Azure Backup policy satisfies the compliance need while preserving the existing daily backups for operational recovery.
✗Increase the daily retention from 30 days to 365 days.Wrong answer — click to see why▾
Why this is wrong here
Increasing daily retention to 365 days would keep every daily backup for a year, not just one per week. The requirement is to keep one weekly backup for 52 weeks, not all daily backups.
★ When this WOULD be the correct answer
This would be correct if the compliance requirement was to retain all daily backups for 52 weeks (e.g., for audit purposes requiring daily point-in-time recovery for a full year).
Why candidates choose this
Candidates may think that extending daily retention is a simpler way to meet the weekly retention requirement, misunderstanding that it retains all daily backups rather than just one per week.
✗Change the vault to use soft delete so backups are retained for 52 weeks.Wrong answer — click to see why▾
Why this is wrong here
Soft delete retains deleted backup data for a specified duration, but it does not create additional weekly recovery points. The requirement is to keep one backup per week for 52 weeks, which requires a retention rule, not soft delete.
★ When this WOULD be the correct answer
If the question required protecting against accidental deletion of backups and retaining deleted backups for 52 weeks for compliance, then enabling soft delete with a retention duration of 52 weeks would be correct.
Why candidates choose this
Candidates may confuse soft delete with long-term retention, thinking that enabling it automatically keeps backups for the specified period without understanding that soft delete only applies to deleted backups and does not create new recovery points.
✗Create a metric alert to warn the team when backups are older than seven days.Wrong answer — click to see why▾
Why this is wrong here
Creating a metric alert does not change the backup retention policy; it only notifies when backups are older than seven days, which does not meet the compliance requirement of retaining one weekly backup for 52 weeks.
★ When this WOULD be the correct answer
This option would be correct if the question asked for a method to monitor backup compliance and alert the team when backups are not being taken within the required timeframe, such as ensuring a backup is taken every seven days.
Why candidates choose this
Candidates may think that alerting on backup age helps enforce retention, but alerts only notify, they do not retain backups. The focus on 'older than seven days' might seem related to weekly backups.
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
Compliance
Compliance is the process of ensuring that an organization follows laws, regulations, standards, and internal policies that apply to its operations and data handling.
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. Based on the exhibit, the backup policy must support 30-day recovery for daily backups while keeping 12 months of monthly copies. Which setting should be changed?
medium- ✓ A.Increase daily retention from 7 days to 30 days.
- B.Increase weekly retention from 4 weeks to 30 weeks.
- C.Change the backup schedule to every 30 days.
- D.Turn on archive tier for the backup policy.
Why A: The backup policy currently has daily retention set to 7 days, which only keeps daily recovery points for a week. To meet the requirement of 30-day recovery for daily backups, you must increase the daily retention to 30 days. This ensures that each daily backup is retained for 30 days, allowing point-in-time recovery within that window.
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.