AIF-C01 Fundamentals of AI and ML Practice Question
This AIF-C01 practice question tests your understanding of fundamentals of ai and ml. 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.
Exhibit
Refer to the exhibit: CloudWatch Logs excerpt from a SageMaker real-time endpoint with instance type ml.m5.large. Average inference time is 500ms but increases over time. Logs show repeated 'MemoryError: cannot allocate memory' after several hours of operation.
Refer to the exhibit. A SageMaker real-time endpoint is experiencing increasing latency and memory errors after running for a few hours. What is the most likely cause and recommended fix?
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.
Refer to the exhibit: CloudWatch Logs excerpt from a SageMaker real-time endpoint with instance type ml.m5.large. Average inference time is 500ms but increases over time. Logs show repeated 'MemoryError: cannot allocate memory' after several hours of operation.
A
Scale the endpoint to a larger instance type, such as ml.r5.large
Why wrong: A larger instance provides more memory but does not fix the underlying leak; the error will recur.
B
Enable auto-scaling to add instances during high load
Why wrong: Auto-scaling handles traffic, not memory leaks within the code.
C
Use SageMaker Debugger to identify and fix a memory leak in the inference code
The increasing memory usage over time indicates a leak; Debugger can help identify the issue.
D
Use SageMaker Model Monitor to detect data drift
Why wrong: Model Monitor detects changes in input distribution, not memory issues.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use SageMaker Debugger to identify and fix a memory leak in the inference code
Option C is correct because the symptoms—increasing latency and memory errors after running for a few hours—point to a memory leak in the inference code. SageMaker Debugger can monitor system metrics like memory utilization and detect anomalies, helping to identify the root cause of the leak. Fixing the memory leak directly resolves the progressive degradation, whereas scaling or auto-scaling only masks the symptom.
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.
✗
Scale the endpoint to a larger instance type, such as ml.r5.large
Why it's wrong here
A larger instance provides more memory but does not fix the underlying leak; the error will recur.
✗
Enable auto-scaling to add instances during high load
Why it's wrong here
Auto-scaling handles traffic, not memory leaks within the code.
✓
Use SageMaker Debugger to identify and fix a memory leak in the inference code
Why this is correct
The increasing memory usage over time indicates a leak; Debugger can help identify the issue.
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.
✗
Use SageMaker Model Monitor to detect data drift
Why it's wrong here
Model Monitor detects changes in input distribution, not memory issues.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between scaling solutions (which address capacity) and debugging tools (which address code defects), trapping candidates who confuse symptom relief with root cause resolution.
Detailed technical explanation
How to think about this question
A memory leak in inference code occurs when objects are not properly garbage-collected after each prediction request, causing heap memory to grow over time. SageMaker Debugger can capture framework metrics (e.g., PyTorch or TensorFlow memory allocator stats) and system metrics (e.g., resident set size) to pinpoint the leak. In a real-world scenario, a common cause is caching prediction results or model weights without eviction logic, leading to unbounded memory growth.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
Fundamentals of AI and ML — This question tests Fundamentals of AI and ML — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use SageMaker Debugger to identify and fix a memory leak in the inference code — Option C is correct because the symptoms—increasing latency and memory errors after running for a few hours—point to a memory leak in the inference code. SageMaker Debugger can monitor system metrics like memory utilization and detect anomalies, helping to identify the root cause of the leak. Fixing the memory leak directly resolves the progressive degradation, whereas scaling or auto-scaling only masks the symptom.
What should I do if I get this AIF-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 →
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.
This AIF-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 AIF-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.