The answer is that the playbook includes an invalid parameter `connection: network_cli` inside the task block. This error occurs because the `cisco.nxos.nxos_config` module does not accept a `connection` parameter at the task level; connection settings like `network_cli` must be defined at the play or inventory level, not within the task itself. On the Cisco DCCOR / CCNP Data Center Core 350-601 exam, this tests your understanding of Ansible playbook syntax for network automation, specifically how connection types are inherited from the play level rather than being redeclared per task. A common trap is treating network modules like command modules, where `connection` can be set locally—but for NX-OS modules, this causes the unsupported parameter error. Remember the memory tip: "Connection at the play, not the task—or your playbook won't last."
350-601 Automation Practice Question
This 350-601 practice question tests your understanding of automation. 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.
An Ansible playbook using the cisco.nxos.nxos_config module fails with the error: 'Unsupported parameters for (cisco.nxos.nxos_config) module: connection type setting'. 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 the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The playbook includes an invalid parameter 'connection: network_cli' inside the task block.
The error 'Unsupported parameters for (cisco.nxos.nxos_config) module: connection type setting' occurs because the `connection: network_cli` parameter is being passed inside the task block of the playbook. The `cisco.nxos.nxos_config` module does not accept a `connection` parameter at the task level; connection settings must be defined at the play or inventory level. This is a common syntax error when using Ansible network modules.
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 SSH key authentication is misconfigured.
Why it's wrong here
Authentication issues cause connection errors, not parameter unsupported errors.
✓
The playbook includes an invalid parameter 'connection: network_cli' inside the task block.
Why this is correct
The 'connection' parameter is a play-level attribute, not a task parameter for nxos_config.
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 module is not installed correctly.
Why it's wrong here
A missing module would give a different error, not about unsupported parameters.
✗
The playbook is targeting a device running an unsupported NX-OS version.
Why it's wrong here
Version unsupported would cause connection or execution errors, not parameter errors.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between play-level and task-level parameters, specifically that `connection` is not a valid parameter for network modules at the task level, leading candidates to incorrectly attribute the error to module installation or device compatibility.
Detailed technical explanation
How to think about this question
In Ansible, the `connection` setting is a play-level or inventory-level directive that defines how Ansible connects to the target (e.g., `network_cli`, `paramiko_ssh`, `local`). Network modules like `cisco.nxos.nxos_config` inherit this setting from the play context and do not accept it as a task parameter. When a user mistakenly includes `connection: network_cli` inside the task's `args` or as a top-level key within the task, Ansible's parameter validation rejects it because it is not a valid module argument. This is a frequent pitfall for those transitioning from older Ansible versions or from non-network modules.
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 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
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 playbook includes an invalid parameter 'connection: network_cli' inside the task block. — The error 'Unsupported parameters for (cisco.nxos.nxos_config) module: connection type setting' occurs because the `connection: network_cli` parameter is being passed inside the task block of the playbook. The `cisco.nxos.nxos_config` module does not accept a `connection` parameter at the task level; connection settings must be defined at the play or inventory level. This is a common syntax error when using Ansible network modules.
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.