Why IaC matters in GCP - Visual Breakdown

Process Flow - Why IaC matters

Write Infrastructure Code

↓

Run Code to Create Resources

↓

Cloud Provider Builds Resources

↓

Resources Ready to Use

↓

Manage & Update by Changing Code

↓

Repeat: Code Controls Infrastructure

Infrastructure as Code means writing code to create and manage cloud resources automatically, making setup and updates easy and consistent.

Execution Sample

GCP

resource "google_compute_instance" "vm1" {
  name         = "vm-instance"
  machine_type = "e2-medium"
  zone         = "us-central1-a"
  boot_disk {
    initialize_params {
      image = "debian-cloud/debian-10"
    }
  }
  network_interface {
    network = "default"
    access_config {}
  }
}

This code defines a virtual machine instance in GCP that will be created automatically when applied.

Process Table

Step	Action	Code Evaluation	Result
1	Parse IaC code	Read resource block	Recognize VM instance definition
2	Send request to GCP	Create VM with name 'vm-instance'	VM creation started
3	GCP provisions VM	Allocate machine type e2-medium in zone us-central1-a	VM is created and running
4	Confirm resource state	Check VM status	VM is ready to use
5	Update code	Change machine_type to e2-standard-2	Prepare update plan
6	Apply update	Send update request to GCP	VM machine type updated
7	Verify update	Check VM machine type	VM runs with new machine type
8	End	No more changes	Infrastructure matches code

💡 All infrastructure resources are created and managed by code, ensuring consistency and easy updates.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	Final
VM Instance	undefined	creation requested	running with e2-medium	updated to e2-standard-2	running with e2-standard-2

Key Moments - 2 Insights

Why do we write code instead of manually creating resources in the cloud?

Writing code lets us create and update resources automatically and consistently, as shown in execution_table steps 1 to 4, avoiding manual errors.

How does changing the code update the cloud resources?

Changing the code triggers an update plan and applies changes to the cloud, as seen in steps 5 to 7, keeping infrastructure in sync with code.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the state of the VM instance?

A VM is running with machine type e2-medium

B VM is stopped

C VM creation requested but not started

D VM machine type is e2-standard-2

💡 Hint

Check the 'Result' column at step 3 in execution_table.

At which step does the VM machine type get updated?

A Step 4

B Step 6

C Step 5

D Step 7

💡 Hint

Look for 'Apply update' action in execution_table.

If we skip step 5 (update code), what happens to the VM machine type?

A VM is deleted

B It changes to e2-standard-2 anyway

C It stays as e2-medium

D VM machine type becomes undefined

💡 Hint

Refer to variable_tracker and see how machine type changes only after step 5 and 6.

Concept Snapshot

IaC means writing code to create and manage cloud resources.
Run the code to build resources automatically.
Change code to update resources safely.
Keeps infrastructure consistent and repeatable.
Avoids manual setup errors and saves time.

Full Transcript

Infrastructure as Code (IaC) lets you write code to create and manage cloud resources instead of doing it manually. When you run the code, the cloud provider builds the resources for you. If you want to change something, you update the code and run it again. The cloud updates the resources to match your code. This way, your infrastructure is always consistent, easy to manage, and less error-prone.

Practice

1. Why is Infrastructure as Code (IaC) important when working with cloud environments like GCP?

easy

A. It requires manual configuration every time.

B. It makes cloud setup faster and repeatable.

C. It only works for small projects.

D. It replaces the need for cloud security.

Solution

1. Step 1: Understand IaC benefits

   IaC automates cloud setup, making it faster and consistent each time.

2. Step 2: Compare options

   Manual setup is slow and error-prone; IaC is designed for repeatability and speed.

3. Final Answer:

   It makes cloud setup faster and repeatable. -> Option B

4. Quick Check:

   IaC speeds up setup = A [OK]

Hint: IaC automates setup for speed and consistency [OK]

Common Mistakes:

• Thinking IaC requires manual setup each time
• Believing IaC only suits small projects
• Confusing IaC with security tools

2. Which of the following is the correct way to define a simple Google Cloud Storage bucket using Terraform (an IaC tool)?

easy

A. resource "google_storage_bucket" "my_bucket" { name = "my-bucket" location = "US" }

B. resource google_storage_bucket my_bucket { name: "my-bucket" location: "US" }

C. resource "google_storage_bucket" my_bucket { name = "my-bucket" location = "US" }

D. resource "google_storage_bucket" "my_bucket" ( name = "my-bucket" location = "US" )

Solution

1. Step 1: Check Terraform resource syntax

   Terraform uses resource "type" "name" { ... } with key = value pairs inside braces.

2. Step 2: Identify correct syntax

   resource "google_storage_bucket" "my_bucket" { name = "my-bucket" location = "US" } matches this syntax exactly; others have wrong punctuation or missing quotes.

3. Final Answer:

   resource "google_storage_bucket" "my_bucket" { name = "my-bucket" location = "US" } -> Option A

4. Quick Check:

   Terraform resource syntax uses quotes and braces = B [OK]

Hint: Terraform resource blocks need quotes and braces [OK]

Common Mistakes:

• Omitting quotes around resource type or name
• Using colons instead of equals
• Using parentheses instead of braces

3. Given this Terraform snippet for a Google Compute Engine instance:

resource "google_compute_instance" "vm_instance" {
  name         = "test-vm"
  machine_type = "e2-medium"
  zone         = "us-central1-a"
  boot_disk {
    initialize_params {
      image = "debian-cloud/debian-11"
    }
  }
  network_interface {
    network = "default"
  }
}

What will happen when you run terraform apply with this configuration?

medium

A. The VM will be created but without a boot disk.

B. Terraform will throw a syntax error due to missing project ID.

C. Terraform will create a VM in the default zone instead of us-central1-a.

D. A new VM named 'test-vm' with e2-medium machine type will be created in us-central1-a.

Solution

1. Step 1: Analyze the Terraform resource

   The resource defines a VM named 'test-vm' with machine type 'e2-medium' in zone 'us-central1-a' and a boot disk with Debian 11 image.

2. Step 2: Understand Terraform behavior

   Terraform will create the VM as specified; project ID is optional if set in provider config, and boot disk is defined properly.

3. Final Answer:

   A new VM named 'test-vm' with e2-medium machine type will be created in us-central1-a. -> Option D

4. Quick Check:

   Defined VM config matches creation = C [OK]

Hint: Check resource fields and defaults carefully [OK]

Common Mistakes:

• Assuming missing project ID causes error
• Thinking boot disk is optional without explicit flag
• Ignoring specified zone in config

4. You wrote this Terraform code to create a Google Cloud Storage bucket:

resource "google_storage_bucket" "bucket1" {
  name = "my-bucket"
  location = "us-central1"
  versioning {
    enabled = true
  }
  versioning = true
}

Why does Terraform fail to apply this configuration?

medium

A. The 'versioning' block and 'versioning' attribute conflict causing an error.

B. Bucket name 'my-bucket' is invalid in GCP.

C. Location 'us-central1' is not supported for buckets.

D. Terraform requires a 'storage_class' attribute which is missing.

Solution

1. Step 1: Identify conflicting versioning definitions

   The code has both a 'versioning' block with 'enabled = true' and a 'versioning' attribute set to true, which conflicts.

2. Step 2: Understand Terraform schema rules

   Terraform expects either a versioning block or attribute, not both; this causes a configuration error.

3. Final Answer:

   The 'versioning' block and 'versioning' attribute conflict causing an error. -> Option A

4. Quick Check:

   Conflicting versioning definitions cause error = D [OK]

Hint: Avoid duplicate keys or blocks in Terraform config [OK]

Common Mistakes:

• Assuming bucket name is invalid without checking rules
• Thinking location is unsupported without evidence
• Believing missing storage_class always causes error

5. You want to ensure your GCP environment can be recreated exactly after a disaster. Which IaC practice best supports this goal?

hard

A. Use different tools each time to test flexibility.

B. Manually configure resources in the console and document steps in a text file.

C. Write and store Terraform code defining all resources, then use version control.

D. Create resources manually but take screenshots for reference.

Solution

1. Step 1: Identify best disaster recovery IaC practice

   Using code (Terraform) to define resources ensures exact recreation and easy tracking.

2. Step 2: Compare other options

   Manual steps or screenshots are error-prone and not repeatable; changing tools reduces consistency.

3. Final Answer:

   Write and store Terraform code defining all resources, then use version control. -> Option C

4. Quick Check:

   Code + version control = reliable recreation = A [OK]

Hint: Store IaC code in version control for exact rebuilds [OK]

Common Mistakes:

• Relying on manual steps or screenshots
• Changing tools frequently causing inconsistency
• Ignoring version control benefits