Courseiva
ModelingeasyMultiple ChoiceObjective-mapped

SageMaker Endpoint Scaling — Troubleshooting InService Status with Lower Capacity

Network Topology
aws sagemaker describe-endpointendpoint-name my-endpointRefer to the exhibit."EndpointStatus": "InService","ProductionVariants": ["VariantName": "variant-1","CurrentInstanceCount": 2,"DesiredInstanceCount": 5,"CurrentWeight": 0.5,"DesiredWeight": 0.5

Refer to the exhibit. A data scientist checks the status of a SageMaker endpoint and sees the output above. The endpoint is receiving traffic, but the data scientist notices that the number of instances has not increased to the desired count. What is the most likely reason?

Quick Answer

The answer is that automatic scaling is not configured for the endpoint. This is the most likely reason because a SageMaker endpoint without an Application Auto Scaling policy will stubbornly remain at its initial instance count, even under heavy traffic load—the service simply has no instruction to add instances. On the AWS Certified Machine Learning Specialty MLS-C01 exam, this scenario tests your understanding of the difference between endpoint status (InService) and scaling behavior; a common trap is assuming a healthy status means scaling is active. Remember, an endpoint can be InService and still fail to scale if no scaling policy is attached. Memory tip: InService does not mean AutoScale—if you see traffic but no growth, check the scaling policy first.

⚠ Common exam trap

AWS often tests the distinction between endpoint status (e.g., 'InService' vs. 'Updating') and scaling configuration, trapping candidates who assume that any traffic increase automatically triggers scaling without an explicit scaling policy.

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

Automatic scaling is not configured for the endpoint

The endpoint is receiving traffic but not scaling out, which indicates that automatic scaling (Application Auto Scaling) has not been configured for the SageMaker endpoint. Without a scaling policy, the endpoint will only use the initial instance count, regardless of traffic load. The status shown does not indicate any update or quota issue, so the lack of scaling is the most likely cause.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The endpoint is performing a rolling update

    Why it's wrong here

    No evidence of rolling update; status is InService.

  • The endpoint is currently being updated

    Why it's wrong here

    The status is InService, not Updating.

  • The account has reached its instance limit

    Why it's wrong here

    If limit exceeded, the endpoint status would show a failure.

  • Automatic scaling is not configured for the endpoint

    Why this is correct

    The desired instance count will not be applied automatically without a scaling policy; it's just a target.

About these practice questions

One of 1,672 original MLS-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on MLS-C01

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Refer to the exhibit. A data scientist checks the status of a SageMaker endpoint and sees the output above. What does this indicate?

easy
  • A.The endpoint has failed
  • B.The endpoint is running at full capacity
  • C.The endpoint is out of service
  • D.The endpoint is scaling up to meet desired capacity

Why D: The endpoint shows InService status with current instance count (2) less than desired count (5), indicating it is scaling up to meet desired capacity. Option D correctly describes this state. Option A is wrong because the status is InService, not OutOfService. Option B is incorrect because the endpoint is not at full capacity; it is under-provisioned. Option C is wrong because the endpoint is operational, not failed.

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.