Ansible definition contradictions

[FonzTech]

Hi.

In Ansible exercises, it's told that:

True or False? Ansible uses declarative style to describe the expected end state
False. It uses a procedural style.

BUT in DevOps exercises, it's told that:

Explain Declarative and Procedural styles. The technologies you are familiar with (or using) are using procedural or declarative style?
Declarative Tools - Terraform, Puppet, CloudFormation, Ansible

Please, fix this.

Ansible clearly prioritizes declarative style!

Thanks.

[Manasa98-coder]

Ansible is primarily declarative in its approach to resource management (defining the what), even though its tasks are executed in a procedural sequence (the how of the playbook flow) and it allows for procedural overrides. Most practitioners and documentation emphasize its declarative nature. The DevOps exercise answer is the more widely accepted and useful description.

[neha-dev-dot]

Hi maintainers 👋

I'd like to suggest a clarification regarding Ansible's style (Declarative vs Procedural) in the exercises:

---

🔍 In Ansible Exercises, it states:

❌ False – "Ansible uses declarative style..."
✅ Answer: It uses a procedural style.

---

💡 But in DevOps Exercises, under "Declarative vs Procedural" you rightly include Ansible under Declarative Tools along with Terraform, Puppet, etc.

---

🛠️ Clarification:

Ansible is primarily declarative — users define the desired end state (e.g., "package should be installed", "service should be running") without manually coding how to reach that state.

While Ansible tasks execute in order (procedural flow), its resource management philosophy is declarative, which is why it's often grouped with declarative tools.

---

✅ Suggested Fix:
Update the Ansible Exercise question to reflect this correctly, e.g.:

True or False? Ansible uses declarative style to describe the expected end state
✅ True. Ansible is primarily declarative, though playbooks execute in a procedural sequence.

Thanks for the great repo!

– Neha Bharti (@neha-dev-dot)