Ansible Automation Ansible Tower and AWX 3

Question 1

How do you install AWX on Kubernetes using the official deployment method?

Accepted Answer

Deploy the AWX Operator using kubectl, then create an AWX custom resource definition (CRD) to provision the AWX instance

Answer

Run 'ansible-playbook install.yml' from the AWX GitHub repository

Answer

Use helm install awx redhat/awx

Answer

Deploy using docker-compose with the provided docker-compose.yml

Question 2

What is the purpose of 'schedules' in Ansible Tower/AWX?

Accepted Answer

They automate job launches at specified times using cron-like syntax, enabling unattended recurring automation

Answer

They define the order in which workflow nodes execute

Answer

They manage Tower's internal maintenance windows

Answer

They schedule inventory syncs only (not Job Templates)

Question 3

What is the 'callback URL' (Provisioning Callback) feature in Ansible Tower?

Accepted Answer

A feature that allows newly provisioned hosts to call Tower and trigger a Job Template to configure themselves, enabling auto-provisioning workflows

Answer

A webhook URL that Tower calls when a job completes

Answer

A URL for external systems to check Tower job status

Answer

A URL that Tower uses to pull playbooks from source control

Question 4

In Ansible Tower/AWX, what is 'fact caching' and how does it benefit automation at scale?

Accepted Answer

Tower stores Ansible facts from previous runs in its database, enabling playbooks to use cached facts without running the setup module on every execution

Answer

Tower caches compiled playbooks to speed up subsequent runs

Answer

Fact caching stores job output for display in the Tower UI

Answer

Tower caches SSH connections to reduce authentication overhead

Question 5

What does the 'ask_variables_on_launch' setting on a Tower Job Template enable?

Accepted Answer

It allows operators launching the job to provide extra variables at launch time through the UI or API without a survey

Answer

It requires all variables to be defined in the Tower UI before the job can run

Answer

It prompts for all playbook variables automatically with no configuration

Answer

It displays all current variable values for review before launch

Question 6

How does Ansible Tower/AWX support high availability (HA) deployments?

Accepted Answer

Multiple Tower nodes share a PostgreSQL database, with jobs distributed across execution nodes and a load balancer fronting the web tier

Answer

Tower requires an active-passive failover cluster with shared storage

Answer

HA is handled entirely by the Kubernetes operator with pod replication

Answer

Tower does not support HA—it requires third-party clustering solutions