What is Infrastructure as Code in Terraform - Quick Revision & Key Takeaways

Recall & Review

beginner

What does Infrastructure as Code (IaC) mean?

IaC means managing and provisioning computer infrastructure using code instead of manual setup. It helps automate and repeat infrastructure tasks.

beginner

Why is Infrastructure as Code useful?

IaC makes infrastructure setup faster, consistent, and less error-prone by using code to define resources. It also allows easy version control and collaboration.

beginner

Name a popular tool used for Infrastructure as Code.

Terraform is a popular IaC tool that lets you write code to create and manage cloud resources safely and efficiently.

intermediate

How does Infrastructure as Code improve teamwork?

IaC stores infrastructure setup as code files that teams can share, review, and update together, improving communication and reducing mistakes.

beginner

What is a key difference between manual infrastructure setup and IaC?

Manual setup is done by hand on each machine, which can be slow and inconsistent. IaC uses code to automate setup, making it fast and repeatable.

What is the main purpose of Infrastructure as Code?

A To write code that manages infrastructure automatically

B To manually configure servers one by one

C To design user interfaces for cloud apps

D To store data in databases

IaC automates infrastructure management by using code to define and provision resources.

Which tool is commonly used for Infrastructure as Code?

A Terraform

B Excel

C Photoshop

D Slack

Terraform is a popular IaC tool for managing cloud infrastructure.

What is a benefit of using Infrastructure as Code?

A Slower setup times

B More manual errors

C Inconsistent environments

D Easier collaboration and version control

IaC improves collaboration by storing infrastructure as code that teams can share and update.

Infrastructure as Code helps to make infrastructure setup:

A Manual and error-prone

B Only for small projects

C Fast and repeatable

D Random and unpredictable

IaC automates setup making it fast and consistent every time.

Which of these is NOT true about Infrastructure as Code?

A It uses code to manage infrastructure

B It requires manual clicking on cloud consoles

C It allows version control of infrastructure

D It reduces human errors

IaC avoids manual clicking by automating infrastructure setup with code.

Explain Infrastructure as Code and why it is important.

Think about how writing code can replace manual setup.

Describe how Infrastructure as Code helps teams work better together.

Consider how code can be reviewed and updated by multiple people.

Practice

1. What does Infrastructure as Code mean in simple terms?

easy

A. Using physical servers instead of cloud

B. Manually clicking buttons in the cloud console

C. Writing text files to create and manage cloud resources

D. Writing code only for applications, not infrastructure

Solution

1. Step 1: Understand the concept of Infrastructure as Code

   It means using code or text files to define and manage infrastructure instead of manual steps.

2. Step 2: Compare options with this definition

   Only Writing text files to create and manage cloud resources describes writing text files to manage cloud resources, matching the concept.

3. Final Answer:

   Writing text files to create and manage cloud resources -> Option C

4. Quick Check:

   Infrastructure as Code = writing text files [OK]

Hint: Think: code controls infrastructure, not manual clicks [OK]

Common Mistakes:

• Confusing manual setup with code-based setup
• Thinking Infrastructure as Code means only coding apps
• Assuming physical servers are Infrastructure as Code

2. Which of these is a correct Terraform resource block syntax?

easy

A. resource "aws_instance" "web" { ami = "ami-123" instance_type = "t2.micro" }

B. resource aws_instance web { ami = ami-123 instance_type = t2.micro }

C. resource "aws_instance" web { ami = "ami-123" instance_type = "t2.micro" }

D. resource "aws_instance" "web" ( ami = "ami-123", instance_type = "t2.micro" )

Solution

1. Step 1: Recall Terraform resource block syntax

   It requires the keyword resource, resource type and name in quotes, then braces with key-value pairs.

2. Step 2: Check each option for correct syntax

   resource "aws_instance" "web" { ami = "ami-123" instance_type = "t2.micro" } uses quotes for type and name, braces, and key-value pairs with equals and quotes correctly.

3. Final Answer:

   resource "aws_instance" "web" { ami = "ami-123" instance_type = "t2.micro" } -> Option A

4. Quick Check:

   Correct Terraform resource syntax = resource "aws_instance" "web" { ami = "ami-123" instance_type = "t2.micro" } [OK]

Hint: Look for quotes around type and name, and braces {} [OK]

Common Mistakes:

• Missing quotes around resource type or name
• Using parentheses instead of braces
• Not quoting string values

3. Given this Terraform snippet:

resource "aws_s3_bucket" "bucket" {
  bucket = "my-bucket"
  acl    = "private"
}

What will Terraform do when applied?

medium

A. Create a public S3 bucket named 'my-bucket'

B. Throw a syntax error due to missing region

C. Delete the S3 bucket named 'my-bucket'

D. Create a private S3 bucket named 'my-bucket'

Solution

1. Step 1: Analyze the resource block

   The resource defines an AWS S3 bucket named 'my-bucket' with ACL set to 'private'.

2. Step 2: Understand the effect of ACL 'private'

   This means the bucket will be created with private access, not public.

3. Final Answer:

   Create a private S3 bucket named 'my-bucket' -> Option D

4. Quick Check:

   ACL 'private' means private bucket [OK]

Hint: ACL 'private' means bucket is not public [OK]

Common Mistakes:

• Assuming default is public
• Thinking missing region causes syntax error
• Confusing create with delete actions

4. This Terraform code has an error:

resource "aws_instance" "web" {
  ami = "ami-123"
  instance_type = t2.micro
}

What is the error?

medium

A. Missing resource name

B. Missing quotes around instance_type value

C. Wrong resource type

D. Missing equals sign after ami

Solution

1. Step 1: Check the instance_type line

   The value t2.micro is not in quotes, but it should be a string.

2. Step 2: Confirm correct syntax for string values

   Terraform requires string values to be in quotes, so missing quotes cause an error.

3. Final Answer:

   Missing quotes around instance_type value -> Option B

4. Quick Check:

   String values need quotes in Terraform [OK]

Hint: String values always need quotes in Terraform [OK]

Common Mistakes:

• Forgetting quotes around string values
• Thinking resource name is missing
• Assuming equals sign is missing

5. You want to create two identical AWS EC2 instances using Terraform without repeating code. Which feature helps you do this efficiently?

hard

A. Using a for_each or count loop in the resource block

B. Manually copying the resource block twice

C. Writing separate Terraform files for each instance

D. Using different resource types for each instance

Solution

1. Step 1: Understand the goal to avoid repetition

   We want to create multiple similar resources without copying code.

2. Step 2: Identify Terraform features for repetition

   Terraform supports 'count' and 'for_each' to create multiple instances from one block.

3. Step 3: Evaluate options

   Using a for_each or count loop in the resource block uses these features, while others involve manual repetition or incorrect methods.

4. Final Answer:

   Using a for_each or count loop in the resource block -> Option A

5. Quick Check:

   Loops in Terraform = efficient resource creation [OK]

Hint: Use count or for_each to repeat resources without copy-paste [OK]

Common Mistakes:

• Copy-pasting resource blocks manually
• Creating separate files unnecessarily
• Using different resource types for same resource