- A
The SageMaker overhead is causing the delay; check endpoint configuration
Why wrong: OverheadLatency is low, so overhead is not the issue.
- B
The model inference time is the bottleneck; consider optimizing the model or using a faster instance type
High ModelLatency indicates inference time is the issue.
- C
The endpoint is overloaded; increase the number of instances
Why wrong: High ModelLatency is not necessarily due to overload; it could be model slowness. Overload would manifest as increased 5XX errors or overall latency.
- D
The network latency is high; move the endpoint closer to clients
Why wrong: Network latency is not reflected in ModelLatency or OverheadLatency.
Question 779 of 1,000
MLA-C01 Practice Question: ML Solution Monitoring, Maintenance, and Security
This MLA-C01 practice question tests your understanding of ml solution monitoring, maintenance, and security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 data scientist deploys a model and wants to monitor the endpoint's invocation latency. They notice that the CloudWatch metric 'ModelLatency' is high, but 'OverheadLatency' is low. Which statement correctly interprets these metrics?
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 model inference time is the bottleneck; consider optimizing the model or using a faster instance type
The 'ModelLatency' metric measures the time taken by the SageMaker model container to process a single request, including inference and any preprocessing/postprocessing within the container. 'OverheadLatency' measures the time spent on SageMaker infrastructure (e.g., network I/O, request queuing, and response handling). When ModelLatency is high and OverheadLatency is low, the bottleneck is clearly the model inference time itself, not the infrastructure overhead. Therefore, optimizing the model (e.g., quantization, pruning) or upgrading to a faster instance type (e.g., GPU vs. CPU) is the correct remediation.
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.
- ✗
The SageMaker overhead is causing the delay; check endpoint configuration
Why it's wrong here
OverheadLatency is low, so overhead is not the issue.
- ✓
The model inference time is the bottleneck; consider optimizing the model or using a faster instance type
Why this is correct
High ModelLatency indicates inference time is the issue.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The endpoint is overloaded; increase the number of instances
Why it's wrong here
High ModelLatency is not necessarily due to overload; it could be model slowness. Overload would manifest as increased 5XX errors or overall latency.
- ✗
The network latency is high; move the endpoint closer to clients
Why it's wrong here
Network latency is not reflected in ModelLatency or OverheadLatency.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'ModelLatency' with overall endpoint latency and assume any high latency is due to infrastructure or scaling issues, when in fact the metric explicitly isolates the model's own inference time from overhead.
Detailed technical explanation
How to think about this question
Under the hood, ModelLatency is the sum of the time taken by the inference container's HTTP response (from receiving the request to sending the response), while OverheadLatency includes SageMaker's internal routing, load balancing, and response serialization. In real-world scenarios, a model with high computational complexity (e.g., large transformer models) can cause ModelLatency to spike even on powerful instances, while OverheadLatency remains low because the infrastructure is not saturated. This distinction is critical for cost optimization: upgrading instance type directly reduces ModelLatency, whereas scaling out instances only helps if OverheadLatency is the issue.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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.
- →
ML Solution Monitoring, Maintenance, and Security — study guide chapter
Learn the concepts, then practise the questions
- →
ML Solution Monitoring, Maintenance, and Security practice questions
Targeted practice on this topic area only
- →
All MLA-C01 questions
1,000 questions across all exam domains
- →
AWS Certified Machine Learning Engineer Associate MLA-C01 study guide
Full concept coverage aligned to exam objectives
- →
MLA-C01 practice test guide
How to use practice tests most effectively before exam day
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.
ML Model Development practice questions
Practise MLA-C01 questions linked to ML Model Development.
Data Preparation for Machine Learning practice questions
Practise MLA-C01 questions linked to Data Preparation for Machine Learning.
Deployment and Orchestration of ML Workflows practice questions
Practise MLA-C01 questions linked to Deployment and Orchestration of ML Workflows.
ML Solution Monitoring, Maintenance, and Security practice questions
Practise MLA-C01 questions linked to ML Solution Monitoring, Maintenance, and Security.
ML Solution Monitoring, Maintenance and Security practice questions
Practise MLA-C01 questions linked to ML Solution Monitoring, Maintenance and Security.
MLA-C01 fundamentals practice questions
Practise MLA-C01 questions linked to MLA-C01 fundamentals.
MLA-C01 scenario practice questions
Practise MLA-C01 questions linked to MLA-C01 scenario.
MLA-C01 troubleshooting practice questions
Practise MLA-C01 questions linked to MLA-C01 troubleshooting.
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?
ML Solution Monitoring, Maintenance, and Security — This question tests ML Solution Monitoring, Maintenance, and Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The model inference time is the bottleneck; consider optimizing the model or using a faster instance type — The 'ModelLatency' metric measures the time taken by the SageMaker model container to process a single request, including inference and any preprocessing/postprocessing within the container. 'OverheadLatency' measures the time spent on SageMaker infrastructure (e.g., network I/O, request queuing, and response handling). When ModelLatency is high and OverheadLatency is low, the bottleneck is clearly the model inference time itself, not the infrastructure overhead. Therefore, optimizing the model (e.g., quantization, pruning) or upgrading to a faster instance type (e.g., GPU vs. CPU) is the correct remediation.
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 →
Last reviewed: Jul 4, 2026
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.
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.
Sign in to join the discussion.