Questions

  1. What is a key advantage of using AWX to store your credentials over the methods available to you on the command line?
  2. Why is it important to make good use of a version control system such as Git to store your playbooks?
  3. How is AWX advantageous over Ansible on the command line when it comes to dynamic inventories?
  4. What is a project in AWX?
  5. What is a template in AWX analogous to on the command line?
  6. How does AWX tell you which commit to a Git repository a playbook run was performed against?
  7. Why is it advisable to restrict access to the server that hosts AWX, especially the shell and local filesystem?
  8. If you need to programmatically launch playbook runs, how can AWX help you?

Get Hands-On Enterprise Automation on Linux now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial