The correct combination is to increase InstanceCount to 4 and convert the data to Parquet format. This works because scaling out to four ml.m5.large instances lets each process 50 GB in parallel, directly cutting the wall-clock time, while Parquet’s columnar storage and predicate pushdown drastically reduce I/O and CPU overhead compared to row-based CSV. On the AWS Certified Machine Learning Engineer Associate MLA-C01 exam, this scenario tests your understanding of distributed data processing and format optimization for SageMaker Processing jobs—a common trap is assuming only instance size matters, when in fact data format and parallelism are equally critical. A useful memory tip: think “scale out, not up, and columnar cuts the clock.”
MLA-C01 Data Preparation for Machine Learning Practice Question
This MLA-C01 practice question tests your understanding of data preparation for machine learning. 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.
A company uses SageMaker Processing jobs to clean customer transaction data. The processing script runs on a single ml.m5.large instance and takes 30 minutes to process 50 GB of data in CSV format. To reduce processing time, the company wants to process 200 GB of data within 1 hour. Which combination of changes should the company make?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Increase InstanceCount to 4 and convert the data to Parquet format.
Option C is correct because increasing InstanceCount to 4 allows parallel processing of the 200 GB dataset across multiple ml.m5.large instances, each handling 50 GB, which directly reduces processing time. Converting the data from CSV to Parquet format further accelerates processing by enabling columnar storage and predicate pushdown, reducing I/O and CPU overhead. Together, these changes can achieve the goal of processing 200 GB within 1 hour, as the original 50 GB took 30 minutes on a single instance.
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.
✗
Run the job in local mode with a larger EBS volume.
Why it's wrong here
Local mode is for testing on the notebook instance and does not scale.
✗
Increase VolumeSizeInGB to 100 and use gzip compression.
Why it's wrong here
Volume size is not a performance bottleneck; compression may reduce I/O but not parallelism.
✓
Increase InstanceCount to 4 and convert the data to Parquet format.
Why this is correct
Multiple instances provide parallelism, and Parquet reduces I/O.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a larger instance type (e.g., ml.r5.4xlarge) and keep the same script.
Why it's wrong here
Increasing instance type helps but scaling is not linear; improved parallelism from multiple instances is needed.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume vertical scaling (larger instance) is sufficient, but the MLA-C01 exam tests understanding that horizontal scaling combined with data format optimization (Parquet) is required to meet strict time constraints for large datasets.
Detailed technical explanation
How to think about this question
SageMaker Processing jobs support distributed processing by setting InstanceCount > 1, which shards the input data across instances using S3 prefix-based partitioning; Parquet format is optimized for this because it is splittable and supports column pruning, reducing data scanned per instance. Under the hood, Parquet uses row group boundaries and metadata to allow each instance to read only its assigned portion, whereas CSV requires full scans and parsing. In real-world scenarios, converting to Parquet can reduce data size by 2-5x and processing time by 3-10x due to compression and efficient encoding like dictionary and run-length encoding.
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.
Data Preparation for Machine Learning — This question tests Data Preparation for Machine Learning — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Increase InstanceCount to 4 and convert the data to Parquet format. — Option C is correct because increasing InstanceCount to 4 allows parallel processing of the 200 GB dataset across multiple ml.m5.large instances, each handling 50 GB, which directly reduces processing time. Converting the data from CSV to Parquet format further accelerates processing by enabling columnar storage and predicate pushdown, reducing I/O and CPU overhead. Together, these changes can achieve the goal of processing 200 GB within 1 hour, as the original 50 GB took 30 minutes on a single instance.
What should I do if I get this MLA-C01 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 MLA-C01 practice question is part of Courseiva's free Amazon Web Services 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 MLA-C01 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.