Terraform Cloud overview - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Terraform Cloud?

Terraform Cloud is a service that helps teams use Terraform together by managing infrastructure as code in a shared, secure, and automated way.

beginner

Name one key benefit of using Terraform Cloud.

It provides a central place to run Terraform plans and applies, so teams avoid conflicts and mistakes when changing infrastructure.

beginner

What does Terraform Cloud use to store your infrastructure state safely?

Terraform Cloud stores the state file remotely and securely, so it is shared and protected from accidental loss or corruption.

intermediate

How does Terraform Cloud help with team collaboration?

It provides role-based access control, shared workspaces, and notifications to keep everyone informed and working safely together.

beginner

What is a workspace in Terraform Cloud?

A workspace is a container for your Terraform configuration, state, and runs. It helps organize and isolate infrastructure environments.

What is the main purpose of Terraform Cloud?

A To replace Terraform CLI completely

B To manage infrastructure as code collaboratively

C To host websites

D To store Docker images

Terraform Cloud helps teams manage infrastructure as code together, not to replace the CLI or host unrelated services.

Where does Terraform Cloud store the Terraform state file?

A In a remote, secure backend

B Locally on your computer

C On a public website

D In a text email

Terraform Cloud stores state files remotely and securely to share and protect them.

Which feature helps teams avoid conflicting changes in Terraform Cloud?

A Role-based access control

B Email alerts only

C Shared workspaces

D Manual file sharing

Shared workspaces organize infrastructure and prevent conflicts by controlling who can change what.

What is a Terraform Cloud workspace used for?

A Storing images

B Writing code in any language

C Running virtual machines

D Organizing Terraform configurations and state

Workspaces hold Terraform configurations and state to keep environments organized.

How does Terraform Cloud improve security for infrastructure management?

A By encrypting state files and controlling user access

B By allowing anyone to edit state files

C By storing passwords in plain text

D By disabling all access controls

Terraform Cloud encrypts sensitive data and uses access controls to keep infrastructure safe.

Explain how Terraform Cloud helps teams work together on infrastructure.

Think about how teams avoid conflicts and keep infrastructure safe.

Describe what a workspace is in Terraform Cloud and why it is useful.

Imagine a workspace as a folder for your infrastructure code and data.

Practice

1. What is the main purpose of Terraform Cloud?

easy

A. To host websites built with Terraform

B. To replace Terraform CLI on your local machine

C. To store Terraform state remotely and run Terraform commands safely

D. To provide a graphical interface for writing Terraform code

Solution

1. Step 1: Understand Terraform Cloud's role

   Terraform Cloud stores state files remotely and runs Terraform commands in a managed environment.

2. Step 2: Compare options with this role

   Only To store Terraform state remotely and run Terraform commands safely correctly describes this purpose; others describe unrelated functions.

3. Final Answer:

   To store Terraform state remotely and run Terraform commands safely -> Option C

4. Quick Check:

   Terraform Cloud = Remote state + safe runs [OK]

Hint: Remember Terraform Cloud manages state and runs commands remotely [OK]

Common Mistakes:

• Thinking Terraform Cloud replaces local CLI
• Confusing Terraform Cloud with a code editor
• Assuming Terraform Cloud hosts websites

2. Which Terraform configuration block connects your code to Terraform Cloud?

easy

A. terraform { backend "cloud" { ... } }

B. terraform { cloud { organization = "org" } }

C. provider "cloud" { organization = "org" }

D. resource "cloud" { organization = "org" }

Solution

1. Step 1: Identify the correct block for Terraform Cloud

   The terraform { cloud { ... } } block is used to configure Terraform Cloud settings.

2. Step 2: Check other options for correctness

   terraform { backend "cloud" { ... } } uses backend "cloud" which is invalid; provider and resource blocks are unrelated.

3. Final Answer:

   terraform { cloud { organization = "org" } } -> Option B

4. Quick Check:

   Cloud config = terraform block with cloud [OK]

Hint: Look for terraform { cloud { ... } } syntax [OK]

Common Mistakes:

• Using backend "cloud" instead of cloud block
• Confusing provider or resource blocks with cloud config
• Missing the organization attribute inside cloud block

3. Given this Terraform snippet, what happens when you run terraform apply?

terraform {
  cloud {
    organization = "my-org"
    workspaces {
      name = "my-workspace"
    }
  }
}

medium

A. Terraform ignores the cloud block and runs with default settings

B. Terraform runs locally and stores state on your machine

C. Terraform throws a syntax error due to missing backend block

D. Terraform connects to Terraform Cloud and uses the specified workspace

Solution

1. Step 1: Analyze the cloud block configuration

   The cloud block specifies organization and workspace, so Terraform connects to Terraform Cloud.

2. Step 2: Understand Terraform apply behavior with cloud config

   Terraform runs remotely using the workspace and stores state in Terraform Cloud.

3. Final Answer:

   Terraform connects to Terraform Cloud and uses the specified workspace -> Option D

4. Quick Check:

   Cloud block present = remote run in workspace [OK]

Hint: Presence of cloud block means remote run in Terraform Cloud [OK]

Common Mistakes:

• Assuming local run despite cloud block
• Expecting syntax error without backend block
• Ignoring workspace setting in cloud block

4. You added this block to your Terraform config but get an error:

terraform {
  cloud {
    organization = "my-org"
  }
}

What is the likely cause?

medium

A. Missing workspace configuration inside the cloud block

B. Incorrect organization name format

C. Terraform Cloud requires a backend block instead

D. The cloud block must be inside a provider block

Solution

1. Step 1: Check required fields in cloud block

   Terraform Cloud requires workspace info inside the cloud block to know where to store state.

2. Step 2: Identify missing workspace causes error

   Without workspace, Terraform cannot connect properly, causing an error.

3. Final Answer:

   Missing workspace configuration inside the cloud block -> Option A

4. Quick Check:

   Cloud block needs workspace info [OK]

Hint: Always include workspace inside cloud block [OK]

Common Mistakes:

• Assuming organization name format is wrong
• Thinking backend block is mandatory with cloud block
• Placing cloud block inside provider block

5. You want to share Terraform state safely among your team using Terraform Cloud. Which steps should you take to set this up correctly?

hard

A. Configure terraform { cloud { organization = "org" workspaces { name = "ws" } } } and push code to VCS connected to Terraform Cloud

B. Run Terraform locally and manually upload state files to Terraform Cloud

C. Use a local backend and share the state file via email with your team

D. Configure a provider block for Terraform Cloud and run terraform init locally

Solution

1. Step 1: Set up Terraform Cloud connection in config

   Use the terraform { cloud { ... } } block with organization and workspace to connect to Terraform Cloud.

2. Step 2: Integrate with version control system (VCS)

   Push your Terraform code to a VCS repository linked to Terraform Cloud for automated runs and shared state.

3. Final Answer:

   Configure terraform { cloud { organization = "org" workspaces { name = "ws" } } } and push code to VCS connected to Terraform Cloud -> Option A

4. Quick Check:

   Cloud block + VCS = safe shared state [OK]

Hint: Use cloud block and VCS integration for team state sharing [OK]

Common Mistakes:

• Uploading state files manually instead of using Terraform Cloud
• Sharing state files via email (unsafe and error-prone)
• Misusing provider block for Terraform Cloud connection