mediumMultiple ChoiceObjective-mapped
MLA-C01 Practice Question: A media company uses SageMaker endpoints to serve…
A media company uses SageMaker endpoints to serve a model that predicts video engagement. They have two production variants: Variant A (ml.c5.large) for regular traffic and Variant B (ml.c5.xlarge) for burst traffic. They use weighted routing (90% to A, 10% to B). Recently, during peak hours, Variant A's latency increase causes many requests to time out. The metrics show that both variants are under similar CPU load, but the number of concurrent requests to Variant A is very high. The team wants to ensure that burst traffic is handled properly without manual intervention. What should they do?
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
✓
Configure Application Auto Scaling for each variant with a target tracking scaling policy based on the number of concurrent requests per instance.
Changing to target tracking scaling based on the number of concurrent requests (or InvocationsPerInstance) ensures each variant scales based on its load. Option A (swap weights) doesn't fix scaling. Option C (p99 latency alarm) might trigger too late. Option D (separate endpoint) is not necessary.
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 traffic weight to Variant B to 70% and reduce Variant A to 30%.
Why it's wrong here
This doesn't solve the root cause of Variant A being overloaded; it might overload B.
- ✓
Configure Application Auto Scaling for each variant with a target tracking scaling policy based on the number of concurrent requests per instance.
Why this is correct
Autoscaling adjusts capacity based on load, preventing timeouts.
- ✗
Set a CloudWatch alarm on Variant A's p99 latency and trigger a step scaling policy to add instances.
Why it's wrong here
Step scaling based on alarm may be reactive; target tracking is more proactive.
- ✗
Create a separate endpoint for burst traffic and route peak traffic to it via DNS.
Why it's wrong here
Separate endpoint adds complexity; scaling within the same endpoint is preferred.
Go deeper
Related to this question
About these practice questions
Courseiva writes every MLA-C01 question from scratch — 835 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.