Pull model

Q: How deeply does Acing the CCNA Exam: Volume 2 Advanced Networking and Security cover pull model?

Defines request direction, agent architecture, workload distribution, and update delays, but does not detail agent implementation.

As explained in Acing the CCNA Exam: Volume 2 Advanced Networking and Security

A pull model is an automation pattern in which managed systems periodically connect to a management system and retrieve configuration.

A pull model is an automation pattern in which each managed device periodically connects to a management server and retrieves its configuration. The client requests configuration instead of receiving it from a server-initiated push. section 25.2.3 section 25.2

Recognize the pattern through these characteristics:

Use an agent-based architecture: install a software agent on every managed device. section 25.2.3
Let managed devices independently check for and apply configuration updates. section 25.2.1
Expect update delays because devices must check in before receiving changes. section 25.2.1
Contrast it with push automation, which provides centralized control and immediate updates from the management server. section 25.2.1

Puppet and Chef

Puppet and Chef primarily use pull models for configuration management. Their agents connect to a central server, retrieve configuration information, and apply changes. Puppet defines desired state with Puppet DSL; Chef uses a procedural approach. section 25.2.3 section 25.3

Table 25.1 Configuration management tools (view table figure)

	Ansible	Terraform	Puppet	Chef
Language	Python	Go	Ruby	Ruby
Configuration file format	YAML	HashiCorp Language (HCL)	Puppet DSL	Ruby
Communication protocol	SSH, NETCONF	HTTP (API)	HTTP (API)	HTTP (API)
Agent-based/agentless	Agentless	Agentless	Agent-based	Agent-based
Procedural/declarative	Procedural	Declarative	Declarative	Procedural
Push/pull	Push	Push	Pull	Pull

Compare pull-based Puppet and Chef with push-based Ansible and Terraform across architecture, configuration style, language, and communication protocol. section 25.2

How Acing the CCNA Exam: Volume 2 Advanced Networking and Security covers it

Cover of Acing the CCNA Exam: Volume 2 Advanced Networking and Security

liveBook manning.com

Read Acing the CCNA Exam: Volume 2 Advanced Networking and Security on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

The Joy of JavaScriptA communication or data-flow model in which a consumer requests data when it needs it.
liveBook manning.com

Spring in Action, Sixth EditionA pull model is a messaging consumption pattern in which a consumer explicitly requests or retrieves messages, potentially waiting until one is available.
liveBook manning.com

Learn Docker in a Month of Lunches, Second EditionA pull model is a data-collection approach in which a monitoring system periodically fetches data from monitored systems.

Compare how 4 books explain pull model →

Related concepts

Prometheusused by · Prometheus is an open-source monitoring and alerting system that collects, stores, and queries time-series metrics.
streamingused by · Streaming is the incremental handling of a sequence of data items, including their processing, transfer, or consumption as they become available.
YAGNI principleincludes · The YAGNI principle is a software design discipline of avoiding functionality or structure until a concrete need for it arises.
push modelcontrasts with · A push model is a communication pattern in which a producer or system proactively sends data, work, or updates to recipients rather than waiting for each to request them.
JmsTemplateused by · JmsTemplate is a Spring API that simplifies JMS message production and consumption by managing messaging boilerplate and exceptions.

This explainer was generated by Manning's knowledge graph from the text of Acing the CCNA Exam: Volume 2 Advanced Networking and Security. The section links point to the parts of the book it draws on.