SageMaker Batch Transform with Spot Instances: Optimal for Large Batch Inference
A company runs a batch inference job on 10 TB of image data stored in S3. Each image needs to be processed by a GPU-accelerated model. The job is not time-sensitive and cost is the primary concern. Which SageMaker option is MOST appropriate?
Quick Answer
Two details in this scenario point directly at the answer: the job is not time-sensitive, meaning there's no requirement for an always-on, low-latency serving layer, and cost is the primary concern, meaning the cheapest way to get the compute done should win as long as it still finishes the job. SageMaker Batch Transform is designed for exactly this kind of large-scale, non-interactive inference, since it processes a whole dataset from S3 in one job, automatically splitting and distributing the work, without requiring a persistent endpoint that would sit around incurring cost even when idle. Pairing it with spot instances is what captures the cost savings, since spot capacity can be dramatically cheaper than on-demand pricing, and because the job isn't time-sensitive, the possibility of spot interruptions and retries is an acceptable tradeoff rather than a risk to a latency-sensitive workload. This is a better fit than a real-time endpoint, which would keep GPU instances running continuously regardless of demand, or an on-demand batch job, which would work but leave cost savings on the table. Whenever a scenario emphasizes large volume, no urgency, and cost as the deciding factor for inference on data already sitting in S3, Batch Transform combined with spot instances is the pattern to reach for.
⚠ Common exam trap
Many candidates confuse 'batch inference' with 'async inference' and choose Option C, not realizing that Async Inference still requires a running endpoint and is designed for near-real-time processing, not cost-optimized offline batch jobs.
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
✓
SageMaker Batch Transform with GPU instance and spot instances
Batch Transform with GPU spot instances is the most cost-effective choice for a non-time-sensitive, large-scale batch inference job on 10 TB of data. Spot instances offer up to 90% cost savings over on-demand, and Batch Transform natively handles splitting the dataset, distributing work across instances, and writing results to S3 without requiring a persistent endpoint.
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 MLA-C01 question is part of Courseiva's 835-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 →
Same concept, more angles
2 more ways this is tested on MLA-C01
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. A company wants to deploy a trained XGBoost model for batch inference on a large dataset stored in S3. The inference job should be cost-effective and does not require real-time responses. Which SageMaker inference option should they use?
easy- ✓ A.SageMaker Batch Transform
- B.SageMaker real-time endpoint
- C.SageMaker Asynchronous Inference
- D.SageMaker Serverless Inference
Why A: SageMaker Batch Transform is designed for batch inference on large datasets stored in S3, processing data in chunks and writing results to S3. It is cost-effective for non-real-time scenarios. Real-time endpoints are for low-latency inference. Serverless is for on-demand, not batch. Asynchronous is for near-real-time with S3 input/output but still not ideal for large batch jobs.
Variation 2. A company wants to run inference on a large dataset stored in S3 using a pre-trained model. The inference can tolerate latency from minutes to hours, and they want a fully managed solution that autoscales to handle large volumes. Which SageMaker inference option is most suitable?
medium- ✓ A.Batch transform
- B.Real-time endpoint
- C.Asynchronous inference
- D.Serverless inference
Why A: Batch transform is the most suitable option because the company needs to run inference on a large dataset stored in S3 with latency tolerance from minutes to hours, and requires a fully managed, autoscaling solution. SageMaker Batch Transform processes the entire dataset as a single job, automatically provisions and scales compute resources, and writes results back to S3 without the need for persistent endpoints.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.