DRAG DROP
-
Drag and drop the configuration management terms from the left onto the descriptions on the right. Not all terms are used.
DRAG DROP
-
Drag and drop the configuration management terms from the left onto the descriptions on the right. Not all terms are used.
The correct order is Agent push provision agentless post
This seems to be correct
last one is pull
My story and I am sticking to it: Agent push provision agentless pull
WTF.?????????????
Agent - daemon that determines when the central authority has updates available Push - model in which the central server sends updates to nodes on an as-needed basis Provision - easy-to-manage deployment option that may lack scalability Agentless - device hardware that runs without embedded management features Pull - to automatically install or deploy a configuration or update
Based on the given terms and definitions, here is how they should be matched: agent: daemon that determines when the central authority has updates available. agentless: model in which the central server sends updates to nodes on an as-needed basis. provision: easy-to-manage deployment option that may lack scalability. pull: device hardware that runs without embedded management features. push: to automatically install or deploy a configuration or update.
last one is 'pull' for the following definition below: "AUS supports a pull model of configuration that you can use for device configuration, configuration updates, device OS updates, and periodic configuration verification. In addition, supported devices that use dynamic IP addresses in combination with the Auto Update feature can use AUS to upgrade their configuration files and pass device and status information. " https://www.cisco.com/c/en/us/td/docs/security/security_management/cisco_security_manager/security_manager/425/deployment/deployment_planning_guide-425.html JJY888 has it correct I believe.
given answers are incorrect daemon that determines when the central authority has updates available == Agent model in which the central server sends updates to nodes on an as-needed basis == push easy-to-manage deployment option that may lack scalability == provision device hardware that runs without embedded management features == agentless to automatically install or deploy a configuration or update == pull Auto Update Server (AUS) enables you to upgrade device configuration files and Adaptive Security Appliance (ASA) devices that use the auto update feature. AUS supports a pull model of configuration that you can use for device configuration, configuration updates. https://www.cisco.com/c/en/us/td/docs/security/security_management/cisco_security_manager/security_manager/425/deployment/deployment_planning_guide-425.html https://dev.to/anubhavitis/push-vs-pull-api-architecture-1djo
Agent - daemon that determines when the central authority has updates available Push - model in which the central server sends updates to nodes on an as-needed basis Post - easy-to-manage deployment option that may lack scalability Agentless - device hardware that runs without embedded management features Provision - to automatically install or deploy a configuration or update
provision : to automatically install or deploy a configuration or update pull (model) : daemon that determines when the central authority has updates available push (model): model in which the central server sends updates to nodes on an as-needed basis agentless (-based management): device hardware that runs without embedded management features agent (-based management): easy-to-manage deployment option that may lack scalability https://gayatrisajith.medium.com/beginner-fundamentals-push-pull-configuration-management-tools-85eff1b41447
https://developer.cisco.com/docs/nx-os/#!agent-less-management https://developer.cisco.com/docs/nx-os/#!agent-based-management
https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/telemetry/70x/b-telemetry-cg-ncs5500-70x/b-telemetry-cg-ncs5500-70x_chapter_01.html
correct answer daemon that determines when the central authority has updates available == Agent model in which the central server sends updates to nodes on an as-needed basis == pull easy-to-manage deployment option that may lack scalability == push device hardware that runs without embedded management features == agentless to automatically install or deploy a configuration or update == provision
Agent push provision agentless pull
seems no one is sure of the answers
after enough research, i submit my findings: agent: daemon that determines when the central authority has updates available. pull: model in which the central server sends updates to nodes on an as-needed basis(nodes sends a pull request when needed). provision: easy-to-manage deployment option that may lack scalability. agentless: device hardware that runs without embedded management features(no agent installed). push: to automatically install or deploy a configuration or update(to push software or update from servers to nodes).
Confusing when everyone thinks he knows better. Stick to the theory found @ Cisco, don't use your own theory or things you do @ work, this can be your downfall @ Exam
I've asked a colleague of mine which is a genius in multiple areas of it. He said: agent - daemon that determines etc agentless - model in which the central server sends updates etc provision - easy to manage deployment option etc pull - device hardware that runs without embedded management push - to automatically install or deploy a configuration.
ChatGPT4 : Agent: This is typically a daemon that determines when the central authority has updates available. Agentless: This would correspond to a model in which the central server sends updates to nodes on an as-needed basis. Provision: Often refers to an easy-to-manage deployment option that may lack scalability. Pull: This term generally applies to the concept of a device hardware that runs without embedded management features, where the device initiates the configuration. Push: This is used to describe the process to automatically install or deploy a configuration or update, usually initiated by the central management server.
Pull Push Agent Agentless Provision
+ easy-to-manage deployment option that may lack scalability: agent + device hardware that runs without embedded management features: agentless + to automatically install or deploy a configuration or update: pull + daemon that determines when the central authority has updates available: provision + model in which the central server sends updates to nodes on an as-needed basis: push ======================== New Questions (added on 31st-Dec-2022) ========================
+ easy-to-manage deployment option that may lack scalability: Agent + device hardware that runs without embedded management features: Agentless + to automatically install or deploy a configuration or update: Pull + daemon that determines when the central authority has updates available: Provision + model in which the central server sends updates to nodes on an as-needed basis: Push had to arrange it for readability