Communication & Stakeholder Relations Flashcards

A manager asks why the Ansible project needs an ansible.cfg file. What is the clearest non-technical explanation?

Answer: It defines default settings and behaviors for the project so teams don't have to repeat options on every command

ansible.cfg centralizes project configuration defaults like inventory location, remote user, and connection settings, simplifying team workflows.

Stakeholders want to know how Ansible Automation Platform's Role-Based Access Control (RBAC) benefits their organization. What is the key value proposition?

Answer: RBAC ensures users can only access and run the automation relevant to their role, reducing security risk

RBAC in AAP restricts access to inventories, job templates, and credentials based on job function, enforcing least-privilege principles.

A stakeholder is concerned that automating server configuration will reduce team flexibility. How do you best address this concern?

Answer: Explain that Ansible playbooks are easily modified and version-controlled, making changes faster and more consistent than manual processes

Version-controlled playbooks can be updated quickly and consistently, and changes propagate uniformly across all systems faster than manual intervention.

During an incident review, the team realizes an Ansible playbook caused an unintended configuration change. What practice would have caught this before production?

Answer: Testing playbooks in a staging environment and using --check mode before promoting to production

Staging environment testing combined with --check dry-run mode validates playbook behavior before changes reach production systems.

A stakeholder wants to understand what 'handlers' in Ansible are and why they matter for reliability. What is the best explanation?

Answer: Handlers are tasks that only run when notified by another task, preventing unnecessary service restarts

Handlers run only when notified by a changed task, ensuring services like web servers restart only when their configuration actually changed.

A cross-department team wants to share Ansible roles without duplicating code across projects. What is the recommended approach for distributing shared roles?

Answer: Publish roles to Ansible Galaxy or a private Automation Hub and reference them with requirements.yml

Ansible Galaxy and private Automation Hub provide centralized role repositories that teams can reference via requirements.yml for consistent shared content.

An IT director asks how automation with Ansible reduces human error compared to manual runbooks. What is the most compelling argument?

Answer: Automation executes the same tested code every time, eliminating variability from human interpretation and manual execution differences

Automated playbooks remove human variability by executing identical, pre-tested logic consistently across every run and every target system.