Quick Answer
The answer is a malformed request payload. HTTP 400 specifically indicates a bad request, meaning the NX-API on the Nexus 9000 received the HTTP call from Python’s requests library but rejected the content because the JSON or XML payload did not match the expected schema. Common culprits include missing required fields like 'ins_api' version, 'type', or 'input', incorrect JSON syntax, or invalid parameter values. On the Cisco DCCOR 350-601 exam, this question tests your ability to distinguish between transport-layer errors (like a 404 or timeout) and application-layer errors (like a 400), which is critical for data center automation troubleshooting. A frequent trap is assuming a 400 error means the switch is unreachable or the credentials are wrong—but those would produce different HTTP status codes. Memory tip: think “400 = bad format, not bad connection.”
This 350-601 practice question tests your understanding of automation. 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 center automation script uses Python's requests library to call the NX-API for a Nexus 9000 switch. The script works but returns HTTP 400. Which is a likely cause?
The request payload is malformed
400 Bad Request is client error.
The switch has no management IP
Why wrong: Would cause connection timeout.
The script uses HTTP instead of HTTPS
Why wrong: Would likely return a redirect or 301.
The API is not enabled
Why wrong: Would return 404 or 401.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The request payload is malformed
HTTP 400 indicates a bad request, which in the context of NX-API typically means the JSON or XML payload sent to the switch does not conform to the expected schema. Common issues include missing required fields (e.g., 'ins_api' version, 'type', 'chunk', 'sid', 'input', 'outputformat'), incorrect JSON syntax, or invalid values for parameters like 'version' or 'type'. The requests library successfully delivered the HTTP request, but the NX-API rejected it due to malformed content.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
The request payload is malformed
Why this is correct
400 Bad Request is client error.
Related concept
Read the scenario before looking for a memorised answer.
The switch has no management IP
Why it's wrong here
Would cause connection timeout.
The script uses HTTP instead of HTTPS
Why it's wrong here
Would likely return a redirect or 301.
The API is not enabled
Why it's wrong here
Would return 404 or 401.
Common exam traps
Cisco often tests the distinction between HTTP status codes (400 vs. 404 vs. connection errors) to see if candidates understand that a 400 specifically points to payload issues, not network or configuration problems.
Detailed technical explanation
NX-API on Nexus 9000 uses a REST-like interface over HTTP/HTTPS, expecting a JSON payload with a specific structure defined by Cisco's 'ins_api' schema. A common subtlety is that the 'version' field must match the switch's NX-API version (e.g., 1.0 or 1.2), and the 'type' field must be 'cli_show' or 'cli_show_ascii' for show commands; using an incorrect type or omitting the 'input' field triggers a 400. In real-world automation, this often occurs when copying payloads from documentation without adjusting for the switch's exact NX-OS version.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the 350-601 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Automation — study guide chapter
Learn the concepts, then practise the questions
Automation practice questions
Targeted practice on this topic area only
All 350-601 questions
500 questions across all exam domains
Cisco DCCOR / CCNP Data Center Core 350-601 study guide
Full concept coverage aligned to exam objectives
350-601 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise 350-601 questions linked to Network.
Practise 350-601 questions linked to Compute.
Practise 350-601 questions linked to Storage Network.
Practise 350-601 questions linked to Automation.
Practise 350-601 questions linked to Security.
Practise 350-601 questions linked to 350-601 fundamentals.
Practise 350-601 questions linked to 350-601 scenario.
Practise 350-601 questions linked to 350-601 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Automation — This question tests Automation — Read the scenario before looking for a memorised answer..
The correct answer is: The request payload is malformed — HTTP 400 indicates a bad request, which in the context of NX-API typically means the JSON or XML payload sent to the switch does not conform to the expected schema. Common issues include missing required fields (e.g., 'ins_api' version, 'type', 'chunk', 'sid', 'input', 'outputformat'), incorrect JSON syntax, or invalid values for parameters like 'version' or 'type'. The requests library successfully delivered the HTTP request, but the NX-API rejected it due to malformed content.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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
Last reviewed: Jun 24, 2026
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.