Infrastructure as Code Flashcards

What is the primary purpose of Infrastructure as Code (IaC)?

Answer: Automating infrastructure provisioning and management.

Infrastructure as Code (IaC) is a practice that defines and manages infrastructure resources using machine-readable definition files, rather than manual configuration. Its primary purpose is to automate the provisioning, configuration, and management of servers, networks, and other infrastructure components. This automation ensures consistency, reduces human error, and enables faster, repeatable deployments.

Which of the following is a key benefit of using IaC?

Answer: Automated and consistent infrastructure deployment.

A key benefit of Infrastructure as Code (IaC) is the ability to achieve automated and consistent infrastructure deployment. By defining infrastructure in code, organizations can version control, test, and deploy environments repeatedly with identical configurations. This eliminates configuration drift and human error, leading to more reliable and predictable infrastructure.

Which tool is commonly used for IaC to provision infrastructure across multiple cloud providers?

Answer: Terraform

Terraform is a widely used open-source Infrastructure as Code (IaC) tool that allows users to define and provision infrastructure using a declarative configuration language. Its key strength lies in its provider-agnostic nature, enabling it to manage resources across numerous cloud providers (like AWS, Azure, GCP) and on-premises environments from a single workflow. This makes it ideal for multi-cloud strategies.

What is a declarative approach in IaC?

Answer: Describing the desired end state of the infrastructure.

A declarative approach in Infrastructure as Code (IaC) means that you describe the desired end state of your infrastructure, rather than specifying the exact sequence of steps to achieve it. The IaC tool then intelligently determines the necessary actions to bring the current infrastructure to that specified desired state. This simplifies configuration management and makes infrastructure definitions more readable.

Which of the following is NOT an IaC tool?

Answer: Photoshop

Ansible, Chef, and Puppet are all prominent Infrastructure as Code (IaC) tools used for configuration management and automation of IT infrastructure. Photoshop, on the other hand, is a widely known image editing and graphic design software. Therefore, Photoshop is not an IaC tool.

What is the primary advantage of version controlling infrastructure code?

Answer: Ability to track changes and collaborate effectively.

Version controlling infrastructure code, typically using systems like Git, provides a comprehensive history of all changes made to the infrastructure. This enables teams to track who made what changes, when, and why, facilitating effective collaboration among multiple engineers. It also allows for easy rollbacks to previous stable configurations, enhancing reliability and auditability.

In IaC, what does 'idempotency' refer to?

Answer: Applying the same configuration yields the same result every time.

In Infrastructure as Code (IaC), 'idempotency' refers to the property that applying the same configuration or operation multiple times will consistently yield the exact same result as the first application. This means that IaC tools can be run repeatedly without causing unintended side effects or errors, ensuring that the infrastructure always converges to the desired state reliably.

Which language is primarily used to write Terraform configuration files?

Answer: HCL

Terraform primarily uses HashiCorp Configuration Language (HCL) for writing its configuration files. HCL is a declarative language designed to be human-readable and machine-friendly, making it intuitive to define infrastructure resources and their desired state. While it supports JSON, HCL is the native and preferred language for Terraform configurations.

What is the role of 'modules' in Terraform?

Answer: They enable code reuse and organization.

In Terraform, 'modules' are self-contained, reusable configurations that encapsulate a set of infrastructure resources. Their primary role is to enable code reuse, allowing developers to define common infrastructure patterns once and apply them across multiple projects or environments. Modules also help organize complex configurations, making them more manageable and readable.