Infrastructure as Code and Configuration Management Flashcards
Microsoft DevOps Engineer Expert AZ-400 Flashcards

| Front | Back |
| Advantages of Declarative IaC | Simplifies infrastructure description by focusing on end states |
| Advantages of IaC | Scalability, repeatability, and version control for infrastructure |
| Ansible | Agentless configuration management tool using YAML playbooks |
| Ansible Inventory | Contains host and group information for Ansible to target systems |
| Ansible Playbook | YAML file defining tasks to automate and manage configuration |
| ARM Template Deployment Scope | Target resource group, subscription, or management group for deployment |
| ARM Template Linked Templates | Enables referencing separate templates for modular deployment |
| ARM Template Parameters | Allow customizing deployment through input values |
| ARM Templates | Declarative JSON files for Azure resources |
| Chef | Configuration management tool using Ruby-based DSL |
| Chef Cookbook | Collection of recipes and associated files for system management |
| Chef Recipes | Defines configuration logic using Ruby code for resources |
| Configuration Management | Process of maintaining system configurations consistently |
| Dynamic Inventory in Ansible | Automatically generates inventory from cloud or external sources |
| idempotency in Configuration Management | Ensures operations result in the same state regardless of initial conditions |
| Immutable Infrastructure | Infrastructure that cannot be modified after deployment |
| Infrastructure as Code | Automates provisioning and managing infrastructure using code |
| Modules in Terraform | Reusable components to organize and simplify Terraform code |
| Pull-based Configuration Management | Central system pushes configuration to target systems as in Ansible |
| Push-based Configuration Management | Client retrieves configuration from central server as in Chef |
| State Drift | When actual infrastructure diverges from declared IaC |
| Terraform | Open-source IaC tool supporting multiple cloud providers |
| Terraform HCL Syntax | Human-readable configuration language used by Terraform |
| Terraform Output Variables | Provide results from applied configurations for use elsewhere |
| Terraform Plan | Command to preview changes before applying configuration |
| Terraform Providers | Plugins that interact with APIs for configuring resources |
| Terraform Remote State | Stores state in a shared backend for team collaboration |
| Terraform State File | Stores mapping of real infrastructure resources to Terraform configuration |
| Terraform Workspaces | Isolated environments within a single configuration |
| Versioning in IaC | Tracks infrastructure changes over time for auditing and rollback |
About the Flashcards
Flashcards for the Microsoft DevOps Engineer Expert exam explore Infrastructure as Code essentials, highlighting how tools like Terraform, Azure ARM templates, Ansible, and Chef automate resource provisioning and configuration. Each card reinforces declarative syntax, module reuse, and the advantages of immutable infrastructure so you can answer exam questions with confidence.
The deck also helps you master state files, workspace isolation, idempotent operations, and version control practices that prevent configuration drift. Reviewing these concise definitions and use-case notes sharpens recall of key commands, parameters, and workflows likely to appear on exam day.
Topics covered in this flashcard deck:
- Infrastructure as Code principles
- Terraform language & state
- Azure ARM templates
- Ansible playbooks & inventory
- Chef recipes & cookbooks
- Configuration drift & versioning