Ansible & Configuration Management
Configuration management, explained from the ground up. Learn how Ansible automates servers agentlessly over SSH — inventory, playbooks, roles, templates and Vault — and remember it with spaced repetition.
- flashcards
- 90
- flashcards
- per day
- ~10 min
- per day
- level
- Beginner → Intermediate
- level
- modules
- 6
- modules
What is Ansible?
Ansible is an open-source automation tool for configuration management: instead of logging into servers and running commands by hand, you describe the state you want in playbooks, and Ansible makes each machine match it. Its defining trait is that it is agentless — the control node connects over ordinary SSH and pushes configuration, so there is nothing to install or maintain on the managed hosts.
The heart of Ansible is idempotency: a well-written task can run a hundred times and only changes what actually needs changing. Playbooks are plain YAML, built from tasks that call modules, organized with handlers, variables, facts and Jinja2 templates — and packaged for reuse as roles and collections shared through Ansible Galaxy.
This track breaks Ansible into bite-sized, practical questions — core concepts, playbooks, roles, control flow, and day-to-day operations like Vault, tags and privilege escalation — and finishes with real-world troubleshooting scenarios. Spaced repetition moves it all from "I followed a tutorial once" to fluent recall.
6 modules, seed to bloom
Each module is a set of flashcards — 90 in total. Answer, review, and watch your knowledge grow from seed to full bloom.
Core Concepts
Ansible fundamentals — agentless architecture, control and managed nodes, inventory, modules and tasks, idempotency, and push vs pull
15 cardsPlaybooks
Writing Ansible playbooks — plays and task order, handlers and notify, variables and facts, and Jinja2 templates
15 cardsRoles & Reuse
Structuring and sharing Ansible content — role layout, ansible-galaxy and collections, requirements files, and import vs include reuse
15 cardsControl Flow & Data
Directing playbook execution — loops, conditionals with when, register, set_fact, blocks with rescue and always, and error handling
15 cardsPractical Ops
Running Ansible day to day — ad-hoc commands, Vault for secrets, check and diff modes, tags, host limiting and privilege escalation
15 cardsPractical Tips
Real-world Ansible troubleshooting — why command tasks always change, handlers don't fire, templates stay literal, roles' vars get overridden, and tasks hit permission denied
15 cardsSample questions
A taste of the real flashcards. Pick an answer, then reveal the explanation.
What kind of architecture does Ansible use to manage remote nodes?
- AAgentless — it connects to nodes over SSH with no agent installed on them
- BAgent-based — a daemon must be installed and running on every managed node
- CMaster-minion — nodes poll a central master server for their configuration
- DPeer-to-peer — nodes gossip their state to one another in order to converge
What is a handler in Ansible?
- AA task that runs only when another task notifies it of a change
- BA task that runs first in every play, before the others start
- CA task that Ansible retries automatically until it succeeds
- DA task that is skipped unless the play is run with --tags
What makes a directory a valid Ansible role?
- AIts subdirectory layout: tasks/, defaults/, handlers/
- BA galaxy_info block naming the author and licence
- CA requirements entry in the playbook that uses it
- DPublication to Ansible Galaxy before its first use
What does Ansible Vault do?
- AIt encrypts sensitive data such as passwords in variables and files
- BIt stores plaintext secrets on a central server for playbooks to read
- CIt scans playbooks for hardcoded secrets and warns you about them
- DIt rotates the SSH keys that are used to connect to managed nodes
Learn it once, keep it for good
Answer a question
Each card is one practical concept with multiple options. Pick what you think is right.
Get the full answer
See the correct option plus a clear explanation, and a link to deeper docs when one is available.
Review at the right time
A spaced-repetition engine (SM-2 or FSRS) resurfaces each card just before you would forget it.
Why Ansible is worth your time
The standard for configuration management
Ansible automates fleets of servers across almost any environment. Fluency is a core DevOps and sysadmin skill.
Agentless, so easy to adopt
No agents to install — if a host has SSH and Python, Ansible can manage it, which is why teams reach for it first.
Repeatable, not one-off
Idempotent playbooks turn manual server setup into codified, reviewable, re-runnable automation.
Completes the IaC picture
Where Terraform provisions infrastructure, Ansible configures it — the two pair naturally on real projects.
Common questions
Do I need Linux experience first? +
A little helps, since Ansible configures mostly Linux hosts over SSH, but the track starts from first principles — architecture, inventory and playbooks — so motivated beginners can follow along.
Does it cover roles, Vault and templates? +
Yes. Dedicated modules cover roles and collections, Jinja2 templates, loops and conditionals, and day-to-day operations including Ansible Vault, tags and privilege escalation.
Is it free? +
Yes, completely free. No registration or credit card is required, and all your progress is stored locally in your browser.
How long does it take? +
About 10 minutes a day. Spaced repetition means short, frequent sessions beat long cramming — most learners get comfortable with the fundamentals within a couple of weeks.
Ready to master Ansible?
Plant your first seed today. Ten minutes a day is all it takes to grow real, lasting automation skills.