Question 536 of 846
Monitor and optimize data storage and processinghardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to pre-process the raw data to coalesce small JSON files into larger Parquet files, such as 256 MB each. This is correct because the job’s bottleneck is the 'listing files' stage, where Spark must enumerate thousands of tiny 10 KB JSON files in Azure Data Lake Storage Gen2, incurring excessive metadata operations. By consolidating these files into fewer, larger Parquet files, you reduce the number of file listings and leverage Parquet’s columnar format for faster reads, directly addressing the root cause of the slowdown. On the DP-203 exam, this scenario tests your understanding of file size optimization in Azure Data Lake Storage Gen2 with Databricks, a common pitfall where candidates mistakenly tune cluster size or partitioning instead of file coalescing. A useful memory tip: think "small files, big overhead" — always aim for files around 256 MB to minimize metadata calls and maximize Spark throughput.

DP-203 Practice Question: Monitor and optimize data storage and processing

This DP-203 practice question tests your understanding of monitor and optimize data storage and 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 a data engineer for a retail company. The company uses Azure Data Lake Storage Gen2 to store raw transaction data partitioned by date. Each day, a folder is created with the format 'YYYY/MM/DD' containing thousands of small JSON files (each ~10 KB). An Azure Databricks job runs daily to read the previous day's folder, transform the data, and write to a Delta table for reporting. Over time, the job's execution time has increased from 15 minutes to over 2 hours. The job uses a cluster with 4 nodes (each 16 GB memory). Monitoring shows that the job spends most of its time in the 'listing files' stage. Which optimization should you implement to reduce the job duration?

Question 1hardmultiple choice
Full question →

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

Pre-process the raw data to coalesce small JSON files into larger parquet files (e.g., 256 MB each).

The job spends most of its time in the 'listing files' stage because reading thousands of small JSON files (each ~10 KB) from Azure Data Lake Storage Gen2 incurs high metadata operation overhead. Coalescing these small files into larger Parquet files (e.g., 256 MB each) reduces the number of files that Spark must list and process, dramatically cutting down the listing stage time and improving overall throughput.

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.

  • Increase the number of nodes in the cluster to 16.

    Why it's wrong here

    More nodes increase parallelism but the bottleneck is file listing, which is not fully parallelized.

  • Change the output format from JSON to Delta and enable Delta caching.

    Why it's wrong here

    Delta caching helps reads but does not solve the file listing bottleneck.

  • Pre-process the raw data to coalesce small JSON files into larger parquet files (e.g., 256 MB each).

    Why this is correct

    Reduces the number of files, drastically cutting listing time.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use Azure Data Factory instead of Databricks to copy the raw data.

    Why it's wrong here

    ADF also lists files; the bottleneck remains.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume scaling the cluster (Option A) will solve any performance issue, but they fail to recognize that metadata operations like file listing are not parallelized across nodes and are limited by the storage account's API limits, not compute resources.

Detailed technical explanation

How to think about this question

Azure Data Lake Storage Gen2 uses a hierarchical namespace, and listing files involves REST API calls that are throttled per partition; with thousands of small files, the cumulative latency of these calls becomes the dominant factor. Coalescing into larger Parquet files (e.g., 256 MB) reduces the number of files by orders of magnitude, and Parquet's columnar format also enables predicate pushdown and compression, further accelerating downstream transformations. In practice, a common pattern is to use an initial 'bronze' ingestion job that batches small files into larger optimized files before the main transformation job runs.

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.

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.

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?

Monitor and optimize data storage and processing — This question tests Monitor and optimize data storage and processing — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Pre-process the raw data to coalesce small JSON files into larger parquet files (e.g., 256 MB each). — The job spends most of its time in the 'listing files' stage because reading thousands of small JSON files (each ~10 KB) from Azure Data Lake Storage Gen2 incurs high metadata operation overhead. Coalescing these small files into larger Parquet files (e.g., 256 MB each) reduces the number of files that Spark must list and process, dramatically cutting down the listing stage time and improving overall throughput.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

2 more ways this is tested on DP-203

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. You are a data engineer for a financial services company. You manage an Azure Data Lake Storage Gen2 account that stores real-time stock trade data ingested from Azure Event Hubs via Azure Stream Analytics. The data is partitioned by date and symbol. Each day, a downstream Azure Databricks job runs an ETL process to aggregate trades into 5-minute bars and writes the results to a separate container. The Databricks job runs on a cluster with 10 worker nodes (Standard_DS3_v2) using Auto-Scaling enabled (2-10 workers). Recently, the job has been taking longer than expected, and you observe that the cluster is often at 10 workers but still the job duration increased by 30%. The storage account shows high transaction costs. You suspect the issue is related to how data is read. What should you do to optimize the job's performance and reduce costs?

medium
  • A.Convert the data to Avro format to reduce file size.
  • B.Increase the maximum number of workers to 20 and use a larger instance type.
  • C.Modify the Stream Analytics job to output larger files (e.g., set the minimum file size to 100 MB) and use coalesce in Databricks to reduce the number of output partitions.
  • D.Move the data to Azure Blob Storage Premium tier to reduce latency.

Why C: Option C is correct because the performance issue stems from reading many small files (small file problem) in Azure Data Lake Storage Gen2, which increases transaction costs and slows down Spark jobs. By configuring Stream Analytics to output larger files (e.g., minimum 100 MB) and using coalesce in Databricks to reduce output partitions, you minimize the number of files read/written, reducing overhead and transaction costs. This directly addresses the root cause—high transaction costs and cluster saturation at 10 workers—without unnecessary scaling or tier changes.

Variation 2. A data engineer is optimizing an Azure Data Lake Storage Gen2 account used for big data analytics. The account contains billions of small files (under 1 MB). The analytics jobs are slow and cost more than expected. Which THREE actions should the engineer take to improve performance and reduce costs?

hard
  • A.Convert data to columnar file formats such as Parquet.
  • B.Move data to the cool tier to reduce storage costs.
  • C.Enable soft delete to protect against accidental deletion.
  • D.Use blob index tags to partition data logically.
  • E.Consolidate small files into larger files (e.g., 100 MB or more).

Why A: Option A is correct because converting data to columnar formats like Parquet reduces the amount of data read during analytics queries, as only the necessary columns are scanned. This significantly improves query performance and lowers I/O costs, especially for big data workloads on Azure Data Lake Storage Gen2.

Keep practising

More DP-203 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.