The answer is that the ARM template error mixing short-term and long-term backup retention properties occurs because long-term retention properties like weeklyRetention, monthlyRetention, and yearlyRetention are not valid within a backupShortTermRetentionPolicies resource. In Azure SQL, point-in-time restore (PITR) is configured exclusively through the backupShortTermRetentionPolicies resource using a retentionDays property—here correctly set to 28 days—while long-term retention (LTR) requires a separate backupLongTermRetentionPolicies resource. This distinction is a frequent trap on the DP-300 exam, testing your ability to separate backup policy resources in ARM templates; many candidates mistakenly combine both retention types into one block, leading to a deployment error. Remember the memory tip: short-term retention uses days only, long-term retention uses weekly, monthly, and yearly—they never share the same resource.
DP-300 Configure and manage automation of tasks Practice Question
This DP-300 practice question tests your understanding of configure and manage automation of tasks. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Refer to the exhibit. You are reviewing an ARM template for an Azure SQL Database backup retention policy. The database is in a business-critical environment that requires point-in-time restore (PITR) for the last 28 days. What is the issue with this configuration?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Long-term retention properties (weeklyRetention, monthlyRetention, yearlyRetention) are not valid in a backupShortTermRetentionPolicies resource.
The ARM template shows both short-term retention (PITR) and long-term retention (LTR) properties. However, PITR retention is set to 28 days (retentionDays), which is valid. The LTR properties (weeklyRetention, monthlyRetention, yearlyRetention) are part of a different resource (backupLongTermRetentionPolicies). Mixing them in the same resource will cause a deployment error. Option C is correct. Option A is wrong because 28 days is within limits. Option B is wrong because LTR is not part of this resource. Option D is wrong because the JSON is syntactically correct.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 JSON syntax is invalid because property names use camelCase instead of PascalCase.
Why it's wrong here
ARM template properties are case-sensitive but camelCase is acceptable; the syntax is valid.
✓
Long-term retention properties (weeklyRetention, monthlyRetention, yearlyRetention) are not valid in a backupShortTermRetentionPolicies resource.
Why this is correct
LTR properties belong to a separate resource type: backupLongTermRetentionPolicies.
Related concept
Read the scenario before looking for a memorised answer.
✗
The diffBackupIntervalInHours should be 12 for a business-critical database.
Why it's wrong here
The differential backup interval can be 12 or 24 hours; 24 is valid, though 12 is more common for business-critical.
✗
The retentionDays value of 28 exceeds the maximum allowed for PITR.
Why it's wrong here
Maximum PITR retention is 35 days; 28 is acceptable.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Identify which DP-300 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Configure and manage automation of tasks — This question tests Configure and manage automation of tasks — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Long-term retention properties (weeklyRetention, monthlyRetention, yearlyRetention) are not valid in a backupShortTermRetentionPolicies resource. — The ARM template shows both short-term retention (PITR) and long-term retention (LTR) properties. However, PITR retention is set to 28 days (retentionDays), which is valid. The LTR properties (weeklyRetention, monthlyRetention, yearlyRetention) are part of a different resource (backupLongTermRetentionPolicies). Mixing them in the same resource will cause a deployment error. Option C is correct. Option A is wrong because 28 days is within limits. Option B is wrong because LTR is not part of this resource. Option D is wrong because the JSON is syntactically correct.
What should I do if I get this DP-300 question wrong?
Identify which DP-300 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DP-300 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 DP-300 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.