hardMultiple SelectObjective-mapped
Optimizing ADLS Gen2 Query Performance
You are monitoring an Azure Data Lake Storage Gen2 account that stores streaming data from IoT devices. You notice that query performance on the data in Parquet format is degrading over time. You need to improve query performance for both current and future data. Which TWO actions should you take?
Quick Answer
The answer is to convert the Parquet files to Delta Lake format and enable file compaction. This combination directly addresses query performance degradation by leveraging Delta Lake’s ACID transactions and built-in optimization features, specifically file compaction which reduces the number of small files that accumulate over time from streaming data, thereby minimizing metadata overhead and improving scan efficiency. On the Microsoft Azure Data Engineer Associate DP-203 exam, this scenario tests your understanding of how to optimize Azure Data Lake Storage Gen2 query performance using partitioning and Delta Lake, a common pattern for handling streaming IoT workloads. A frequent trap is to focus only on partitioning by a filter column like date—while that helps with predicate pushdown, it does not solve the small-file problem that degrades performance in streaming scenarios. Memory tip: think “compact and partition” like packing a suitcase—fewer, larger items (compacted files) are easier to carry, and grouping them by destination (partitioning) lets you skip unnecessary bags entirely.
⚠ Common exam trap
Candidates often confuse data protection features (like soft delete) or storage migration options (like Azure SQL or NetApp Files) with performance optimization techniques, failing to recognize that partitioning and file format optimization are the standard solutions for improving query performance on large-scale Parquet data in a data lake.
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
✓
Partition the data by a column commonly used in filter conditions.
Partitioning the data by a column commonly used in filter conditions (e.g., date, device ID) enables predicate pushdown in query engines like Azure Synapse or Spark, allowing them to skip irrelevant partitions and scan only the necessary files. This directly addresses the performance degradation by reducing the amount of data read during queries, and it benefits both current and future data when applied consistently.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Move frequently accessed data to Azure SQL Database.
Why it's wrong here
Azure SQL Database is for transactional workloads, not for large-scale analytical queries.
- ✓
Partition the data by a column commonly used in filter conditions.
Why this is correct
Partitioning reduces the amount of data scanned per query.
- ✓
Convert the Parquet files to Delta Lake format and enable file compaction.
Why this is correct
Delta Lake improves performance through ACID transactions and small file compaction.
- ✗
Enable soft delete on the storage account to optimize read performance.
Why it's wrong here
Soft delete is a data protection feature, not a performance optimization.
- ✗
Migrate the data to Azure NetApp Files for lower latency.
Why it's wrong here
NetApp Files is a file share service, not optimized for analytical queries on data lakes.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DP-203 question from scratch — 760 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 →
Same concept, more angles
1 more way 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 have an Azure Data Lake Storage Gen2 account that stores large volumes of parquet files. A reporting application frequently queries a specific subset of data filtered by a 'region' column. To minimize query latency and cost, which optimization should you implement?
medium- ✓ A.Partition the data by region in the folder structure.
- B.Create a clustered index on the region column.
- C.Compress the parquet files using gzip.
- D.Enable hierarchical namespace on the storage account.
Why A: Partitioning the data by region in the folder structure (e.g., /region=NorthAmerica/...) enables Azure Data Lake Storage Gen2 and query engines like Azure Synapse or PolyBase to perform partition pruning. This skips scanning irrelevant files entirely, reducing I/O and query latency while lowering cost by minimizing data processed.
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.