- A
The instances are under-provisioned; switch to ml.m5.xlarge instances.
Why wrong: Upscaling instances may help throughput but not necessarily per-request latency if the issue is input size.
- B
A recent change increased the average input size, causing longer inference time; investigate input preprocessing.
Larger inputs can increase inference latency significantly.
- C
The endpoint is experiencing too many concurrent requests; add more instances.
Why wrong: Concurrent requests cause queuing, but the symptom is per-request timeout, not consistently high latency.
- D
Model drift caused the model to become computationally heavier; retrain the model.
Why wrong: Model drift affects prediction accuracy, not computation time.
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. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 uses Amazon SageMaker to host a real-time inference endpoint for a fraud detection model. The endpoint is deployed with three instances of ml.m5.large. The model processes each request in about 200 ms. Lately, users report occasional timeouts (requests taking >5 seconds). The team suspects model drift or data skew. What is the MOST likely cause and solution?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
A recent change increased the average input size, causing longer inference time; investigate input preprocessing.
Option B is correct because the symptom of occasional timeouts (>5 seconds) on a model that normally processes requests in ~200 ms suggests that a recent change in input data characteristics (e.g., larger payloads or more complex features) is causing sporadic latency spikes. Investigating input preprocessing can identify if data skew or increased input size is overwhelming the model's inference path, which is a common monitoring concern in SageMaker real-time endpoints.
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 instances are under-provisioned; switch to ml.m5.xlarge instances.
Why it's wrong here
Upscaling instances may help throughput but not necessarily per-request latency if the issue is input size.
- ✓
A recent change increased the average input size, causing longer inference time; investigate input preprocessing.
Why this is correct
Larger inputs can increase inference latency significantly.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The endpoint is experiencing too many concurrent requests; add more instances.
Why it's wrong here
Concurrent requests cause queuing, but the symptom is per-request timeout, not consistently high latency.
- ✗
Model drift caused the model to become computationally heavier; retrain the model.
Why it's wrong here
Model drift affects prediction accuracy, not computation time.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse model drift (accuracy degradation) with performance degradation (latency increase), leading them to choose retraining (Option D) instead of investigating input preprocessing changes.
Detailed technical explanation
How to think about this question
SageMaker real-time endpoints use synchronous inference, where each request must complete within the endpoint's configured invocation timeout (default 60 seconds, but user-reported 5-second timeouts suggest a custom timeout or client-side cutoff). Input preprocessing steps, such as feature engineering or data transformation, run inside the inference container and can become a bottleneck if input payloads grow (e.g., from 1 KB to 100 KB), causing the 200 ms baseline to spike unpredictably. Monitoring SageMaker endpoint metrics like ModelLatency and OverheadLatency can help isolate whether the delay is in the model itself or in preprocessing.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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
507 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.
Data Preparation for Machine Learning practice questions
Practise MLA-C01 questions linked to Data Preparation for Machine Learning.
ML Model Development practice questions
Practise MLA-C01 questions linked to ML Model Development.
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.
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: A recent change increased the average input size, causing longer inference time; investigate input preprocessing. — Option B is correct because the symptom of occasional timeouts (>5 seconds) on a model that normally processes requests in ~200 ms suggests that a recent change in input data characteristics (e.g., larger payloads or more complex features) is causing sporadic latency spikes. Investigating input preprocessing can identify if data skew or increased input size is overwhelming the model's inference path, which is a common monitoring concern in SageMaker real-time endpoints.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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: Jun 24, 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.