Question 406 of 1,755
Machine Learning Implementation and OperationshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the scaling policy is missing a cooldown period or the cooldown period is set too long. SageMaker’s auto scaling cooldown period acts as a mandatory stabilization window—defaulting to 300 seconds—that prevents the scaling policy from triggering new adjustments until the previous scaling activity has fully taken effect. Without this cooldown, or if it is excessively long, the policy will simply not activate, even when the SageMakerVariantInvocationsPerInstance metric correctly reports high load. On the AWS Certified Machine Learning Specialty MLS-C01 exam, this concept tests your understanding that auto scaling policies are not purely metric-driven; they require explicit cooldown configuration to avoid thrashing. A common trap is assuming the metric alone is sufficient or that a scheduled action is needed—neither is true. Remember the mnemonic: “No cooldown, no action—the policy needs a pause to pass.”

MLS-C01 Practice Question: Machine Learning Implementation and Operations

This MLS-C01 practice question tests your understanding of machine learning implementation and operations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 machine learning engineer is deploying a model using SageMaker and wants to use automatic scaling for the endpoint based on the number of concurrent requests. The engineer has defined a scaling policy using the SageMakerVariantInvocationsPerInstance metric. However, the scaling is not triggering as expected. What could be the issue?

Question 1hardmultiple choice
Full question →

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

The scaling policy does not have a cooldown period configured, or the cooldown period is too long.

Option D is correct because scaling policies require a cooldown period (default 300 seconds) to prevent rapid scaling. Without it, the policy may not activate. Option A is wrong because the metric is valid. Option B is wrong because the metric is emitted by default. Option C is wrong because scaling policy can be defined without a scheduled action.

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.

  • A scheduled scaling action must be created first.

    Why it's wrong here

    Not required for target tracking.

  • The scaling policy does not have a cooldown period configured, or the cooldown period is too long.

    Why this is correct

    Cooldown prevents scaling actions from triggering too frequently.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The metric must be published to CloudWatch manually.

    Why it's wrong here

    It is emitted automatically.

  • The metric is not available for automatic scaling.

    Why it's wrong here

    SageMakerVariantInvocationsPerInstance is valid.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Detailed technical explanation

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which MLS-C01 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

Related practice questions

Related MLS-C01 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free MLS-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 MLS-C01 question test?

Machine Learning Implementation and Operations — This question tests Machine Learning Implementation and Operations — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The scaling policy does not have a cooldown period configured, or the cooldown period is too long. — Option D is correct because scaling policies require a cooldown period (default 300 seconds) to prevent rapid scaling. Without it, the policy may not activate. Option A is wrong because the metric is valid. Option B is wrong because the metric is emitted by default. Option C is wrong because scaling policy can be defined without a scheduled action.

What should I do if I get this MLS-C01 question wrong?

Identify which MLS-C01 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 20, 2026

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.

Loading comments…

Sign in to join the discussion.

This MLS-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 MLS-C01 exam.