1. Navigate to Jobs in Automation Controller.
2. Open the job details for the executed playbook.
3. View the logs for task outputs and errors.
Explanation:
Job logs provide insights into the execution flow and help debug issues within the EE.

git status
Explanation:
git status shows the current state of the working directory and staging area, helping track changes.

1. Create a Job Template: o Name: Run Git Playbook o Project: Git Project
o Playbook: site.yml
o Inventory: Add an appropriate inventory.
2. Save and launch the job.
Explanation:
Job templates tie playbooks to inventories and credentials, enabling consistent and repeatable automation execution.

1. Go to Jobs and select the template.
2. Check the Execution Environment field in the job details.
Explanation:
Validating ensures the correct EE is associated, providing the necessary dependencies for playbook execution.

- name: Delegate and control facts hosts: web1
tasks:
- name: Gather facts for db1 setup:
delegate_to: db1
delegate_facts: false
Explanation:
Setting delegate_facts: false stores gathered facts in the context of the delegating host rather than the target.