SAA-C03 Design High-Performing Architectures Practice Question
A data engineering team runs an Amazon EMR cluster that processes large datasets stored in Amazon S3. The cluster uses Amazon EBS volumes for temporary storage, and jobs frequently spill intermediate data to disk. The team notices that shuffle operations are slow and wants to improve performance without changing the data format or increasing the number of core nodes. Which change should the team make?
⚠ Common exam trap
The trap here is assuming that adding more nodes or increasing EBS size will fix a shuffle bottleneck that is actually caused by local disk latency.
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
✓
Replace the EBS volumes with instance store volumes and configure EMR to use them for shuffle and temporary data.
Shuffle-heavy EMR workloads benefit from fast local storage, and instance store volumes provide higher IOPS and lower latency than EBS. Configuring EMR to use instance store for shuffle and temporary data reduces spill time and improves job performance without adding core nodes or altering data formats. Managed scaling, larger EBS volumes, and S3-backed shuffle either do not address the local disk bottleneck or introduce additional latency.
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 size of the existing EBS volumes and enable EBS optimization on the core nodes.
Why it's wrong here
EBS optimization and larger volumes can improve throughput to some degree, but EBS is network-attached storage and still has higher latency than instance store for shuffle-intensive workloads. The change may not deliver the needed performance gain and can increase cost. The scenario points to a local disk bottleneck that instance store is better suited to resolve.
- ✗
Move the intermediate data to an Amazon S3 bucket and configure EMR to use S3 for shuffle storage.
Why it's wrong here
Using S3 for shuffle storage introduces network latency and request costs, and it is generally slower than local disk for frequent small writes. While S3 is durable and scalable, shuffle operations benefit from low-latency local storage. This approach would likely worsen performance rather than improve it, and it does not align with the goal of faster shuffle operations.
- ✗
Enable EMR managed scaling to automatically add task nodes during shuffle-heavy stages.
Why it's wrong here
EMR managed scaling adjusts cluster size based on workload, but adding task nodes does not change the storage performance of existing core nodes where shuffle data is written. It can help overall throughput, but the scenario explicitly asks to improve performance without increasing core nodes, and shuffle spill latency is a local disk issue. Managed scaling alone does not address the slow local storage.
- ✓
Replace the EBS volumes with instance store volumes and configure EMR to use them for shuffle and temporary data.
Why this is correct
Instance store volumes provide locally attached NVMe or SSD storage with higher throughput and lower latency than EBS for temporary data. EMR can be configured to use instance store for shuffle and scratch space, which speeds up spill-heavy operations. This improves performance without adding core nodes or changing the data format, directly addressing the shuffle bottleneck.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 935-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This SAA-C03 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 SAA-C03 exam.