Examkin

Question

Difficulty: HardCapabilities of Configuration Management Mechanisms (Puppet, Chef, Ansible)

A network engineering team is evaluating configuration management tools to automate Cisco IOS XE switch deployments. The architecture mandates that managed network devices must not require a persistent local management daemon or software agent, and all configuration task execution must be driven from a central control node using native management protocols and human-readable YAML files.

Which of the following operational characteristics correctly describe the selected configuration management tool? (Select TWO.)

  1. The framework utilizes a push-based communication model where the control node initiates management sessions directly to target network devices.Answer
  2. Configuration tasks are defined in playbooks and executed across endpoints over standard SSH or NETCONF transport protocols.Answer
  3. C
    Managed endpoints periodically initiate outbound connections over TCP port 8140 to pull target state definitions from a centralized master server.
  4. D
    System states are structured using Ruby-based cookbooks and recipes that must be compiled locally by a client daemon running on each switch.

Answer

The configuration management mechanism described is Ansible, which uses a push-based communication model from a control node over standard transport protocols (SSH/NETCONF) with YAML playbooks and requires no agent software on target endpoints.
The scenario describes Ansible, which is unique among the three major configuration management tools for being completely agentless on target network devices. Ansible relies on a push-based model where the control node opens standard transport sessions (such as SSH or NETCONF) to execute tasks defined in YAML playbooks.

Step-by-Step Solution

1
Analyze the architectural requirements stated in the scenario.
The requirements specify an agentless architecture, central control node driving execution, native management protocols (SSH/NETCONF), and YAML files.
Identifying these key attributes narrows the tool down to Ansible, distinguishing it from agent-based pull systems like Puppet and Chef.
2
Evaluate the delivery mechanism and transport method of Ansible.
Ansible uses a push model where the control node initiates connections to managed devices using SSH or NETCONF.
Because no persistent agent daemon is installed on managed network switches, Ansible relies on native network management transport protocols.
3
Verify file structure and contrast with alternative mechanisms.
Ansible uses YAML playbooks. In contrast, Puppet uses Puppet DSL manifests over TCP 8140 (pull), and Chef uses Ruby recipes/cookbooks over TCP 443 (pull).
This confirms that options describing push-based execution over SSH/NETCONF and YAML playbooks are correct, while options referring to TCP 8140 pull operations or Ruby cookbooks describe Puppet and Chef.

Key Concept

Ansible Agentless Push Architecture and Protocol Capabilities
Estimated Time:2m 0s
Rate this question

Topics

Capabilities of Configuration Management Mechanisms (Puppet, Chef, Ansible)

More questions from this topic