Free Designing, Deploying and Managing Network Automation Systems Practice Questions

Sample Practice Questions

Try these 10 sample questions from the Designing, Deploying and Managing Network Automation Systems practice bank. Each includes the answer and explanation. Continue with the interactive practice above to review the full question set.

1. 1An offline review job must turn a proposed VLAN configuration into Cisco IOS CLI commands using cisco.ios.ios_vlans. Which module state should the job use?

   1. A. state: gathered
   2. B. state: rendered
   3. C. state: parsed
   4. D. state: merged

   Answer: B

   Explanation: The module describes rendered output as "platform specific CLI commands which will be returned in the I(rendered) key". Use rendered to translate the proposed config without applying it. Gathered reads a device, parsed interprets captured output, and merged applies configuration.

   Reference: Cisco IOS Ansible Collection — ios_vlans module documentation — DOCUMENTATION > state > rendered

2. 2A network configuration feature branch has several commits. Starting from a clean main branch, the maintainer wants their combined changes in one new ordinary commit, without recording a merge commit. Which sequence implements this?

   1. A. git merge --no-ff feature -m "Integrate feature"
   2. B. git merge --squash feature git commit -m "Integrate feature"
   3. C. git checkout feature git commit --amend -m "Integrate feature"
   4. D. git merge --no-commit feature git commit -m "Integrate feature"

   Answer: B

   Explanation: The merge manual says --squash lets you "create a single commit on top of the current branch". It prepares the combined working tree and index without recording merge information; the following commit records an ordinary commit. No-ff and no-commit merges retain merge semantics, and amending the feature tip does not integrate its changes into main.

   Reference: Git git-merge manual — OPTIONS > --squash

3. 3In Cisco's model-driven telemetry architecture, which role creates subscriptions while directing the associated telemetry data to separate receivers rather than receiving it itself?

   1. A. Publisher
   2. B. Controller
   3. C. Receiver
   4. D. Subscriber

   Answer: B

   Explanation: Cisco defines the controller as the entity that "creates subscriptions but does not receive the telemetry data." The publisher sends data; the receiver collects it; the subscriber both creates subscriptions and receives data in the documented role model.

   Reference: Cisco IOS XE — Model-Driven Telemetry — Model-Driven Telemetry > telemetry roles

4. 4An engineer uses GitHub Copilot inline suggestions while writing a network automation script. Which capability can directly accelerate authoring within this inline-suggestion experience?

   1. A. Execute the proposed script against the target network.
   2. B. Certify the proposed script's compliance with network policy.
   3. C. Confirm the target devices' current operational state.
   4. D. Propose code completions and edits from editor context.

   Answer: D

   Explanation: GitHub describes inline suggestions as helping developers by "completing code, generating new blocks, or modifying existing code." This accelerates authoring. Inline suggestions do not themselves execute the script, certify policy compliance, or establish live device state.

   Reference: GitHub Copilot inline suggestions — Responsible use application card — 4. Intended uses > Accelerating code authoring

5. 5A VLAN inventory playbook must read the current configuration from a reachable switch and return structured data without changing the switch. Which cisco.ios.ios_vlans state implements this step?

   1. A. state: replaced
   2. B. state: merged
   3. C. state: gathered
   4. D. state: parsed

   Answer: C

   Explanation: The documentation states, "The state I(gathered) will fetch the running configuration from device and transform". Gathered obtains live configuration and returns it as structured data without changing the device. Replaced and merged are configuration-management states that can change it; parsed consumes previously supplied CLI text.

   Reference: Cisco IOS Ansible Collection — ios_vlans module documentation — DOCUMENTATION > state > gathered

6. 6A release branch needs the patch introduced by commit abc123 from another branch, without integrating that branch's other commits. The working tree is clean. Which command applies that selected patch and normally records a new commit?

   1. A. git merge other-branch
   2. B. git reset --hard abc123
   3. C. git checkout abc123
   4. D. git cherry-pick abc123

   Answer: D

   Explanation: The cherry-pick manual says it will "apply the change each one introduces, recording a new commit for each." Cherry-pick selects the specified patch. Merge integrates branch history, reset moves the branch state, and checkout selects a commit without applying its patch as a new release-branch commit.

   Reference: Git git-cherry-pick manual — DESCRIPTION

7. 7An IOS XE telemetry design requires its subscription definition to survive publisher reboots and transport interruptions, with the publisher initiating the receiver connection. Persistent configuration will be saved to startup configuration. Which subscription architecture matches this?

   1. A. A dynamic dial-in subscription tied to a client session.
   2. B. A dynamic subscription with a longer client socket timeout.
   3. C. A dynamic dial-in subscription with a periodic update policy.
   4. D. A configured dial-out subscription stored on the publisher.

   Answer: D

   Explanation: Cisco states, "These subscriptions persist across device reboots and transport session interruptions." With configuration saved to startup as specified, configured dial-out subscriptions meet the requirement. Dynamic subscriptions remain session-bound; a longer timeout or a periodic update policy does not make their definitions persistent.

   Reference: Cisco IOS XE — Model-Driven Telemetry — Configured subscriptions; High Availability in telemetry

8. 8Copilot proposes a network configuration script that looks syntactically valid. Which review approach addresses the documented risk that the code does not implement the engineer's intended behavior?

   1. A. Accept it after checking indentation and syntax alone.
   2. B. Review its logic and test it against the required behavior.
   3. C. Accept it if the public-code matching filter allows it.
   4. D. Accept it if the same suggestion appears on another attempt.

   Answer: B

   Explanation: GitHub warns that generated code may "not accurately reflect the intent of the developer." Logic review and behavior-based testing address that risk. Syntax checks, matching filters, and repeated generation do not establish that the script meets the specified network requirements.

   Reference: GitHub Copilot inline suggestions — Responsible use application card — 7. Limitations > Inaccurate code

9. 9A compliance job has captured VLAN CLI output in the documented running_config format. It must convert that text into structured data while the switch is unavailable. Which cisco.ios.ios_vlans state should it use?

   1. A. state: parsed
   2. B. state: gathered
   3. C. state: rendered
   4. D. state: replaced

   Answer: A

   Explanation: The source says, "The state I(parsed) reads the configuration from C(running_config) option". Parsed consumes the captured CLI text without needing an active connection. Gathered requires live device data, rendered translates structured configuration into CLI, and replaced is a configuration-changing state.

   Reference: Cisco IOS Ansible Collection — ios_vlans module documentation — DOCUMENTATION > state > parsed

10. 10A developer must undo the latest unpushed Git commit while preserving both the working-tree files and the current index exactly, so its changes remain staged for a replacement commit. Which command matches these requirements?

    1. A. git reset --soft HEAD~1
    2. B. git reset --mixed HEAD~1
    3. C. git reset --hard HEAD~1
    4. D. git revert HEAD

    Answer: A

    Explanation: For --soft, the reset manual states, "Leave your working tree files and the index unchanged." Soft reset moves HEAD back while retaining staged changes. Mixed reset resets the index, hard reset also resets the working tree, and revert creates a reversing commit rather than undoing the unpushed commit as requested.

    Reference: Git git-reset manual — DESCRIPTION > --soft, --mixed, and --hard