Least-Overhead Managed Image Processing Workflow on AWS?
Short answer
B Use AWS Batch jobs to process the images, AWS Step Functions to orchestrate the workflow, and Amazon S3 to store the processed files.
Question
Key Takeaways
The question tests whether you map a batch-processing workload to a fully managed compute service plus a managed orchestrator and object storage; the trap is picking a self-managed EC2/ECS design or a filesystem that is not needed.
This SAA-C03 scenario asks for the lowest-operational-overhead way to run a growing multi-step image processing pipeline on AWS without managing servers. The answer is AWS Batch for job processing, AWS Step Functions for orchestration, and Amazon S3 for the large generated output files.
Common mistake: Choosing option A (ECS on Spot Instances with SQS and EFS) because Spot is cheap and SQS decouples components — but the team still owns cluster capacity, task definitions and a shared filesystem, which contradicts the 'no infrastructure management' requirement.
Expert Analysis
Why the Answer Is Correct
AWS Batch is a fully managed batch-computing service: it provisions and scales the underlying compute (including Spot capacity), queues jobs, retries failures and schedules work based on job priority, so the company never manages servers or cluster capacity for thousands of image-processing jobs. AWS Step Functions expresses the multi-step workflow (submit, process, watermark, store, notify) as a state machine, so error handling, branching and sequencing happen automatically instead of through manual scripting or polling. Amazon S3 stores the large generated output files durably, with virtually unlimited scale and pay-for-what-you-use pricing, which fits the 'generates large files' part of the scenario. Together these three services deliver the required scale and automation with the least operational overhead of any option.
Why the Other Options Are Wrong
Option A uses Amazon ECS with Spot Instances, SQS and EFS: the team must still pick instance types, manage container host capacity, handle Spot interruptions itself and operate an EFS filesystem, and EFS is a costlier fit for archiving large output artifacts than S3. Option C pairs Lambda with Spot Instances and Amazon FSx — Lambda's time and payload limits make long-running image processing risky, mixing Spot instances reintroduces infrastructure management, and FSx (Windows/Lustre) only makes sense when a shared high-performance POSIX filesystem is genuinely required. Option D is the weakest: a fixed group of EC2 instances plus EBS volumes means patching, AMI maintenance, per-instance block storage and no elastic scaling, so it directly violates the 'no infrastructure management' and 'growing number of jobs' requirements.
Community Comment Notes
LeonSauveterre weighs the Spot-interruption risk in options A and C and points out that "AWS Batch is a fully managed service for batch processing", noting that it scales automatically and removes infrastructure management while Step Functions adds robust orchestration. Ell89 makes the simplest disqualifier: "all other answers mention EC2", which conflicts with the company not wanting to manage underlying infrastructure. trinh_le flags that "Amazon FSx is not an ideal compared to s3" for the output files and also calls out ECS complexity, reinforcing S3 as the storage target.
Official Reference
- https://docs.aws.amazon.com/batch/latest/userguide/what-is-batch.html
- https://docs.aws.amazon.com/step-functions/latest/dg/welcome.html
These links open the official vendor documentation in a new tab.
Exam Strategy
When a scenario says 'least operational overhead' and 'does not want to manage infrastructure', immediately eliminate answers built on EC2 instances, ECS clusters or EBS volumes you must operate yourself. Then match each pipeline stage to a managed service: AWS Batch for the compute jobs, Step Functions for orchestration, and S3 for large output artifacts.
Frequently Asked Questions
Why is AWS Batch better than ECS with EC2 Spot Instances for this image processing workload?
Why is Amazon S3 used for the processed files instead of Amazon FSx or EFS?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 4
-
trinh_le 👍 4 Answered BA. Use Amazon Elastic Container Service (Amazon ECS) complexity C. Amazon FSx is not an ideal compared to s3 D. Use a group of Amazon EC2 instances do not scalable
-
LeonSauveterre 👍 3 Answered BA & C - Spot Instances are cost-effective but are subject to interruptions. "The solution must also reduce the manual tasks." B - AWS Batch is a fully managed service for batch processing, ideal for workloads like image processing. It scales automatically, handles job scheduling, and eliminates the need to manage infrastructure. Step Functions provides robust orchestration with built-in support for retries, error handling, and dependencies, reducing manual tasks in the workflow. D - Using EC2 instances requires managing the underlying infrastructure. Also, EBS is not as scalable or cost-effective as S3 when you want to store large, growing numbers of files.
-
Ell89 👍 1 Answered BB- because all other answers mention EC2 which goes against the company not wanting to manage the underlying infrastructure.
-
aragon_saa 👍 4 Answered BAnswer is B
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →