- A
Simple scaling policy
Why wrong: Simple scaling requires manual configuration of alarm thresholds.
- B
Scheduled scaling policy
Why wrong: Scheduled scaling is for predictable traffic patterns, not spikes.
- C
Target tracking policy
Target tracking automatically adjusts capacity to maintain a target metric value.
- D
Step scaling policy
Why wrong: Step scaling is more complex but can be used; target tracking is simpler and recommended.
Quick Answer
The answer is a target tracking scaling policy. This is the correct choice because it automatically adjusts the number of instances in your SageMaker endpoint based on a target metric like InvocationsPerInstance or ModelLatency, dynamically scaling resources up or down to maintain that target without manual intervention. For a model with a large memory footprint handling real-time predictions, this policy is ideal because it proactively adds capacity during traffic spikes while avoiding over-provisioning during lulls, ensuring consistent performance and cost efficiency. On the AWS Certified Machine Learning Engineer Associate MLA-C01 exam, this concept tests your understanding of automatic scaling for real-time inference endpoints, often appearing as a scenario where you must choose between simple, step, and target tracking policies. A common trap is selecting a step scaling policy, which requires predefined thresholds and can lag behind sudden bursts, whereas target tracking continuously adjusts based on a live metric. Memory tip: think “track the target, don’t step on the spikes.”
MLA-C01 Deployment and Orchestration of ML Workflows Practice Question
This MLA-C01 practice question tests your understanding of deployment and orchestration of ml workflows. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 wants to use SageMaker to serve real-time predictions with a model that has a large memory footprint. They need to ensure the endpoint can handle traffic spikes. Which scaling policy should they use?
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
Target tracking policy
Target tracking scaling policy is the correct choice because it automatically adjusts the number of instances in the SageMaker endpoint based on a target metric, such as InvocationsPerInstance or ModelLatency, to handle traffic spikes without manual intervention. This policy is ideal for real-time inference with large memory models because it dynamically scales resources up or down to maintain the target metric, ensuring consistent performance during unpredictable traffic bursts.
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.
- ✗
Simple scaling policy
Why it's wrong here
Simple scaling requires manual configuration of alarm thresholds.
- ✗
Scheduled scaling policy
Why it's wrong here
Scheduled scaling is for predictable traffic patterns, not spikes.
- ✓
Target tracking policy
Why this is correct
Target tracking automatically adjusts capacity to maintain a target metric value.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Step scaling policy
Why it's wrong here
Step scaling is more complex but can be used; target tracking is simpler and recommended.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse step scaling with target tracking, assuming step scaling is more responsive for spikes, but target tracking is actually the recommended and simpler approach for handling unpredictable traffic in SageMaker real-time endpoints.
Detailed technical explanation
How to think about this question
Target tracking scaling in SageMaker uses a built-in or custom CloudWatch metric (e.g., SageMakerVariantInvocationsPerInstance) and automatically creates the necessary CloudWatch alarms and scaling adjustments to keep the metric close to the target value. Under the hood, it applies a proportional-integral-derivative (PID) control algorithm to smooth out scaling actions, preventing oscillations that can occur with step scaling. In real-world scenarios, for a large memory model like a transformer with billions of parameters, target tracking ensures that the endpoint scales out quickly when invocations spike, while also scaling in during low traffic to minimize costs.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
- →
Deployment and Orchestration of ML Workflows — study guide chapter
Learn the concepts, then practise the questions
- →
Deployment and Orchestration of ML Workflows practice questions
Targeted practice on this topic area only
- →
All MLA-C01 questions
507 questions across all exam domains
- →
AWS Certified Machine Learning Engineer Associate MLA-C01 study guide
Full concept coverage aligned to exam objectives
- →
MLA-C01 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related MLA-C01 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Data Preparation for Machine Learning practice questions
Practise MLA-C01 questions linked to Data Preparation for Machine Learning.
ML Model Development practice questions
Practise MLA-C01 questions linked to ML Model Development.
Deployment and Orchestration of ML Workflows practice questions
Practise MLA-C01 questions linked to Deployment and Orchestration of ML Workflows.
ML Solution Monitoring, Maintenance and Security practice questions
Practise MLA-C01 questions linked to ML Solution Monitoring, Maintenance and Security.
MLA-C01 fundamentals practice questions
Practise MLA-C01 questions linked to MLA-C01 fundamentals.
MLA-C01 scenario practice questions
Practise MLA-C01 questions linked to MLA-C01 scenario.
MLA-C01 troubleshooting practice questions
Practise MLA-C01 questions linked to MLA-C01 troubleshooting.
Practice this exam
Start a free MLA-C01 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this MLA-C01 question test?
Deployment and Orchestration of ML Workflows — This question tests Deployment and Orchestration of ML Workflows — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Target tracking policy — Target tracking scaling policy is the correct choice because it automatically adjusts the number of instances in the SageMaker endpoint based on a target metric, such as InvocationsPerInstance or ModelLatency, to handle traffic spikes without manual intervention. This policy is ideal for real-time inference with large memory models because it dynamically scales resources up or down to maintain the target metric, ensuring consistent performance during unpredictable traffic bursts.
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 →
Last reviewed: Jun 24, 2026
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.