Backend initialization and migration in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens during Terraform backend initialization?

When you run terraform init with a configured backend, what is the main action Terraform performs?

A Terraform validates the syntax of all Terraform files without any network activity.

B Terraform applies all infrastructure changes defined in the configuration.

C Terraform destroys all existing resources to prepare for a fresh deployment.

D Terraform downloads provider plugins and configures the backend to store state remotely.

💡 Hint

Think about what terraform init does before any changes happen.

Running terraform init downloads necessary provider plugins and sets up the backend, which is where Terraform stores its state file remotely. It does not apply or destroy resources at this stage.

❓ service_behavior

intermediate

Effect of backend migration on Terraform state

You have a Terraform project using a local backend. You configure a new remote backend and run terraform init -migrate-state. What is the expected result?

A Terraform copies the existing local state file to the new remote backend and updates the configuration to use it.

B Terraform deletes the local state file and starts with an empty remote state.

C Terraform ignores the local state and creates a new remote state from scratch.

D Terraform fails with an error because state migration is not supported.

💡 Hint

Consider what the -migrate-state flag is designed to do.

The -migrate-state flag tells Terraform to move the existing state from the current backend (local) to the new backend (remote) during initialization. This preserves the state and avoids resource duplication.

❓ Configuration

advanced

Identify the correct Terraform backend configuration for migration

Given this Terraform backend block for local state:

terraform {
  backend "local" {
    path = "terraform.tfstate"
  }
}

You want to migrate to an S3 backend. Which backend configuration block correctly sets up the S3 backend for migration?

A

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    path   = "state/terraform.tfstate"
    region = "us-west-2"
  }
}

B

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "state/terraform.tfstate"
    region = "us-west-2"
  }
}

C

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "terraform.tfstate"
    zone   = "us-west-2"
  }
}

D

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "state/terraform.tfstate"
    region = "us-east-1"
  }
}

💡 Hint

Check the correct attribute names and region for S3 backend.

The S3 backend requires bucket, key, and region attributes. The key is the path inside the bucket. The region must be correct. Option B uses correct attribute names and region.

❓ security

advanced

Security best practice during backend migration

When migrating Terraform state from a local backend to a remote backend like S3, which practice best protects sensitive state data?

A Enable server-side encryption on the S3 bucket and restrict access with IAM policies.

B Store the state file publicly to allow easy access for all team members.

C Disable encryption to improve performance during migration.

D Keep the state file only on local machines to avoid cloud exposure.

💡 Hint

Think about how to keep state data safe in cloud storage.

Encrypting the state file on the server side and restricting access with IAM policies ensures that sensitive information in the state is protected from unauthorized access.

❓ Architecture

expert

Impact of backend migration on Terraform workflow in a team

Your team migrates Terraform state from local files to a remote backend with state locking enabled. Which change in workflow behavior should the team expect?

A Terraform automatically merges conflicting state changes from multiple users.

B All team members can apply changes simultaneously without any state conflicts.

C Only one team member can run Terraform commands that modify state at a time, preventing concurrent state changes.

D State locking disables Terraform plan commands for all users.

💡 Hint

Consider what state locking is designed to prevent.

State locking prevents multiple users from making changes to the state at the same time, avoiding conflicts and corruption. This means only one user can apply changes at once.