State and real infrastructure mapping in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How Terraform detects drift in infrastructure

Terraform keeps track of your infrastructure state. What happens when you manually change a resource outside Terraform?

Which option best describes Terraform's behavior when you run terraform plan after such a manual change?

A Terraform crashes with an error about state mismatch.

B Terraform ignores the manual change and shows no difference in the plan.

C Terraform deletes the resource automatically without warning.

D Terraform detects the difference and shows the manual change as a drift to be corrected.

💡 Hint

Think about how Terraform compares the saved state with the real infrastructure.

Terraform compares the saved state file with the real infrastructure. If it finds differences, it shows them as drift in the plan, so you can decide how to handle them.

❓ Architecture

intermediate

Best practice for remote Terraform state storage

You want to share Terraform state safely among your team and avoid state conflicts. Which remote backend is the best choice for this purpose?

A Keep the state file in a public GitHub repository.

B Store the state file locally on each developer's machine.

C Use a remote backend like AWS S3 with state locking via DynamoDB.

D Upload the state file manually to a shared email group.

💡 Hint

Think about safe sharing and preventing simultaneous edits.

Using a remote backend like AWS S3 with DynamoDB locking allows safe sharing of state and prevents concurrent changes that could corrupt the state.

❓ Configuration

advanced

Terraform state locking mechanism

Which of the following Terraform backend configurations correctly enables state locking to prevent concurrent modifications?

Terraform

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "prod/terraform.tfstate"
    region = "us-west-2"
    # Which option enables locking?
  }
}

A Add <code>enable_locking = true</code> to enable locking.

B Add <code>dynamodb_table = "terraform-lock-table"</code> to enable locking with DynamoDB.

C Add <code>lock = true</code> to enable locking.

D Add <code>lock_table = "terraform-lock-table"</code> to enable locking.

💡 Hint

Look for the exact parameter name for DynamoDB locking in S3 backend.

The S3 backend uses a DynamoDB table for locking. The correct parameter is dynamodb_table to specify the lock table.

❓ security

advanced

Protecting sensitive data in Terraform state

Your Terraform state contains sensitive information like passwords and API keys. What is the best way to protect this data in the state file?

A Encrypt the state file at rest using backend encryption features.

B Store sensitive data in plain text variables inside the state file.

C Remove sensitive data from Terraform configuration completely.

D Store the state file unencrypted but restrict file permissions only.

💡 Hint

Think about encryption and backend capabilities.

Encrypting the state file at rest using backend features (like S3 encryption) protects sensitive data from unauthorized access.

🧠 Conceptual

expert

Terraform state refresh behavior

After running terraform apply, you manually delete a resource in the cloud provider console. What will happen when you run terraform plan next?

A Terraform will show the resource as needing to be created again to match the state file.

B Terraform will ignore the missing resource and show no changes.

C Terraform will delete the resource from the state file automatically.

D Terraform will crash with an error about missing resource.

💡 Hint

Think about how Terraform compares state with real infrastructure.

Terraform detects that the resource is missing in the real infrastructure but present in the state file, so it plans to recreate it to match the state.