Answer:- Ansible playbooks are pre-written code that developers can use on the fly or as a starting point. Ansible playbooks are used to automate complicated IT tasks, infrastructure (like operating system/Kubernetes platforms), security systems, and networks on a regular basis. An Ansible inventory is made up of a group, classification, or set of hosts that are all executed by Ansible playbooks.

Answer:- Ansible Galaxy is a collection of Ansible Roles that can be brought directly into your Playbooks to speed up your automation projects.

Answer:- In its codebase, Ansible supports a variety of module types. Some of these are meant for backward compatibility, while others provide flexibility. • Action Plugins Action plugins may seem like modules while using playbooks, however, both of them are different. Some action plugins handle everything, while the modules only give out the documentation. Some of these plugins even execute modules. The documentation for the majority of action plugins is to be found in a module with the same name. The controller is where all the action plugins run. • New style modules Modules that get shipped with Ansible come under this category. All official Ansible modules use Windows PowerShell or Python. New-style modules come with module arguments, while old-style modules require copying another folder to a controlled node which reduces the efficiency and requires two over the wired connectivity.

Answer:- Ansible Tower (previously known as AWX) is an internet-based solution that makes Ansible easier to use for IT departments of all types. Its intended to serve as the central hub for all of your automation projects.

Answer:- Ansible was built for multi-level deployments, and instead of managing one system at a time, it models your IT infrastructure by defining how all of your systems interact.

Answer:- Ad-hoc commands are one-line commands that are used to accomplish a particular task. Ad Hoc commands can be thought of as a replacement for playbooks. The following is an example of an Ad Hoc command: ansible host -m netscaler -a "nsc_host=nsc.xyz.com user=apiuser password=apipass" The above Ad Hoc command terminates the server by accessing the netscaler module.

Answer:- Variables are used by Ansible to manage system differences. With Ansible, you can use a single command to run tasks and playbooks on multiple different systems. During a playbook run, you can also create variables by recording the task’s return value or values as a new variable. Conditions can also be used around variables. Variables can be created inline as per below: - hosts: host1 vars: http_port: 80

Answer:- You can use Ansible Tasks to break down large chunks of configuration policy into separate tiny files. These are reusable code elements that can be used to automate any task. If you want to install a package or update a piece of software, for instance, you can use the code snippet below: install , update

Answer:- If you just want to double-check that everything in the playbook is in order, you u can run a syntax check on your code. Below is an example of using the command line to do a syntax check on an ansible-playbook $ ansible-playbook --syntax-check

Answer:- You can use the Dry Run feature to view what changes the playbook will make to the server without having to make the actual changes yourself. To accomplish this, simply add the -C option to your playbook startup task.

Answer:- It determines whether or not an Ansible playbook will ask for a password by default. “No” is the default option: ask_pass = true Its unlikely that youll need to change this setting if you use SSH keys for authentication.

Answer:- It controls whether an Ansible playbook should ask for a sudo password by default, same as ask_pass. No is also the default option. ask_sudo_pass = true. Users with sudo passwords enabled on their platforms can modify this setting.

Answer:- This determines whether or not an Ansible playbook will ask for the vault password by default. No is the default option. ask_vault_pass = true

Answer:- Ansible callbacks are bits of scripts that are executed when certain events occur, allowing notifications to be triggered.