Azure SQL Long-Term Retention Backup Periods

Design solutions for backup and disaster recovery
Answer Correct answer: F — Weekly, monthly, and yearly backup periods can all be included in an Azure SQL Database Long-Term Retention solution.

You have an Azure subscription that contains an Azure SQL database named DB1. You need to recommend a long-term retention (LTR) backup solution for DB1. The solution must ensure that backups can be retained for up to seven years. Which backup periods can you include in the solution?

  1. weekly only
  2. monthly only
  3. yearly only
  4. weekly and monthly only
  5. monthly and yearly only
  6. weekly, monthly, and yearly Correct Answer

Community Insight

The question tests knowledge of Azure SQL LTR capabilities and the common trap is confusing it with short-term retention or assuming only one period is allowed.

This page explains the supported backup periods for Azure SQL Database Long-Term Retention (LTR) policies. It establishes that weekly, monthly, and yearly backups can all be included in a single LTR solution.

Learners often select 'monthly and yearly only' because they associate long-term retention primarily with compliance cycles, forgetting that weekly backups are also part of the LTR hierarchy.

Community Discussion (1 comments)

Ras1364 👍 2 Selected: F
The question asks: Which backup periods can you include in the solution? Notice it does not ask: Which backup period is sufficient? It asks: Which backup periods can be included? In Azure SQL Database Long-Term Retention (LTR), you can define retention for: Weekly backups (W) Monthly backups (M) Yearly backups (Y) An LTR policy supports combinations of all three.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Azure SQL Database Long-Term Retention (LTR) allows you to retain copies of your weekly, monthly, and yearly backups for up to 10 years. To implement an LTR policy, you must first enable weekly LTR backups, then optionally enable monthly and yearly LTR backups. Therefore, a comprehensive solution can include all three periods to meet specific compliance requirements like seven-year retention.

Why the Other Options Are Wrong

Options limiting the selection to weekly, monthly, or pairs thereof are incorrect because they exclude valid components of the LTR framework. For instance, excluding yearly backups would prevent meeting multi-year retention mandates, while excluding weekly backups ignores the base frequency from which monthly/yearly snapshots are derived. The question asks what can be included, not what is minimal.

Community Comment Notes

Community consensus correctly identifies that all three periods are supportable. As noted by user Ras1364, "An LTR policy supports combinations of all three." This aligns with Microsoft documentation stating that you can define separate retention policies for each backup type within the LTR scope.

Official Reference

Exam Strategy

When designing backup solutions, always check if the service supports hierarchical retention. In Azure SQL LTR, remember that weekly, monthly, and yearly are distinct but combinable options for long-term storage needs.

Frequently Asked Questions

Can I use only yearly backups for LTR?

No, you must enable weekly LTR backups as a prerequisite before enabling monthly or yearly LTR backups.

What is the maximum retention period for Azure SQL LTR?

Azure SQL Database LTR allows you to retain backups for up to 10 years.

More AZ-305 FAQ →

Related Analysis

Practice All AZ-305 Questions

Access 95 questions with complete answers and detailed explanations.

View Full AZ-305 Practice Test →

← Back to AZ-305 Study Guide