How to Make SageMaker Endpoint Auto Scaling Most Responsive?

MLA-C01 By islever Editorial Last updated

Select deployment infrastructure based on existing architecture and requirements. Monitor and optimize infrastructure and costs.

Short answer

D Use the SageMaker InvocationsPerInstance metric with high-resolution 10-second intervals and the default 300-second scale-in cooldown for the fastest target-tracking response.

Question

An airline company uses an ML model to adjust ticket prices based on demand. The model runs on Amazon SageMaker real-time endpoints. During previous deployments, the model failed to scale quickly enough when website traffic increased, which caused delays in price adjustments.
An ML engineer needs to configure auto scaling for the SageMaker endpoints to respond rapidly to traffic changes. The solution must use target tracking scaling policies.
Which configuration will be MOST responsive to sudden changes in traffic?
  1. Configure auto scaling based on the SageMaker AI InvocationsPerInstance standard metric. Configure 10-second interval resolution, and set the default 300-second scale-in cooldown period.
  2. Configure auto scaling based on the SageMaker AI InvocationsPerInstance metric. Configure high-resolution 10-second intervals, and set a 600-second scale-in cooldown period.
  3. Configure auto scaling based on the SageMaker InvocationsPerInstance standard metric. Configure 10-second intervals resolution, and set a 600-second scale-in cooldown period.
  4. Configure auto scaling based on the SageMaker InvocationsPerInstance metric. Configure high-resolution 10-second intervals, and set the default 300-second scale-in cooldown period. Correct Answer

Key Takeaways

Tests SageMaker endpoint target-tracking responsiveness; the trap is assuming a longer 600-second cooldown or standard-resolution metric improves reaction speed.

For a SageMaker real-time endpoint that must react quickly to traffic spikes, this page explains why high-resolution InvocationsPerInstance metrics and the shorter default scale-in cooldown are the most responsive target-tracking configuration.

Common mistake: Choosing the 600-second cooldown because it sounds safer; a longer scale-in cooldown works against the requirement for rapid response, and standard metrics do not deliver 10-second high-resolution evaluation.

Expert Analysis

Why the Answer Is Correct

D combines the two settings that make target tracking react fastest: the built-in InvocationsPerInstance metric evaluated at high-resolution 10-second intervals, and the default 300-second scale-in cooldown rather than 600 seconds. SageMaker endpoint auto scaling is driven by load per instance, so InvocationsPerInstance is the appropriate signal for a real-time pricing endpoint. High-resolution intervals let CloudWatch and Application Auto Scaling observe traffic spikes sooner than standard one-minute metrics. The shorter cooldown reduces the wait before the policy can take another scaling action, preserving responsiveness when demand is volatile.

Why the Other Options Are Wrong

A pairs a standard metric with 10-second interval resolution, which does not provide the high-resolution evaluation needed for the fastest response. C makes the same standard-metric mistake and adds a longer 600-second cooldown, making it less responsive than D. B does use high-resolution 10-second intervals, but its 600-second scale-in cooldown is slower than D's default 300-second cooldown. D is the only option that correctly combines high-resolution metric evaluation with the shorter cooldown.

Community Comment Notes

Two learners, 9502a22 and ChiggaBoy, picked D and highlighted the same tradeoff: "high-resolution metrics and the scale-in cooldown." 9502a22 summarized D as high-resolution intervals with a 300-second cooldown for fastest scale-in response. ChiggaBoy emphasized the phrase "MOST responsive to sudden changes in traffic." Billhardy supported A by focusing on the standard metric, but A's standard-resolution metric is not the high-resolution path needed for 10-second responsiveness; Chelseajcole only identified InvocationsPerInstance in B, which misses the shorter cooldown advantage.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Look for the two levers in SageMaker endpoint auto scaling questions: high-resolution metrics for faster detection and the shorter cooldown for faster follow-up scaling. Eliminate options that pair a 10-second interval with a standard-resolution metric or a longer 600-second cooldown.

Frequently Asked Questions

Why is the 600-second scale-in cooldown worse than the default 300 seconds?

A longer cooldown keeps the endpoint waiting longer before another scaling action, which reduces responsiveness when demand is volatile; 300 seconds supports faster adjustment.

Does SageMaker auto scaling support 10-second high-resolution metrics?

Yes. SageMaker endpoint target tracking can use high-resolution metrics at 10-second intervals, which detect traffic spikes sooner than standard one-minute metrics.

More MLA-C01 FAQ →

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. 9502a22 👍 2 Answered D
    D. High-resolution capability supports 10-second intervals Standard metric naming follows AWS conventions 300-second cooldown provides fastest scale-in response Maximum responsiveness for sudden traffic changes
  2. Billhardy 👍 1 Answered A
    The question asks for: Maximum responsiveness to sudden traffic spikes Target tracking scaling policies Rapid scaling for real‑time endpoints To achieve the fastest response: 1. Use InvocationsPerInstance standard metric This is the correct metric for SageMaker endpoint auto scaling because: It measures load per instance It is a standard, native, and recommended metric for scaling endpoints It directly reflects request traffic pressure CloudWatch high‑resolution metrics (10s) give faster scaling decisions, but the key point is using the standard metric rather than the AI namespace metric.
  3. ChiggaBoy 👍 1 Answered D
    Answer: D. The key is the wording “MOST responsive to sudden changes in traffic.” Two settings matter here: high-resolution metrics and the scale-in cooldown.
  4. Chelseajcole 👍 1 Answered B
    InvocationsPerInstance metric

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Choosing LightGBM in SageMaker for Fraud Detection with Class Imbalance and Correlated Features

S-grade

Processing Mixed CSV JSON XLSX Parquet Files in One S3 Folder with DataBrew and Outputting Apache Parquet

S-grade

Rebuilding the Model Monitor Baseline After a Model Update Causes Data Quality Violations

S-grade

Orchestrating SageMaker ML Workflows as DAGs in Studio with ML Lineage Tracking for Governance

S-grade

Practice All MLA-C01 Questions

Access 115 questions with complete answers and detailed explanations.

View Full MLA-C01 Practice Test →

← Back to MLA-C01 Study Guide