The answer is that NX-API returns all values as strings in JSON output, causing type mismatches when scripts enforce strict type checking. This occurs because the Nexus 9000 serializes every field—including numeric VLAN IDs—as a string, so comparing the string '100' to an integer 100 with a strict equality operator like `===` in Python or JavaScript will always fail, even when the configuration is correct. On the Cisco DCCOR / CCNP Data Center Core 350-601 exam, this tests your understanding of NX-API behavior and automation pitfalls, often appearing in troubleshooting scenarios where a seemingly valid script reports failure. The common trap is assuming JSON preserves native data types, but NX-API does not—you must explicitly convert strings to integers before comparison. Memory tip: "NX-API strings everything—convert before you compare."
350-601 Automation Practice Question
This 350-601 practice question tests your understanding of automation. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
Refer to the exhibit. An automation script queries the Cisco Nexus 9000 using the NX-API JSON format and receives the above output. The script is designed to validate that interface Eth1/1 is in access mode with VLAN 100. However, the script reports a failure. What is the most likely reason?
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 the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The script uses strict type checking, and the values are returned as strings instead of integers.
The NX-API returns all values as strings in JSON output, including numeric fields like VLANIDs. If the script uses strict type checking (e.g., `===` in Python or JavaScript), comparing the string '100' to the integer 100 will fail, even though the interface is correctly configured in access mode with VLAN 100. This is a common pitfall when parsing NX-API responses without explicit type conversion.
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 script uses strict type checking, and the values are returned as strings instead of integers.
Why this is correct
JSON returns numbers as strings in this context; a type mismatch causes failure.
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 JSON output is malformed and cannot be parsed.
The JSON output is missing the 'switchportMode' field.
Why it's wrong here
The output includes 'switchportMode'.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the nuance that NX-API returns all values as strings, tricking candidates who assume numeric fields are returned as integers and overlook the need for type conversion in validation logic.
Trap categories for this question
Command / output trap
The output shows 'adminSt': 'up'.
Detailed technical explanation
How to think about this question
The NX-API on Cisco Nexus 9000 series switches serializes all data as strings in JSON-RPC responses, even for numeric or boolean fields. This behavior is documented in Cisco's NX-API Developer Guide; for example, VLANIDs, port-channel numbers, and counters are always returned as strings. When automating validation scripts, developers must explicitly cast these string values to integers (e.g., `int(vlan)`) before comparison to avoid false failures in strict type-checking environments.
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 help-desk technician troubleshoots why a newly connected PC cannot reach shared printers on the same floor. The cable is good, the switch port is active, but the PC is in VLAN 20 and the printers are in VLAN 10. The uplink trunk only allows VLAN 10. A trunk being up does not mean every VLAN crosses it.
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.
Automation — This question tests Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The script uses strict type checking, and the values are returned as strings instead of integers. — The NX-API returns all values as strings in JSON output, including numeric fields like VLAN IDs. If the script uses strict type checking (e.g., `===` in Python or JavaScript), comparing the string '100' to the integer 100 will fail, even though the interface is correctly configured in access mode with VLAN 100. This is a common pitfall when parsing NX-API responses without explicit type conversion.
What should I do if I get this 350-601 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 350-601 practice question is part of Courseiva's free Cisco 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 350-601 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.