The answer is to enable Spark Dynamic Resource Allocation and combine small files using a separate job before the main transformation. This is correct because the core bottleneck when optimizing Spark small files on Dataproc is the massive task overhead from listing millions of tiny files—each 10 KB file forces Spark to create a separate partition, overwhelming the driver with metadata and scheduling. By pre-combining files into larger blocks (e.g., 128 MB), you slash the number of tasks and file listings, directly cutting the 4-hour runtime without scaling the cluster. On the Google Professional Data Engineer exam, this scenario tests your understanding of Spark’s file listing and task scheduling limits versus compute scaling; a common trap is to mistakenly choose increasing partitions or repartitioning, which only worsens overhead. Remember the memory tip: “Small files, big overhead—combine first, then transform.”
PDE Practice Question: Building and operationalizing data processing systems
This PDE practice question tests your understanding of building and operationalizing data processing systems. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
Your organization has a data lake on Cloud Storage with millions of small files (average 10 KB). You need to build a batch processing pipeline using Cloud Dataproc that runs a Spark job to transform the data and output results to BigQuery. The pipeline currently takes 4 hours to run because Spark spends a large amount of time listing files and managing tasks. You want to reduce the run time without changing the cluster size. Which action should you take?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable the Spark Dynamic Resource Allocation and combine small files using a separate job before the main transformation
Option D is correct because the primary bottleneck is the overhead of listing millions of small files and managing many Spark tasks. By combining small files into larger ones using a separate job before the main transformation, you reduce the number of files Spark must list and the number of tasks required, which directly cuts the 4-hour runtime. Enabling Spark Dynamic Resource Allocation ensures resources are used efficiently during this preprocessing step without changing the cluster size.
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.
✗
Convert the input files from CSV to Parquet format
Why it's wrong here
Format change doesn't reduce file count.
✗
Use Spark coalesce to reduce the number of output partitions
Why it's wrong here
Coalesce reduces partitions after processing, not input file overhead.
✗
Increase the number of Spark partitions to process more files in parallel
Why it's wrong here
More partitions increase overhead.
✓
Enable the Spark Dynamic Resource Allocation and combine small files using a separate job before the main transformation
Why this is correct
Combining files reduces task count and listing overhead.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates focus on data format or partitioning tuning (A, B, C) instead of recognizing that the root cause is the sheer number of small files causing excessive file listing and task overhead, which requires a preprocessing step to consolidate files.
Detailed technical explanation
How to think about this question
Under the hood, Spark's FileInputFormat (used for Cloud Storage via the Hadoop Connector) lists all files in the input path and creates one partition per file or per block; with millions of 10 KB files, the listing phase can dominate runtime due to RPC overhead and the scheduler must manage millions of tasks, each with serialization and launch costs. Combining files into larger chunks (e.g., 128 MB) reduces the number of partitions to a manageable number, allowing Spark to process data in fewer, more efficient tasks. In real-world scenarios, this technique is critical for data lakes with high-frequency ingestion producing many small files, such as IoT sensor logs or clickstream data.
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.
Building and operationalizing data processing systems — This question tests Building and operationalizing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable the Spark Dynamic Resource Allocation and combine small files using a separate job before the main transformation — Option D is correct because the primary bottleneck is the overhead of listing millions of small files and managing many Spark tasks. By combining small files into larger ones using a separate job before the main transformation, you reduce the number of files Spark must list and the number of tasks required, which directly cuts the 4-hour runtime. Enabling Spark Dynamic Resource Allocation ensures resources are used efficiently during this preprocessing step without changing the cluster size.
What should I do if I get this PDE 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 →
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 PDE practice question is part of Courseiva's free Google Cloud 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 PDE 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.