Free Automating Cisco Data Center Networking Solutions Practice Questions
100 free questions · Answer explanations · No signup required
View examination details, outline and sourcesLoading selected examination banks…
Sample Practice Questions
Try these 10 sample questions from the Automating Cisco Data Center Networking Solutions practice bank. Each includes the answer and explanation. Continue with the interactive practice above to review the full question set.
1What is a defining design goal of OpenConfig YANG models?
- A. Describe a common, vendor-neutral network data model.
- B. Describe only the internal objects of Cisco NX-OS.
- C. Define the transport framing for NETCONF sessions.
- D. Convert every vendor CLI into an identical command set.
Answer: A
Explanation: Cisco describes "vendor-neutral OpenConfig YANG data models". OpenConfig standardizes modeled data across vendors; it is neither a Cisco-only internal model nor a transport or CLI standard.
Reference: Getting Started with Model-Driven Programmability on Cisco Nexus 9000 Series Switches — YANG models supported by Cisco Nexus 9000 Series NX-OS
2Which practice characterizes infrastructure as code for a data center fabric?
- A. Configuration files serve only as records after manual provisioning.
- B. Reusable configuration files are inputs to tools that manage infrastructure.
- C. Configuration files cannot drive changes and must be translated manually.
- D. Each provider requires an unrelated language and deployment workflow.
Answer: B
Explanation: HashiCorp states that IaC tools "manage infrastructure with configuration files". These files drive management rather than serving only as after-the-fact records. Its provider workflow supports a consistent language across platforms rather than requiring an unrelated language per provider.
Reference: What is Infrastructure as Code with Terraform? — Opening definition of Infrastructure as Code
3In a Python ncclient session m, which call retrieves the running configuration using the get-config RPC?
- A. m.get(source='running')
- B. m.copy_config(source='running', target='candidate')
- C. m.get_schema(identifier='running')
- D. m.get_config(source='running')
Answer: D
Explanation: The API documents "get_config(source, filter=None, with_defaults=None)" and maps it to GetConfig. Passing running as source selects that datastore. Get does not accept source; copy_config writes another datastore, and get_schema retrieves a schema rather than configuration.
Reference: ncclient Manager — High-level API — Manager > get_config; Special kinds of parameters > Source and target parameters
4When using CML reference platforms to validate a data center design, which conclusion respects the documented scope of their device behavior?
- A. Every physical ASIC feature is reproduced by each virtual image.
- B. Only CLI command spelling is reproduced; software protocols do not run.
- C. Software-level features are generally supported, with exceptions.
- D. Physical port optics and transceiver faults are fully reproduced.
Answer: C
Explanation: Cisco describes "software-level feature parity to physical devices that run the same operating system, with some exceptions". This supports software protocol and configuration tests, while requiring checks for features that depend on absent physical hardware.
Reference: Cisco Modeling Labs v2.x — FAQ — Reference Platform and Images Questions > 1. What are reference platforms?
5While an engineer writes an ncclient script, what assistance can GitHub Copilot inline suggestions provide?
- A. Predict code completions and edits using the surrounding code context.
- B. Act as a compiler that rejects every invalid device API before showing code.
- C. Retrieve unchanged vendor examples without generating new code suggestions.
- D. Complete identifier names while being unable to suggest larger code blocks.
Answer: A
Explanation: GitHub describes suggestions that "complete the current line, generate new blocks of code, or suggest edits to existing code." This is contextual code generation, not a compiler guarantee, retrieval-only copying, or identifier-only completion.
Reference: Application Card: GitHub Copilot Inline Suggestions — Section 1, Overview > IDE inline suggestions
6Which YANG model category is intended to expose Cisco NX-OS-specific configuration beyond a vendor-neutral common feature set?
- A. OpenConfig vendor-neutral YANG models.
- B. Cisco native NX-OS YANG models.
- C. IETF standardized YANG models.
- D. IEEE standardized YANG models.
Answer: B
Explanation: Cisco recommends native models "for support of specific Cisco NX-OS Software features". Native models expose NX-OS-specific coverage. OpenConfig, IETF, and IEEE models are open/common modeling families, rather than Cisco's native device schema.
Reference: Getting Started with Model-Driven Programmability on Cisco Nexus 9000 Series Switches — YANG models supported by Cisco Nexus 9000 Series NX-OS
7What does a declarative GitOps description specify for network infrastructure?
- A. The ordered CLI instructions that perform each configuration change.
- B. The procedural handlers that implement every infrastructure transition.
- C. The intended end state that the system should reach.
- D. The manual runbook steps that operators must execute in sequence.
Answer: C
Explanation: OpenGitOps requires "desired state expressed declaratively". A declaration specifies the target infrastructure state; ordered CLI instructions, procedural transition handlers, and manual step sequences instead describe how to perform changes.
8A connected ncclient Manager m controls an NX-OS device advertising writable-running. The variable payload contains a valid NETCONF config element. Which call applies that payload directly to running configuration?
- A. m.edit_config(target='running', config=payload)
- B. m.get_config(source='running', filter=payload)
- C. m.validate(source='running')
- D. m.copy_config(source='running', target='startup')
Answer: A
Explanation: The documented edit operation accepts "target='candidate', default_operation=None, test_option=None, error_option=None", and its first argument is config. Explicitly setting target to running edits that datastore. Retrieval, validation, and copying running to startup do not apply the supplied edit payload.
Reference: ncclient Manager — High-level API — Manager > edit_config
9A team wants to model a Nexus switch in CML by uploading the .bin image copied from the physical switch. What limitation applies to that approach?
- A. Physical-device images are not built as the VM images required by CML.
- B. Renaming the physical .bin file to .qcow2 makes it a usable CML image.
- C. Assigning more vCPUs and RAM makes the physical .bin a usable VM image.
- D. Matching the physical device's x86_64 CPU architecture makes its image usable.
Answer: A
Explanation: Cisco states: "it is not possible to use images taken from a physical device in CML." The FAQ explicitly explains that even x86_64 physical-device images assume hardware and are not VM builds. Renaming the file or allocating more resources does not change that dependency.
Reference: Cisco Modeling Labs v2.x — FAQ — Reference Platform and Images Questions > 11. Can I use an image taken from a physical device within CML?
10An AI coding assistant keeps proposing a different Python library than the one approved for a network automation script. Which prompt/context change directly addresses that mismatch?
- A. Remove the script's existing import statements from the supplied context.
- B. Ask for more explanatory comments in the generated Python code.
- C. Explicitly name the required library or include its imports.
- D. Describe the network device platform and desired JSON output fields.
Answer: C
Explanation: GitHub advises: "set the import statements at the top of the file or specify what library you want to use." Naming the implementation library directly addresses the mismatch. Removing that context, requesting comments, or describing platforms and output alone does not identify the approved Python library.
Reference: Prompt Engineering for GitHub Copilot — Avoid ambiguity, specific-library guidance
Topics in this practice bank
These topics describe the available practice for Automating Cisco Data Center Networking Solutions. Review the examination outline and its sources for scope and allocation details.
Network Automation Foundation
- Describe OpenConfig, IETF, and native YANG models
- Describe ACI-based network-centric mode including objects such as EPG, bridge domains, contracts, and VRFs
- Describe DPUs in data center network switches
- Describe NETCONF, gNMI, gRPC, and gNOI
- Construct a gRPC payload based on a YANG module using tools such as YANG Suite and pyang
Infrastructure as Code
- Describe infrastructure as code (IaC) and GitOps
- Construct network configuration templates with Jinja2 using features such as loops, conditionals, output modifiers, and filters
- Construct an Ansible playbook with controller and device collections
- Construct a Terraform plan with controller and device providers
- Troubleshoot network automation solutions based on Ansible and Terraform
Network Element Programmability
- Construct a network automation solution with Python using ncclient to manage and monitor configurations
- Construct a device-level network automation solution for Day-0 provisioning with POAP
- Implement on-box programmability and automation with NX-OS using
- Describe the use of templates and policies in Nexus Dashboard
- Construct network configuration templates with Nexus Dashboard
- Describe capabilities and features of NX-API
Operations
- Describe use of network topology simulation related to data center operations
- Implement change validation for a network automation solution using pyATS CLI tools
- Describe architectural components of model-driven telemetry
- Configure a subscription for model-driven telemetry on NX-OS devices (gNMI and gRPC)
- Integrate a network automation solution with a network source of truth
- Construct a Python script that retrieves network health data from NX-OS devices via CLI and Nexus Dashboard
- Troubleshoot packet flows for containerized workloads on Linux hosts considering VLANs, veth, bond interfaces, subinterfaces, and bridges
AI in Automation
- Describe AI-assisted code development for network automation
- Describe the security risks in a given AI-based network automation solution
- Describe the integration of network devices, controllers, and management platforms with AI agents
How to use these free practice questions
Choose an answer, check the explanation, and review your progress by chapter. Practice questions and explanations are free to access without signing up.
These are independent study questions, not actual examination items. For examination requirements and official information, view Automating Cisco Data Center Networking Solutions details.