Why IaC over manual provisioning in Terraform - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a resource in Terraform.

Terraform

resource "aws_instance" "example" {
  ami           = "ami-12345678"
  instance_type = "[1]"
}

Drag options to blanks, or click blank then click option'

At2.nano

Bt2.small

Ct2.medium

Dt2.micro

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid instance type string.

Leaving the instance_type blank.

The instance_type specifies the size of the instance. "t2.micro" is a valid and common choice.

2fill in blank

medium

Complete the code to initialize Terraform in your project directory.

Terraform

terraform [1]

Drag options to blanks, or click blank then click option'

Ainit

Bdestroy

Cplan

Dapply

Attempts:

3 left

💡 Hint

Common Mistakes

Using terraform apply before initialization.

Confusing init with plan or apply.

terraform init initializes the working directory containing Terraform configuration files.

3fill in blank

hard

Fix the error in the Terraform code to output the instance's public IP.

Terraform

output "instance_ip" {
  value = aws_instance.example.[1]
}

Drag options to blanks, or click blank then click option'

Apublic_ip

Bprivate_ip

Cip_address

Dinstance_ip

Attempts:

3 left

💡 Hint

Common Mistakes

Using private_ip instead of public_ip.

Using a non-existent attribute like ip_address.

The correct attribute to get the public IP of an AWS instance is public_ip.

4fill in blank

hard

Fill both blanks to create a variable with a default value in Terraform.

Terraform

variable "region" {
  type    = [1]
  default = [2]
}

Drag options to blanks, or click blank then click option'

Astring

B"us-west-2"

C"number"

D"eu-central-1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using number type for a region variable.

Setting default to an unsupported region string.

The variable type is string and the default region is "us-west-2".

5fill in blank

hard

Fill all three blanks to create a resource with tags in Terraform.

Terraform

resource "aws_s3_bucket" "bucket" {
  bucket = [1]
  acl    = [2]
  tags = {
    Name        = [3]
  }
}

Drag options to blanks, or click blank then click option'

A"my-unique-bucket-123"

B"private"

C"MyBucket"

D"public-read"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-unique bucket name.

Setting acl to "public-read" without intention.

Omitting tags or using incorrect syntax.

The bucket name must be unique, acl is set to "private" for security, and tags include a friendly name.

Practice

1. Why is Infrastructure as Code (IaC) preferred over manual cloud provisioning?

easy

A. Manual provisioning tracks changes automatically.

B. Manual provisioning is faster for large-scale deployments.

C. IaC requires no knowledge of cloud services.

D. IaC automates setup, saving time and reducing human errors.

Solution

1. Step 1: Understand automation benefits of IaC

   IaC automates cloud setup, which reduces manual work and human mistakes.

2. Step 2: Compare manual provisioning drawbacks

   Manual provisioning is slower and prone to errors, especially at scale.

3. Final Answer:

   IaC automates setup, saving time and reducing human errors. -> Option D

4. Quick Check:

   Automation = IaC advantage [OK]

Hint: IaC automates and reduces errors, unlike manual steps [OK]

Common Mistakes:

• Thinking manual is faster for big setups
• Believing IaC needs no cloud knowledge
• Assuming manual tracks changes automatically

2. Which Terraform command applies your infrastructure code to create resources?

easy

A. terraform apply

B. terraform plan

C. terraform init

D. terraform destroy

Solution

1. Step 1: Identify command to create resources

   terraform apply runs the code and creates or updates infrastructure.

2. Step 2: Differentiate from other commands

   terraform plan shows changes, init sets up, destroy deletes resources.

3. Final Answer:

   terraform apply -> Option A

4. Quick Check:

   Apply = create/update resources [OK]

Hint: Apply means execute changes to infrastructure [OK]

Common Mistakes:

• Confusing plan with apply
• Using init to create resources
• Destroying instead of applying

3. Given this Terraform snippet, what is the main benefit of using it instead of manual setup?

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

medium

A. It automatically tracks and applies changes to the instance.

B. It requires manual steps to launch the instance.

C. It disables version control for infrastructure.

D. It prevents reuse of the configuration.

Solution

1. Step 1: Understand Terraform resource block

   This block defines an AWS instance that Terraform can create and manage automatically.

2. Step 2: Compare with manual setup

   Manual setup requires clicking or scripting outside Terraform, no automatic tracking or updates.

3. Final Answer:

   It automatically tracks and applies changes to the instance. -> Option A

4. Quick Check:

   Automatic tracking = IaC benefit [OK]

Hint: Terraform tracks changes; manual does not [OK]

Common Mistakes:

• Thinking manual steps are needed with Terraform
• Believing Terraform disables version control
• Assuming config cannot be reused

4. You wrote Terraform code but it fails to update your cloud resources. What is a common reason for this?

medium

A. Manual provisioning is required after every change.

B. You forgot to run terraform apply after changes.

C. Terraform does not support updating resources.

D. Terraform automatically updates without commands.

Solution

1. Step 1: Identify Terraform workflow

   After editing code, you must run terraform apply to update resources.

2. Step 2: Eliminate incorrect options

   Terraform supports updates but needs apply; manual provisioning is not needed after changes; updates are not automatic without commands.

3. Final Answer:

   You forgot to run terraform apply after changes. -> Option B

4. Quick Check:

   Apply runs updates [OK]

Hint: Always run terraform apply to update resources [OK]

Common Mistakes:

• Assuming Terraform updates automatically
• Thinking manual steps are needed after code changes
• Believing Terraform cannot update resources

5. How does using Terraform as IaC help teams fix problems faster compared to manual provisioning?

hard

A. Manual provisioning is faster to fix because it uses GUIs.

B. Manual provisioning automatically logs all changes for easy fixes.

C. Terraform code is reusable and tracks changes, making troubleshooting easier.

D. Terraform requires no collaboration, so fewer errors occur.

Solution

1. Step 1: Understand Terraform's tracking and reusability

   Terraform stores infrastructure as code, enabling version control and easy sharing.

2. Step 2: Compare with manual provisioning challenges

   Manual provisioning lacks automatic tracking and is harder to reproduce or fix consistently.

3. Final Answer:

   Terraform code is reusable and tracks changes, making troubleshooting easier. -> Option C

4. Quick Check:

   Tracking + reuse = faster fixes [OK]

Hint: Code tracks changes and is reusable for quick fixes [OK]

Common Mistakes:

• Believing manual provisioning logs changes automatically
• Thinking Terraform needs no teamwork
• Assuming GUIs are always faster to fix problems