Auto-scaling inference endpoints in MLOps - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Auto-scaling Triggers

Which metric is most commonly used to trigger auto-scaling of inference endpoints in a cloud environment?

A Time of day

B Disk space usage

C Number of active users on the website

D CPU utilization percentage

💡 Hint

Think about what resource usage directly affects the ability to handle inference requests.

CPU utilization is a direct indicator of how busy the inference endpoint is. When CPU usage is high, scaling out helps handle more requests.

💻 Command Output

intermediate

Interpreting Auto-scaling CLI Output

Given the following CLI output from an auto-scaling tool monitoring an inference endpoint, what is the current number of active instances?

Endpoint: model-v1
Instances: 3
CPU Utilization: 75%
Scaling Status: Stable

A 3

B 75

C 1

D 0

💡 Hint

Look for the line that indicates how many instances are running.

The line 'Instances: 3' shows that there are currently 3 active instances serving the endpoint.

❓ Configuration

advanced

Configuring Auto-scaling Policy

Which YAML snippet correctly configures an auto-scaling policy to scale out when CPU usage exceeds 70% and scale in when below 30%?

A

autoScaling:
  minInstances: 1
  maxInstances: 5
  targetCPUUtilizationPercentage: 50

B

autoScaling:
  minInstances: 1
  maxInstances: 5
  cpuUtilization:
    scaleOut: 70
    scaleIn: 30

C

autoScaling:
  minInstances: 1
  maxInstances: 5
  scaleOutCPUThreshold: 70
  scaleInCPUThreshold: 30

D

autoScaling:
  minInstances: 1
  maxInstances: 5
  targetCPUUtilizationPercentage: 70

💡 Hint

Look for explicit scale out and scale in thresholds.

Option C explicitly sets scaleOutCPUThreshold and scaleInCPUThreshold, which are required to define when to scale out and in.

❓ Troubleshoot

advanced

Diagnosing Auto-scaling Failure

An inference endpoint is not scaling out despite high CPU usage. Which of the following is the most likely cause?

A The endpoint has no traffic

B The maxInstances limit is set to 1

C The CPU usage is below the scale-out threshold

D The auto-scaling feature is disabled in the cloud provider

💡 Hint

Check if the scaling limits allow more instances to be created.

If maxInstances is set to 1, the system cannot add more instances even if CPU usage is high, preventing scale out.

🔀 Workflow

expert

Auto-scaling Workflow for Inference Endpoint

Arrange the steps in the correct order for an auto-scaling workflow of an inference endpoint.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 1,2,4,3

💡 Hint

Think about monitoring first, then triggering, then adding instances, then routing traffic.

The workflow starts with monitoring metrics, then triggers scaling, adds instances, and finally distributes requests.

Practice

1. What is the main purpose of auto-scaling inference endpoints in ML services?

easy

A. To automatically adjust the number of servers based on traffic

B. To manually add servers when traffic increases

C. To reduce the accuracy of ML models during high traffic

D. To store more data for training models

Solution

1. Step 1: Understand auto-scaling concept

   Auto-scaling means the system changes the number of servers automatically depending on the traffic load.

2. Step 2: Identify the purpose in ML inference

   For ML inference endpoints, auto-scaling keeps the service fast and cost-efficient by adjusting servers without manual work.

3. Final Answer:

   To automatically adjust the number of servers based on traffic -> Option A

4. Quick Check:

   Auto-scaling = automatic server adjustment [OK]

Hint: Auto-scaling means automatic server count change [OK]

Common Mistakes:

• Thinking auto-scaling requires manual server changes
• Confusing auto-scaling with model accuracy changes
• Believing auto-scaling stores training data

2. Which configuration setting defines the minimum number of servers to keep running in an auto-scaling inference endpoint?

easy

A. max_servers

B. scale_up_threshold

C. target_utilization

D. min_servers

Solution

1. Step 1: Identify minimum server setting

   The minimum number of servers to keep running is controlled by the setting named min_servers.

2. Step 2: Differentiate from other settings

   max_servers sets the upper limit, target_utilization controls load target, and scale_up_threshold is not a standard setting here.

3. Final Answer:

   min_servers -> Option D

4. Quick Check:

   Minimum servers = min_servers [OK]

Hint: Min servers setting always starts with 'min_' [OK]

Common Mistakes:

• Confusing max_servers with minimum servers
• Mixing target utilization with server count
• Using non-existent settings like scale_up_threshold

3. Given this auto-scaling config snippet:

{
  "min_servers": 2,
  "max_servers": 5,
  "target_utilization": 0.7
}

If the current server usage is 80%, what will likely happen?

medium

A. The system will scale up servers to reduce load

B. The system will scale down servers to save cost

C. The system will keep the same number of servers

D. The system will shut down all servers

Solution

1. Step 1: Compare current usage to target utilization

   The current usage (80%) is higher than the target utilization (70%).

2. Step 2: Determine scaling action

   Since usage is above target, the system will add servers (scale up) to reduce load and meet the target.

3. Final Answer:

   The system will scale up servers to reduce load -> Option A

4. Quick Check:

   Usage > target = scale up [OK]

Hint: If usage > target, scale up servers [OK]

Common Mistakes:

• Scaling down when usage is above target
• Assuming no change if usage is slightly above target
• Thinking system shuts down servers automatically

4. You configured an auto-scaling endpoint with min_servers: 1 and max_servers: 3. The system never scales above 1 server even under high load. What is the most likely cause?

medium

A. The max_servers is set too low to allow scaling

B. The target utilization is set too high, preventing scale up

C. The min_servers value is incorrectly set to 3

D. The system does not support auto-scaling

Solution

1. Step 1: Analyze scaling limits

   Min servers is 1 and max servers is 3, so scaling up to 3 is allowed.

2. Step 2: Check target utilization impact

   If target utilization is set very high (e.g., 90%+), the system thinks current load is acceptable and won't scale up.

3. Final Answer:

   The target utilization is set too high, preventing scale up -> Option B

4. Quick Check:

   High target utilization blocks scaling up [OK]

Hint: High target utilization can block scaling up [OK]

Common Mistakes:

• Confusing max_servers as too low when it allows scaling
• Misreading min_servers as max_servers
• Assuming system lacks auto-scaling support

5. You want to configure an auto-scaling inference endpoint that never drops below 2 servers, never exceeds 6 servers, and aims to keep CPU usage around 60%. Which configuration is correct?

hard

A. { "min_servers": 2, "max_servers": 6, "target_utilization": 0.9 }

B. { "min_servers": 6, "max_servers": 2, "target_utilization": 0.6 }

C. { "min_servers": 2, "max_servers": 6, "target_utilization": 0.6 }

D. { "min_servers": 1, "max_servers": 6, "target_utilization": 0.6 }

Solution

1. Step 1: Set minimum and maximum servers correctly

   Minimum servers should be 2 and maximum servers 6, so min_servers: 2 and max_servers: 6 are correct.

2. Step 2: Set target utilization to 60%

   Target utilization should be 0.6 (60%) to keep CPU usage around that level.

3. Step 3: Verify options

   { "min_servers": 2, "max_servers": 6, "target_utilization": 0.6 } matches all requirements. { "min_servers": 6, "max_servers": 2, "target_utilization": 0.6 } reverses min and max servers. { "min_servers": 2, "max_servers": 6, "target_utilization": 0.9 } has wrong target utilization. { "min_servers": 1, "max_servers": 6, "target_utilization": 0.6 } has min_servers as 1, which is below requirement.

4. Final Answer:

   { "min_servers": 2, "max_servers": 6, "target_utilization": 0.6 } -> Option C

5. Quick Check:

   Correct min, max, and target utilization = { "min_servers": 2, "max_servers": 6, "target_utilization": 0.6 } [OK]

Hint: Min ≤ max and target_utilization as decimal (0.6) [OK]

Common Mistakes:

• Swapping min_servers and max_servers values
• Using target_utilization as percentage (60) instead of decimal (0.6)
• Setting min_servers lower than required