Terraform Cloud/Enterprise features - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Terraform Cloud?

Terraform Cloud is a service that helps teams use Terraform together by managing state, runs, and providing collaboration features in a secure way.

beginner

Explain the purpose of 'Workspaces' in Terraform Cloud.

Workspaces in Terraform Cloud isolate state and runs for different infrastructure environments or projects, helping organize and manage infrastructure safely.

intermediate

What is the role of 'Sentinel' in Terraform Enterprise?

Sentinel is a policy-as-code framework in Terraform Enterprise that lets you write rules to enforce compliance and governance before applying infrastructure changes.

beginner

How does Terraform Cloud handle state management?

Terraform Cloud securely stores the Terraform state file remotely, preventing conflicts and enabling team collaboration without manual state file sharing.

intermediate

What is the purpose of 'Run Triggers' in Terraform Cloud?

Run Triggers automatically start Terraform runs in one workspace when runs complete in another, helping coordinate changes across related infrastructure components.

Which feature in Terraform Enterprise allows you to enforce rules on infrastructure changes before applying them?

A Workspaces

B Sentinel

C Run Triggers

D Remote State

Sentinel is the policy-as-code framework used to enforce rules and compliance in Terraform Enterprise.

What does a Terraform Cloud workspace primarily manage?

A State and runs for a specific infrastructure environment

B User permissions only

C Billing and account settings

D Terraform CLI installation

Workspaces isolate state and runs for different infrastructure environments or projects.

How does Terraform Cloud improve team collaboration?

A By sharing local state files via email

B By disabling concurrent runs

C By requiring manual approval for every command

D By storing state remotely and managing runs centrally

Terraform Cloud stores state remotely and manages runs, enabling safe team collaboration.

What is the function of Run Triggers in Terraform Cloud?

A To automatically start runs in one workspace after another completes

B To backup state files

C To send notifications on run failures

D To schedule runs at fixed times

Run Triggers automate runs in dependent workspaces after a run completes.

Which Terraform Cloud feature helps secure sensitive variables and credentials?

A Remote State

B Sentinel

C Variable Sets

D Workspaces

Variable Sets securely store and share sensitive variables across workspaces.

Describe how Terraform Cloud manages state and why this is important for teams.

Think about how sharing files manually can cause problems for teams.

Explain the role of Sentinel policies in Terraform Enterprise and give an example of a rule it might enforce.

Consider how companies keep their infrastructure safe and compliant.

Practice

1. What is the main purpose of Terraform Cloud/Enterprise?

easy

A. To help teams manage infrastructure together safely

B. To replace Terraform CLI on local machines

C. To provide a graphical interface for writing Terraform code

D. To host websites built with Terraform

Solution

1. Step 1: Understand Terraform Cloud/Enterprise role

   Terraform Cloud/Enterprise is designed to help teams collaborate on infrastructure management safely.

2. Step 2: Eliminate incorrect options

   It does not replace the CLI, provide a GUI for coding, or host websites.

3. Final Answer:

   To help teams manage infrastructure together safely -> Option A

4. Quick Check:

   Collaboration and safety = B [OK]

Hint: Think teamwork and safety in infrastructure management [OK]

Common Mistakes:

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

2. Which of the following is the correct way to configure a Terraform Cloud workspace in terraform block?

easy

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

B. terraform { cloud_backend { org_name = "my-org" ws_name = "my-workspace" } }

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

D. terraform { backend "remote" { org = "my-org" workspace_name = "my-workspace" } }

Solution

1. Step 1: Recall Terraform Cloud backend syntax

   The correct syntax uses backend "cloud" with organization and workspaces { name = "my-workspace" } block.

2. Step 2: Compare options to syntax

   terraform { backend "cloud" { organization = "my-org" workspaces { name = "my-workspace" } } } matches the official syntax exactly; others have incorrect keys or structure.

3. Final Answer:

   terraform { backend "cloud" { organization = "my-org" workspaces { name = "my-workspace" } } } -> Option C

4. Quick Check:

   Backend "cloud" with organization and workspaces block = D [OK]

Hint: Remember backend "cloud" block with organization and workspaces { name } [OK]

Common Mistakes:

• Using incorrect block names like cloud_backend
• Mixing keys like org vs organization
• Wrong nesting of workspace inside cloud block

3. Given this Terraform Cloud workspace configuration snippet, what will happen when you run terraform apply?

terraform {
  backend "cloud" {
    organization = "example-org"
    workspaces {
      name = "prod"
    }
  }
}

medium

A. Terraform will run the apply remotely in Terraform Cloud and update the remote state

B. Terraform will run the apply locally and update remote state in Terraform Cloud

C. Terraform will fail because workspace name should be outside workspaces block

D. Terraform will ignore the backend and run locally without remote state

Solution

1. Step 1: Understand backend cloud with workspaces block

   The workspaces { name = "prod" } syntax is valid and specifies the workspace in Terraform Cloud.

2. Step 2: Know Terraform Cloud apply behavior

   When using Terraform Cloud backend, terraform apply runs locally but updates the remote state.

3. Final Answer:

   Terraform will run the apply locally and update remote state in Terraform Cloud -> Option B

4. Quick Check:

   Local execution, remote state = B [OK]

Hint: Cloud backend: local execution, remote state [OK]

Common Mistakes:

• Thinking apply runs remotely with cloud backend
• Confusing workspace block syntax
• Assuming backend config is ignored

4. You configured a Terraform Cloud workspace with the following backend block but get an error: Invalid backend configuration. What is wrong?

terraform {
  backend "cloud" {
    organization = "my-org"
    workspace = "dev"
  }
}

medium

A. The organization name is missing

B. Backend "cloud" does not support workspace configuration

C. The key extra_key is not valid in backend configuration

D. The workspace name must be inside a workspaces block, not as workspace key

Solution

1. Step 1: Check valid keys for backend "cloud" block

   Valid keys include organization and workspaces { name = "dev" } block. Direct workspace key is invalid.

2. Step 2: Identify invalid key causing error

   The workspace = "dev" key is not valid; it must be inside a workspaces block.

3. Final Answer:

   The workspace name must be inside a workspaces block, not as workspace key -> Option D

4. Quick Check:

   workspace requires workspaces block = B [OK]

Hint: Only use documented keys in backend block [OK]

Common Mistakes:

• Using direct workspace= instead of workspaces block
• Adding unsupported keys in backend config
• Misplacing workspace inside or outside workspaces block
• Assuming organization can be omitted

5. Your team wants to enforce that all Terraform runs in Terraform Cloud must pass a policy check before applying changes. Which Terraform Cloud/Enterprise feature should you use to achieve this?

hard

A. Sentinel policies integrated with Terraform Cloud runs

B. Terraform CLI hooks on local machines

C. Manual approval outside Terraform Cloud

D. Terraform Cloud workspace tags

Solution

1. Step 1: Identify feature for policy enforcement in Terraform Cloud

   Sentinel is Terraform Cloud's policy as code framework that integrates with runs to enforce rules.

2. Step 2: Eliminate other options

   CLI hooks are local and not enforced centrally; manual approval is not automated; tags do not enforce policies.

3. Final Answer:

   Sentinel policies integrated with Terraform Cloud runs -> Option A

4. Quick Check:

   Policy enforcement = Sentinel = A [OK]

Hint: Use Sentinel for policy checks in Terraform Cloud [OK]

Common Mistakes:

• Confusing local CLI hooks with centralized policy enforcement
• Thinking tags enforce policies
• Relying on manual approval only