DP-203 Design and implement data storage Practice Question
You are designing a solution to store large amounts of log data that is written once and accessed rarely. The data must be retained for 7 years for compliance. After 30 days, the data should be moved to a lower-cost storage tier. After 1 year, the data should be archived. Which Azure Storage lifecycle management policy should you implement for an Azure Data Lake Storage Gen2 account?
⚠ Common exam trap
A common mix-up: candidates confuse the required tiering order (cool then archive) with direct archiving after 30 days (Option C) or fail to include a deletion rule (Option D), missing the 7-year compliance requirement.
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
✓
Transition to cool tier after 30 days; transition to archive tier after 365 days; delete after 2555 days (7 years).
It aligns with the specified lifecycle requirements: transition to cool tier after 30 days for cost savings, transition to archive tier after 365 days for long-term retention, and delete after 2555 days (7 years) for compliance. Azure Data Lake Storage Gen2 supports lifecycle management policies that automate tier transitions and deletion based on age, ensuring data is moved to lower-cost storage as access patterns change.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Transition to cool tier after 30 days; delete after 7 years.
Why it's wrong here
Cool tier at 30 days satisfies the first transition, but deleting at 7 years ignores the mandated archive step at one year, leaving data in cool storage for six years at higher cost. Cool tier is correct only when data remains occasionally accessed and never requires archival.
- ✓
Transition to cool tier after 30 days; transition to archive tier after 365 days; delete after 2555 days (7 years).
Why this is correct
Lifecycle management rules apply tier transitions and deletion by last-modified age, so cool at 30 days, archive at 365 days and deletion at 2555 days exactly match the stated retention and cost requirements for the rarely accessed log data.
- ✗
Transition to archive tier after 30 days; delete after 7 years.
Why it's wrong here
Archiving at 30 days contradicts the stated requirement that data stays in a lower-cost tier until one year, and archive rehydration latency would hinder any access during that period. Archive tier is for data already past its access window, matching the one-year transition the stem specifies.
- ✗
Transition to cool tier after 30 days; transition to cool tier again after 365 days.
Why it's wrong here
Transitioning to cool twice performs no tier change the second time, so data never reaches archive tier at one year and stays in cool storage for the full retention period. Cool tier is for occasionally accessed data; archive tier is the correct destination once access ceases.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DP-203 question from scratch — 509 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-203 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-203 exam.