The answer is that the load is slow because the source files are too many and too small, such as thousands of 1 MB files. PolyBase in Azure Synapse Analytics is optimized for reading large, contiguous files; each tiny file forces a separate read operation with its own overhead for file open, close, and metadata requests, which dramatically reduces throughput compared to fewer, larger files. On the DP-203 exam, this tests your understanding of PolyBase’s batch-oriented architecture and the importance of file size in data movement—a common trap is assuming more parallel files always speed up the process. Remember the memory tip: “Small files, big delays; big files, PolyBase pays.”
DP-203 Develop data processing Practice Question
This DP-203 practice question tests your understanding of develop data processing. 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 optimizing a pipeline in Azure Data Factory that copies data from Azure Blob Storage to Azure Synapse Analytics. The pipeline uses a copy activity with PolyBase. The data is partitioned by date in Blob Storage. You notice that the load is slow. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The source files are too many and too small (e.g., thousands of 1 MB files)
PolyBase in Azure Synapse Analytics performs best when reading large, contiguous files. When the source contains thousands of small files (e.g., 1 MB each), PolyBase must initiate a separate read operation for each file, causing excessive overhead from file open/close operations and metadata requests. This dramatically reduces throughput compared to reading fewer, larger files.
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 source files are stored in Azure Blob Storage instead of Data Lake Storage Gen2
Why it's wrong here
PolyBase works with Blob Storage.
✗
The source files are in CSV format instead of Parquet
Why it's wrong here
PolyBase supports CSV, so this is not a significant issue.
✓
The source files are too many and too small (e.g., thousands of 1 MB files)
Why this is correct
Many small files cause overhead; PolyBase is optimized for fewer, larger files.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The sink table has a clustered columnstore index
Why it's wrong here
Columnstore is actually beneficial for PolyBase loading.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often focus on file format (Parquet vs. CSV) or storage type (Blob vs. ADLS Gen2) as the primary performance factor, when in reality the number and size of files is a more common and impactful bottleneck in PolyBase loads.
Detailed technical explanation
How to think about this question
PolyBase uses a distributed data movement service (DMS) that schedules file splits across compute nodes. With many small files, the DMS spends disproportionate time on scheduling and coordination rather than data transfer. A best practice is to coalesce small files into larger ones (e.g., 256 MB or more) to maximize parallelism and minimize overhead. Additionally, PolyBase reads files sequentially within a single file, so small files underutilize the available bandwidth.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Develop data processing — This question tests Develop data processing — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The source files are too many and too small (e.g., thousands of 1 MB files) — PolyBase in Azure Synapse Analytics performs best when reading large, contiguous files. When the source contains thousands of small files (e.g., 1 MB each), PolyBase must initiate a separate read operation for each file, causing excessive overhead from file open/close operations and metadata requests. This dramatically reduces throughput compared to reading fewer, larger files.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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-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.