Question 320 of 507
Deployment and Orchestration of ML WorkflowshardMultiple ChoiceObjective-mapped

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 deploys a model using SageMaker real-time endpoint with auto scaling. They observe that during a traffic spike, the endpoint quickly scales up to 10 instances, but after the spike, it takes a long time to scale down, leading to high costs. The scaling policy is based on a simple average CPU utilization threshold. Which adjustment would optimize the scaling down behavior?

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

Decrease the scale-in cooldown period to allow the endpoint to scale down faster when utilization drops.

The correct answer is B because decreasing the scale-in cooldown period allows the endpoint to respond more quickly to sustained drops in CPU utilization. By default, SageMaker auto scaling uses cooldown periods to prevent rapid fluctuations; a long scale-in cooldown delays the termination of instances after utilization falls, keeping costs high. Reducing this cooldown lets the endpoint scale down faster when the spike subsides, directly addressing the problem.

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.

  • Increase the scale-in cooldown period to prevent premature scale-down.

    Why it's wrong here

    Increasing cooldown would make scaling down even slower.

  • Decrease the scale-in cooldown period to allow the endpoint to scale down faster when utilization drops.

    Why this is correct

    Reducing cooldown enables the Auto Scaling group to remove instances sooner.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use a step scaling policy with a larger step adjustment for scale-in.

    Why it's wrong here

    Step scaling can help but the cooldown period is the main issue.

  • Change the scaling policy to use memory utilization instead of CPU.

    Why it's wrong here

    Changing metric may not address the cooldown delay.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse cooldown periods with step adjustments, thinking that larger scale-in steps will speed up the process, when in fact the cooldown period controls the timing of when scaling actions can occur.

Detailed technical explanation

How to think about this question

Under the hood, SageMaker auto scaling uses the Application Auto Scaling service, which applies cooldown periods to prevent thrashing. The scale-in cooldown period (default 300 seconds) is the time after a scale-in activity during which further scale-in activities are blocked. In real-world scenarios, a bursty workload (e.g., inference requests from a flash sale) can cause rapid scaling up, but if the cooldown is too long, idle instances remain running for minutes, incurring unnecessary costs. Tuning this value to match the typical duration of traffic spikes (e.g., 60 seconds) optimizes cost without sacrificing availability.

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

A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

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.

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.

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: Decrease the scale-in cooldown period to allow the endpoint to scale down faster when utilization drops. — The correct answer is B because decreasing the scale-in cooldown period allows the endpoint to respond more quickly to sustained drops in CPU utilization. By default, SageMaker auto scaling uses cooldown periods to prevent rapid fluctuations; a long scale-in cooldown delays the termination of instances after utilization falls, keeping costs high. Reducing this cooldown lets the endpoint scale down faster when the spike subsides, directly addressing the problem.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More MLA-C01 practice questions

Last reviewed: Jun 24, 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 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.