- A
The evaluation step did not produce the output correctly.
Why wrong: The evaluation step produced the output with key 'accuracy' as expected.
- B
The training step output is being used instead of the evaluation step output.
Why wrong: Even if that were the case, the property name mismatch would still cause the error.
- C
The pipeline definition has a syntax error.
Why wrong: The error message points to a missing property, not a syntax error.
- D
The Condition step is referencing the wrong property name.
Correct: 'Accuracy' vs 'accuracy' case mismatch causes the error.
Question 518 of 1,000
hardMultiple ChoiceObjective-mapped
MLA-C01 Practice Question: A team is using SageMaker Pipelines to train a…
This MLA-C01 practice question tests your understanding of mla-c01 exam topics. 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 team is using SageMaker Pipelines to train a model. The pipeline has multiple steps: data processing, training, evaluation, and registration. They use a Condition step to evaluate the model's accuracy and if it exceeds a threshold, register the model. They run the pipeline and the training step succeeds, but the pipeline fails at the Condition step with an error: 'Unable to evaluate condition: the property 'Accuracy' does not exist.' The evaluation step output is a JSON file with key 'accuracy'. What is the most likely cause?
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
✓
The Condition step is referencing the wrong property name.
The Condition step in SageMaker Pipelines evaluates a property from the output of a previous step. The error 'Unable to evaluate condition: the property 'Accuracy' does not exist' indicates that the Condition step is looking for a property named 'Accuracy' (capital A), but the evaluation step outputs a JSON file with the key 'accuracy' (lowercase a). This mismatch in property name casing causes the condition to fail, even though the evaluation step produced the correct output.
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 evaluation step did not produce the output correctly.
Why it's wrong here
The evaluation step produced the output with key 'accuracy' as expected.
- ✗
The training step output is being used instead of the evaluation step output.
Why it's wrong here
Even if that were the case, the property name mismatch would still cause the error.
- ✗
The pipeline definition has a syntax error.
Why it's wrong here
The error message points to a missing property, not a syntax error.
- ✓
The Condition step is referencing the wrong property name.
Why this is correct
Correct: 'Accuracy' vs 'accuracy' case mismatch causes the error.
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
AWS often tests the subtlety of case sensitivity in property names when referencing step outputs in SageMaker Pipelines, leading candidates to incorrectly assume the evaluation step failed or that the pipeline definition has a syntax error.
Trap categories for this question
Command / output trap
The evaluation step produced the output with key 'accuracy' as expected.
Detailed technical explanation
How to think about this question
SageMaker Pipelines uses JSONPaths to reference properties from step outputs in Condition steps. The property name is case-sensitive and must exactly match the key in the output JSON. For example, if the evaluation step writes {'accuracy': 0.95}, the Condition step must reference 'accuracy' (lowercase), not 'Accuracy' (capitalized). This is a common pitfall when using Python dictionaries or JSON files where key naming conventions (e.g., camelCase vs. snake_case) differ from the pipeline definition.
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.
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?
Read the scenario before looking for a memorised answer.
What is the correct answer to this question?
The correct answer is: The Condition step is referencing the wrong property name. — The Condition step in SageMaker Pipelines evaluates a property from the output of a previous step. The error 'Unable to evaluate condition: the property 'Accuracy' does not exist' indicates that the Condition step is looking for a property named 'Accuracy' (capital A), but the evaluation step outputs a JSON file with the key 'accuracy' (lowercase a). This mismatch in property name casing causes the condition to fail, even though the evaluation step produced the correct output.
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 →
Keep practising
More MLA-C01 practice questions
- A machine learning team deploys a custom container image for an Amazon SageMaker training job. The container needs to ac…
- A machine learning engineer sees the above error in Amazon CloudWatch Logs for a SageMaker endpoint. What is the most li…
- A data scientist has trained a model that achieves 95% accuracy on the training set but only 70% on the test set. Which…
- Refer to the exhibit. A data scientist reviews the output of a SageMaker training job. The model has 95% training accura…
- A team is using Amazon SageMaker to train a neural network. They want to minimize training time while effectively explor…
- Which TWO of the following are best practices for deploying machine learning models on SageMaker? (Select TWO.)
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.