Bash, the Crucial Exams Chat Bot
AI Bot
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 |
Front
Chef Recipes
Click the card to flip
Back
Defines configuration logic using Ruby code for resources
Front
Ansible
Back
Agentless configuration management tool using YAML playbooks
Front
Terraform Plan
Back
Command to preview changes before applying configuration
Front
Terraform Workspaces
Back
Isolated environments within a single configuration
Front
Chef
Back
Configuration management tool using Ruby-based DSL
Front
Pull-based Configuration Management
Back
Central system pushes configuration to target systems as in Ansible
Front
Advantages of Declarative IaC
Back
Simplifies infrastructure description by focusing on end states
Front
Terraform State File
Back
Stores mapping of real infrastructure resources to Terraform configuration
Front
Modules in Terraform
Back
Reusable components to organize and simplify Terraform code
Front
Terraform Providers
Back
Plugins that interact with APIs for configuring resources
Front
ARM Template Parameters
Back
Allow customizing deployment through input values
Front
Dynamic Inventory in Ansible
Back
Automatically generates inventory from cloud or external sources
Front
ARM Template Deployment Scope
Back
Target resource group, subscription, or management group for deployment
Front
Terraform
Back
Open-source IaC tool supporting multiple cloud providers
Front
Immutable Infrastructure
Back
Infrastructure that cannot be modified after deployment
Front
Versioning in IaC
Back
Tracks infrastructure changes over time for auditing and rollback
Front
ARM Templates
Back
Declarative JSON files for Azure resources
Front
Configuration Management
Back
Process of maintaining system configurations consistently
Front
Advantages of IaC
Back
Scalability, repeatability, and version control for infrastructure
Front
Chef Cookbook
Back
Collection of recipes and associated files for system management
Front
Ansible Playbook
Back
YAML file defining tasks to automate and manage configuration
Front
ARM Template Linked Templates
Back
Enables referencing separate templates for modular deployment
Front
idempotency in Configuration Management
Back
Ensures operations result in the same state regardless of initial conditions
Front
State Drift
Back
When actual infrastructure diverges from declared IaC
Front
Terraform HCL Syntax
Back
Human-readable configuration language used by Terraform
Front
Push-based Configuration Management
Back
Client retrieves configuration from central server as in Chef
Front
Infrastructure as Code
Back
Automates provisioning and managing infrastructure using code
Front
Terraform Remote State
Back
Stores state in a shared backend for team collaboration
Front
Ansible Inventory
Back
Contains host and group information for Ansible to target systems
Front
Terraform Output Variables
Back
Provide results from applied configurations for use elsewhere
1/30
This deck explains automating infrastructure deployment using ARM templates, Terraform, and managing configuration with tools like Chef or Ansible.