Skip to content
AvailabilitySign inBook a DemoStart free lab
Topic: Configuration Management ToolsSwitch
All CCNP topics

6.0 Automation

Configuration Management Tools Practice Questions

Ansible, Chef, and Puppet for network device configuration management.

One solved question, so you can see how these are marked

Which configuration management software is agentless, is written in Python, connects to managed nodes over SSH, and describes its automation in YAML playbooks?

Ansible

Ansible is agentless: the control node interprets YAML playbooks and connects to managed nodes over SSH (or WinRM, or network_cli for network devices) to run modules or send commands. Puppet and Chef rely on installed client agents and Ruby-based code.

Every question in the set below is marked like this. The answers stay hidden until you pick one.

All 5 Configuration Management Tools questions in this set

Answers and explanations appear when you work through the set above.

  1. What file in Ansible defines the target hosts, network devices, and IP addresses that playbooks execute tasks against?

    • ansible.cfg
    • Inventory file
    • YAML Playbook
    • Jinja2 Template

  2. Which system management tool uses Python, operates agentlessly via SSH for network configuration, and uses YAML for formatting playbooks?

    • Puppet
    • Chef
    • Ansible
    • SaltStack

  3. Which configuration management system uses Ruby DSL syntax, requires an installed client agent on target nodes, and relies on a central server designated as the "Chef Server"?

    • Ansible
    • Puppet
    • Chef
    • Terraform

  4. In Ansible infrastructure automation, what play-level parameter defines the target inventory group on which the play's tasks execute?

    • hosts:
    • vars:
    • gather_facts:
    • connection:

  5. What is the structural relationship between an Ansible Playbook, a Play, and a Task?

    • A Playbook holds one or more Plays; each Play maps hosts to an ordered list of Tasks that call modules.
    • A Task holds one or more Playbooks; each Playbook maps hosts to Plays written as Python functions.
    • A Play holds one or more Playbooks, and each Playbook runs a single Task against every inventory host.
    • Plays run locally on the control node, while Tasks run inside a Docker container on each managed host.