Terraform GCP provider setup - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Correct GCP provider block for Terraform

Which Terraform provider block correctly configures the Google Cloud provider with a specific project and region?

A

provider "google" {
  project = "my-project-id"
  region  = "us-central1"
}

B

provider "gcp" {
  project = "my-project-id"
  region  = "us-central1"
}

C

provider "google" {
  project_id = "my-project-id"
  location  = "us-central1"
}

D

provider "google" {
  project = "my-project-id"
  zone  = "us-central1"
}

💡 Hint

The official Terraform provider for Google Cloud is named "google" and uses "project" and "region" keys.

The correct provider block uses provider "google" with project and region keys. Option A uses wrong provider name, C uses incorrect keys, and D uses zone instead of region.

❓ service_behavior

intermediate

Effect of missing credentials in GCP provider

What happens when you run Terraform with a GCP provider block that does not specify credentials and no environment variables are set?

A Terraform ignores authentication and creates resources anonymously.

B Terraform fails with an authentication error indicating missing credentials.

C Terraform applies resources successfully using default application credentials.

D Terraform prompts interactively for credentials during apply.

💡 Hint

Terraform requires credentials to authenticate with GCP APIs unless default credentials are available.

If no credentials are provided in the provider block or environment, Terraform cannot authenticate and will fail with an error.

❓ Architecture

advanced

Best practice for managing multiple GCP projects in Terraform

You manage infrastructure across multiple GCP projects. Which Terraform setup best isolates configurations and credentials per project?

A Use a single Terraform configuration with multiple provider aliases, each configured with its project and credentials.

B Use one provider block with the first project and switch the project ID manually before each apply.

C Create separate Terraform workspaces for each project but use the same provider block without aliases.

D Use one provider block and pass project IDs as variables without changing credentials.

💡 Hint

Terraform provider aliases allow multiple configurations in one setup.

Using multiple provider aliases lets you configure each GCP project separately with its credentials, enabling isolated management within one Terraform codebase.

❓ security

advanced

Secure way to provide GCP credentials to Terraform

Which method is the most secure way to provide GCP credentials to Terraform for automated pipelines?

A Commit the service account JSON key file to the source code repository and reference it in Terraform provider.

B Manually enter credentials in Terraform provider block as plain text.

C Store the service account JSON key file in the pipeline environment variables as a base64 string and decode it at runtime.

D Use Google Cloud Workload Identity Federation to authenticate without storing keys.

💡 Hint

Avoid storing long-lived keys in source code or environment variables when possible.

Workload Identity Federation allows Terraform to authenticate to GCP securely without storing service account keys, reducing risk of key leakage.

🧠 Conceptual

expert

Terraform provider version constraint impact

Given this provider block snippet, what is the effect of the version constraint on Terraform provider behavior? provider "google" { version = ">= 4.0, < 5.0" project = "my-project" region = "us-east1" }

GCP

provider "google" {
  version = ">= 4.0, < 5.0"
  project = "my-project"
  region  = "us-east1"
}

A Terraform will fail to initialize because the version constraint syntax is invalid.

B Terraform will use any provider version including 5.0 and above if available.

C Terraform will only use provider versions 4.x, preventing automatic upgrades to version 5 or higher.

D Terraform ignores the version constraint and uses the latest installed provider.

💡 Hint

Version constraints control which provider versions Terraform can install and use.

The constraint ">= 4.0, < 5.0" means Terraform will use any provider version starting at 4.0 up to but not including 5.0, preventing upgrades to major version 5.

Practice

1. What is the main purpose of the provider block in a Terraform configuration for GCP?

easy

A. To store user credentials permanently

B. To define virtual machines in GCP

C. To create network firewalls automatically

D. To connect Terraform to Google Cloud services

Solution

1. Step 1: Understand the role of the provider block

   The provider block tells Terraform which cloud service to use and how to connect to it.

2. Step 2: Identify the specific function for GCP

   For Google Cloud, the provider block sets up the connection using project ID, region, and credentials.

3. Final Answer:

   To connect Terraform to Google Cloud services -> Option D

4. Quick Check:

   Provider block = Connect Terraform to cloud [OK]

Hint: Provider block always sets up cloud connection [OK]

Common Mistakes:

• Confusing provider block with resource definitions
• Thinking provider stores credentials permanently
• Assuming provider creates resources automatically

2. Which of the following is the correct syntax to specify the GCP project ID in the Terraform provider block?

easy

A. project = "my-gcp-project"

B. project_id = "my-gcp-project"

C. gcp_project = "my-gcp-project"

D. id_project = "my-gcp-project"

Solution

1. Step 1: Recall the correct attribute name for project ID

   In Terraform's GCP provider, the attribute to set the project is project.

2. Step 2: Match the correct syntax

   The correct syntax is project = "my-gcp-project", which matches project = "my-gcp-project".

3. Final Answer:

   project = "my-gcp-project" -> Option A

4. Quick Check:

   Project ID attribute = project [OK]

Hint: Use 'project' keyword for project ID in provider [OK]

Common Mistakes:

• Using project_id instead of project
• Mixing attribute names like gcp_project
• Misspelling the attribute name

3. Given this Terraform provider block snippet:

provider "google" {
  project = var.project_id
  region  = "us-central1"
  credentials = file("account.json")
}

What will happen if the file account.json is missing or unreadable?

medium

A. Terraform will throw an error and stop

B. Terraform will apply changes without authentication

C. Terraform will use default credentials automatically

D. Terraform will ignore the credentials and proceed

Solution

1. Step 1: Understand the role of credentials in provider block

   The credentials file provides authentication details needed to access GCP.

2. Step 2: Identify behavior when credentials file is missing

   If the file is missing or unreadable, Terraform cannot authenticate and will throw an error, stopping the process.

3. Final Answer:

   Terraform will throw an error and stop -> Option A

4. Quick Check:

   Missing credentials file = error stop [OK]

Hint: Missing credentials file causes error [OK]

Common Mistakes:

• Assuming Terraform skips authentication
• Thinking default credentials always apply
• Believing Terraform proceeds without credentials

4. You wrote this provider block:

provider "google" {
  project = var.project
  region = var.region
  credentials = file("credentials.json")
}

Terraform gives an error: <code>"var.project" is not defined.
What is the likely cause and fix?

medium

A. The provider block must not use variables; replace with fixed strings

B. The file credentials.json is missing; add the file

C. Variables project and region are not declared; declare them in variables.tf

D. Terraform does not support variable use in provider blocks; remove variables

Solution

1. Step 1: Analyze the error message

   The error says var.project is not defined, meaning Terraform cannot find the variable declaration.

2. Step 2: Understand variable usage in Terraform

   Variables must be declared in a variables.tf file or equivalent before use.

3. Final Answer:

   Variables project and region are not declared; declare them in variables.tf -> Option C

4. Quick Check:

   Undefined variable error = declare variables [OK]

Hint: Declare variables before using them in provider [OK]

Common Mistakes:

• Assuming missing credentials file causes this error
• Thinking variables can't be used in provider block
• Ignoring the need to declare variables explicitly

5. You want to set up the Terraform GCP provider to use different projects and regions without changing code. Which is the best practice to achieve this?

hard

A. Hardcode project and region in the provider block

B. Use variables for project and region and pass values at runtime

C. Create multiple provider blocks with fixed values for each environment

D. Store credentials inside the Terraform code directly

Solution

1. Step 1: Understand flexibility needs

   To switch projects and regions easily, avoid hardcoding values in code.

2. Step 2: Use variables for dynamic configuration

   Using variables allows passing different values at runtime without changing code, which is best practice.

3. Step 3: Avoid insecure or rigid methods

   Hardcoding or multiple fixed provider blocks reduce flexibility; storing credentials in code risks security.

4. Final Answer:

   Use variables for project and region and pass values at runtime -> Option B

5. Quick Check:

   Variables for flexibility = best practice [OK]

Hint: Use variables to change project and region easily [OK]

Common Mistakes:

• Hardcoding values reduces flexibility
• Duplicating provider blocks causes maintenance issues
• Embedding credentials in code risks security