Most Ansible modules check whether the desired final state has already been achieved, and exit without performing any actions if that state has been achieved, so that repeating the task does not change the final state. Modules that behave this way are often called ‘idempotent.’ Whether you run a playbook once, or multiple times, the outcome should be the same. However, not all playbooks and not all modules behave this way. If you are unsure, test your playbooks in a sandbox environment before running them multiple times in production. (Source: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_intro.html).... I think you are right
- Impact analysis is a Continuous Delivery for Puppet Enterprise (PE) tool that shows you the potential impact that new Puppet code can have on your PE-managed infrastructure, without actually merging the new code.
- Ansible Lint is a command-line tool for linting playbooks, roles, and collections aimed toward any Ansible users. Its main goal is to promote proven practices, patterns, and behaviors while avoiding common pitfalls that can easily lead to bugs or make code harder to maintain.
- Puppet utilizes an agent-based approach, while Ansible is an agentless (push) architecture.
given answers are incorrect
Ansible:
agentless automation platform
assesses the impact of changes before applied
Puppet:
agent or agentless automation platform
provides intent-based networking feedback loop
Ansible’s check mode allows you to execute a playbook without applying any alterations to your systems.
You can use check mode to test playbooks before implementing them in a production environment.
The puppet intent-based automation solution can automate the repetitive configuration management tasks quickly.
The answer is correct.
https://www.puppet.com/blog/ansible-vs-puppet
Visibility
Ansible Controller (formerly Tower) offers a visual user interface to schedule and run tasks. However, both reporting and historical auditing capabilities are not included, which makes it difficult to preview the impact of new code.
Puppet’s interface was built with viewing, managing, and monitoring in mind. Impact Analysis (available in Continuous Delivery for Puppet Enterprise) will parse changes to your existing code, adding additional visibility.
ansible-playbook provides a --check option, which enables Ansible check mode. In this mode, Ansible runs through your playbook and reports what it would do, but makes no actual changes. This allows you to validate your code before applying it for real, providing several benefits including:
allowing you to catch syntax errors in your code
allowing you to validate the changes that Ansible intends to make, to ensure they match your expectations
Additionally, you can also pass --diff. With this option, for each task that Ansible detects changes will be necessary, Ansible will output the difference between the current state and the changes it intends to make.
https://www.clockworknet.com/blog/2020/06/05/mastering-ansible-check-mode/
I believe answer is correct. This explains features of puppet.
https://www.globenewswire.com/news-release/2019/05/02/1815333/0/en/Puppet-s-Latest-Release-Offers-Organizations-a-One-Stop-Shop-for-Infrastructure-Automation.html
Intent-based feedback loops seem to be more appropriate with Puppet:
Feedback loops must be maintained to ensure that any issues picked up along the stream are reported back to the right area for remediation.
Configuration management tools, including Puppet, support some of these critical tasks.
https://www.techtarget.com/searchitoperations/tip/What-is-the-Puppet-configuration-management-tool-and-how-does-it-work
Intent-Based Network Automation with Ansible
Ansible is interesting because it’s often debated if it’s imperative or declarative. This partially goes back to defining something as intent-driven or not.
Within Ansible, there are modules, tasks, plays, and roles that allow you to build your own abstractions that perform how you need them to fit your environment. This means you can write an Ansible playbook to automate your network that enforces your precise intent. Of course, if you look inside the playbook, you may see some imperative tasks, but who cares? This is why there are platform architects (who build robust playbooks) and users of the system (who execute the playbooks).
I believe the given answer is correct based on this article:
http://jedelman.com/home/intent-based-network-automation-with-ansible/
upvoted 3 times
...
This section is not available anymore. Please use the main Exam Page.350-401 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
MO_2022
Highly Voted 2 years, 4 months agoRose66
2 years, 3 months agoAM17212
1 year, 2 months agoAbdullahMohammad251
Most Recent 7 months, 2 weeks ago[Removed]
11 months ago[Removed]
11 months ago[Removed]
1 year, 8 months agomdawg
2 years, 2 months agosnarkymark
2 years, 3 months agoHungarianDish_111
2 years, 3 months agoslacker_at_work
1 year, 2 months agoAndreasThornus
2 years, 4 months ago