Book Image

Mastering Ansible, 4th Edition - Fourth Edition

By : James Freeman, Jesse Keating
Book Image

Mastering Ansible, 4th Edition - Fourth Edition

By: James Freeman, Jesse Keating

Overview of this book

Ansible is a modern, YAML-based automation tool (built on top of Python, one of the world’s most popular programming languages) with a massive and ever-growing user base. Its popularity and Python underpinnings make it essential learning for all in the DevOps space. This fourth edition of Mastering Ansible provides complete coverage of Ansible automation, from the design and architecture of the tool and basic automation with playbooks to writing and debugging your own Python-based extensions. You'll learn how to build automation workflows with Ansible’s extensive built-in library of collections, modules, and plugins. You'll then look at extending the modules and plugins with Python-based code and even build your own collections — ultimately learning how to give back to the Ansible community. By the end of this Ansible book, you'll be confident in all aspects of Ansible automation, from the fundamentals of playbook design to getting under the hood and extending and adapting Ansible to solve new automation challenges.
Table of Contents (18 chapters)
1
Section 1: Ansible Overview and Fundamentals
7
Section 2: Writing and Troubleshooting Ansible Playbooks
13
Section 3: Orchestration with Ansible

Questions

  1. Which Ansible module can be used to run tasks from a separate external task file when a playbook is run?

    a) ansible.builtin.import

    b) ansible.builtin.include

    c) ansible.builtin.tasks_file

    d) ansible.builtin.with_tasks

  2. Variable data can be passed to an external task file when it is called:

    a) True

    b) False

  3. The default name of the variable containing the current loop value is:

    a) i

    b) loop_var

    c) loop_value

    d) item

  4. When looping over external task files, it is important to consider setting which special variable to prevent loop variable name collisions?

    a) loop_name

    b) loop_item

    c) loop_var

    d) item

  5. Handlers are generally run:

    a) Once, at the end of the play

    b) Once each, at the end of the pre_tasks, roles/tasks, and post_tasks sections of the play

    c) Once each, at the end of the pre_tasks, roles/tasks, and post_tasks sections of the play and only when notified

    d) Once each, at the end of the pre_tasks, roles/tasks, and post_tasks sections of the play and only when imported...