- A
/data/{date}/{source_system}/ (e.g., /data/2023-01-01/SourceA/)
Why wrong: Date-first may lead to many small partitions across sources.
- B
/data/{source_system}/{date}/ (e.g., /data/SourceA/2023-01-01/)
This structure separates sources and dates, enabling efficient query pruning.
- C
/data/{source_system}/ with files named {timestamp}.csv/.json/.parquet
Why wrong: No date partitioning, leading to poor query performance.
- D
/data/{source_system}/{year}/{month}/{day}/ (e.g., /data/SourceA/2023/01/01/)
Why wrong: This is also valid but more nested; main issue is mixing formats if not careful. However, it's acceptable.
Quick Answer
The recommended folder structure is /data/{source_system}/{date}/, which places the source system partition first and the ingestion date partition second. This design is correct because Azure Synapse Serverless SQL performs partition elimination most efficiently when the leading partition column matches the most frequently filtered attribute—here, the source system—while the trailing date partition enables pruning on ingestion time. The hierarchical layout maps directly to Hive-style partitioning, which Synapse Serverless SQL natively supports across CSV, JSON, and Parquet formats, ensuring optimal query performance without additional metadata management. On the DP-203 exam, this scenario tests your understanding of how folder structure directly impacts partition elimination in serverless SQL pools; a common trap is placing the date first, which forces full scans when filtering by source system. Remember the memory tip: “Source first, date last—partition elimination fast.”
DP-203 Design and implement data storage Practice Question
This DP-203 practice question tests your understanding of design and implement data storage. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
You are designing a solution to store streaming data from multiple sources into Azure Data Lake Storage Gen2. The data must be organized by ingestion time and source system. Each source system produces data in a different format: CSV, JSON, and Parquet. The solution must allow efficient querying using Azure Synapse Serverless SQL and must support partitioning on ingestion date. What is the recommended folder structure?
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
/data/{source_system}/{date}/ (e.g., /data/SourceA/2023-01-01/)
Option B is correct because it places the source system partition first, which aligns with Azure Synapse Serverless SQL's partition elimination behavior when querying by source system. The date partition at the end allows efficient pruning on ingestion date, and the hierarchical folder structure maps directly to Hive-style partitioning, which Synapse Serverless SQL natively supports for CSV, JSON, and Parquet formats.
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.
- ✗
/data/{date}/{source_system}/ (e.g., /data/2023-01-01/SourceA/)
Why it's wrong here
Date-first may lead to many small partitions across sources.
- ✓
/data/{source_system}/{date}/ (e.g., /data/SourceA/2023-01-01/)
Why this is correct
This structure separates sources and dates, enabling efficient query pruning.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
/data/{source_system}/ with files named {timestamp}.csv/.json/.parquet
Why it's wrong here
No date partitioning, leading to poor query performance.
- ✗
/data/{source_system}/{year}/{month}/{day}/ (e.g., /data/SourceA/2023/01/01/)
Why it's wrong here
This is also valid but more nested; main issue is mixing formats if not careful. However, it's acceptable.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose Option D because they assume year/month/day granularity is required for performance, but Azure Synapse Serverless SQL treats each folder level as a separate partition key, and a single date folder is sufficient for efficient pruning without unnecessary complexity.
Detailed technical explanation
How to think about this question
Azure Synapse Serverless SQL uses partition elimination by reading only the subfolders that match the WHERE clause when the folder structure follows a partitioned layout. Under the hood, the OPENROWSET function with PARSER_VERSION='2.0' maps folder paths to virtual columns, enabling predicate pushdown. In real-world scenarios, a single date folder (e.g., /2023-01-01/) is simpler to manage than year/month/day subfolders, and Synapse Serverless SQL can still prune efficiently because it treats the entire date string as a single partition key.
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.
TExam Day Tips
- 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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design and implement data storage — study guide chapter
Learn the concepts, then practise the questions
- →
Design and implement data storage practice questions
Targeted practice on this topic area only
- →
All DP-203 questions
846 questions across all exam domains
- →
Microsoft Azure Data Engineer Associate DP-203 study guide
Full concept coverage aligned to exam objectives
- →
DP-203 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DP-203 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Secure, monitor, and optimize data storage and data processing practice questions
Practise DP-203 questions linked to Secure, monitor, and optimize data storage and data processing.
Design and develop data processing practice questions
Practise DP-203 questions linked to Design and develop data processing.
Design and implement data security practice questions
Practise DP-203 questions linked to Design and implement data security.
Monitor and optimize data storage and processing practice questions
Practise DP-203 questions linked to Monitor and optimize data storage and processing.
Design and implement data storage practice questions
Practise DP-203 questions linked to Design and implement data storage.
Develop data processing practice questions
Practise DP-203 questions linked to Develop data processing.
DP-203 fundamentals practice questions
Practise DP-203 questions linked to DP-203 fundamentals.
DP-203 scenario practice questions
Practise DP-203 questions linked to DP-203 scenario.
DP-203 troubleshooting practice questions
Practise DP-203 questions linked to DP-203 troubleshooting.
Practice this exam
Start a free DP-203 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DP-203 question test?
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: /data/{source_system}/{date}/ (e.g., /data/SourceA/2023-01-01/) — Option B is correct because it places the source system partition first, which aligns with Azure Synapse Serverless SQL's partition elimination behavior when querying by source system. The date partition at the end allows efficient pruning on ingestion date, and the hierarchical folder structure maps directly to Hive-style partitioning, which Synapse Serverless SQL natively supports for CSV, JSON, and Parquet formats.
What should I do if I get this DP-203 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 11, 2026
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.
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.