GCP provider setup in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the GCP provider in Terraform.

Terraform

provider "google" {
  project = "[1]"
}

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

Amy-gcp-project

Baws-project

Cazure-project

Dlocal-project

Attempts:

3 left

💡 Hint

Common Mistakes

Using project names from other cloud providers like AWS or Azure.

Leaving the project field empty.

The project attribute specifies your Google Cloud project ID. It must match your actual GCP project.

2fill in blank

medium

Complete the code to specify the region for the GCP provider.

Terraform

provider "google" {
  project = "my-gcp-project"
  region  = "[1]"
}

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

Aeurope-west1

Bus-east-1

Cus-central1

Dasia-southeast1

Attempts:

3 left

💡 Hint

Common Mistakes

Using AWS region names like 'us-east-1' which are invalid in GCP.

Leaving the region field blank.

The region attribute sets the geographic location for your resources. 'us-central1' is a valid GCP region.

3fill in blank

hard

Fix the error in the provider block by completing the missing attribute.

Terraform

provider "google" {
  project = "my-gcp-project"
  region  = "us-central1"
  [1] = "/path/to/credentials.json"
}

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

Acredentials

Bcredentials_path

Cauth_file

Dservice_account

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect attribute names like 'credentials_path' or 'auth_file'.

Not providing the path to the credentials file.

The credentials attribute specifies the path to your service account JSON key file for authentication.

4fill in blank

hard

Fill both blanks to configure the provider with project and region variables.

Terraform

variable "project_id" {
  type = string
}

variable "region" {
  type = string
}

provider "google" {
  project = "[1]"
  region  = "[2]"
}

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

Avar.project_id

Bvar.region

Cvar.project

Dvar.location

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect variable names like 'var.project' or 'var.location'.

Omitting the 'var.' prefix.

Use var.project_id and var.region to reference the declared variables in the provider block.

5fill in blank

hard

Fill all three blanks to configure the provider with project, region, and credentials variables.

Terraform

variable "project_id" {
  type = string
}

variable "region" {
  type = string
}

variable "credentials_path" {
  type = string
}

provider "google" {
  project  = "[1]"
  region   = "[2]"
  credentials = "[3]"
}

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

Avar.project_id

Bvar.region

Cvar.credentials_path

Dvar.keyfile

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names like 'var.keyfile' instead of 'var.credentials_path'.

Forgetting the 'var.' prefix.

Reference the variables var.project_id, var.region, and var.credentials_path correctly in the provider block.

Practice

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

easy

A. To define the virtual machine size in GCP

B. To create a new Google Cloud project automatically

C. To connect Terraform to your Google Cloud project

D. To set up billing information for Google Cloud

Solution

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

   The provider "google" block tells Terraform which cloud service to connect to and how.

2. Step 2: Identify what the provider configures

   It sets the connection details like project ID, region, and credentials to manage resources in GCP.

3. Final Answer:

   To connect Terraform to your Google Cloud project -> Option C

4. Quick Check:

   Provider block = Connect to GCP [OK]

Hint: Provider block always connects Terraform to the cloud service [OK]

Common Mistakes:

• Thinking provider creates resources directly
• Confusing provider with resource definitions
• Assuming provider sets billing or VM size

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

easy

A. project = "my-project-123"

B. project_id = "my-project-123"

C. projectName = "my-project-123"

D. projectID = "my-project-123"

Solution

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

   The official Terraform GCP provider uses project to specify the project.

2. Step 2: Check the syntax format

   The attribute is project = "my-project-123".

3. Final Answer:

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

4. Quick Check:

   Correct attribute is project [OK]

Hint: Use project [OK]

Common Mistakes:

• Using project_id instead of project
• Using camelCase like projectName or projectID
• Missing quotes around the project ID string

3. Given this Terraform provider block for GCP:

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

What will happen when you run terraform init?

medium

A. Terraform throws an error because the attribute project is incorrect

B. Terraform initializes and connects to the specified GCP project using the credentials file

C. Terraform ignores the credentials file and uses default credentials

D. Terraform creates a new GCP project named "my-project" automatically

Solution

1. Step 1: Check attribute names in the provider block

   The correct attribute for project ID is project, which is used here.

2. Step 2: Understand Terraform behavior on correct attributes

   Terraform initializes successfully and configures the provider using the credentials file.

3. Final Answer:

   Terraform initializes and connects to the specified GCP project using the credentials file -> Option B

4. Quick Check:

   Correct attributes allow successful init [OK]

Hint: Use exact attribute names like project to ensure smooth init [OK]

Common Mistakes:

• Assuming project is incorrect (it's the right attribute)
• Thinking Terraform auto-creates projects
• Believing init ignores credentials

4. You wrote this provider block:

provider "google" {
  project = "my-project"
  region = "us-central1"
  credentials = file("wrong-path.json")
}

When running terraform plan, you get a credentials error. What is the most likely cause?

medium

A. The credentials file path is incorrect or file does not exist

B. The project is invalid format

C. The region value is not supported by GCP

D. Terraform requires credentials to be set as environment variables only

Solution

1. Step 1: Analyze the credentials attribute

   The credentials attribute expects a valid JSON file path with service account keys.

2. Step 2: Identify the error cause

   If the file path is wrong or file missing, Terraform cannot authenticate and throws an error.

3. Final Answer:

   The credentials file path is incorrect or file does not exist -> Option A

4. Quick Check:

   Wrong credentials file path causes auth error [OK]

Hint: Check credentials file path carefully to avoid auth errors [OK]

Common Mistakes:

• Assuming region errors cause credential failures
• Thinking project format causes credential errors
• Believing credentials must be environment variables only

5. You want to configure Terraform to manage resources in two different GCP projects within the same configuration. How should you set up the provider blocks?

hard

A. Set project dynamically inside resource blocks without provider aliases

B. Use a single provider block with a list of projects

C. Create two separate Terraform configurations for each project

D. Define two provider blocks with different aliases and specify project for each

Solution

1. Step 1: Understand multi-project management in Terraform

   Terraform supports multiple provider configurations using aliases to distinguish them.

2. Step 2: Configure providers with aliases and project

   Define two provider "google" blocks with different alias names and set project for each.

3. Step 3: Reference providers in resources

   Use provider = google.alias_name in resource blocks to specify which project to use.

4. Final Answer:

   Define two provider blocks with different aliases and specify project for each -> Option D

5. Quick Check:

   Multiple projects = multiple aliased providers [OK]

Hint: Use provider aliases to manage multiple GCP projects [OK]

Common Mistakes:

• Trying to list multiple projects in one provider
• Not using aliases and causing conflicts
• Splitting into separate configs unnecessarily