Hard — Terraform Associate Practice Quiz

Question 1

You maintain a reusable networking module that must deploy resources into a secondary AWS region. In the root module you have configured a default AWS provider and an aliased provider named `aws.secondary`. You want the child module to use the aliased provider for all of its resources. What is the correct way to pass this provider configuration to the module?

Accepted Answer

Add a `providers` argument to the module block mapping the child's `aws` to `aws.secondary`, and declare the requirement with a `configuration_aliases` entry in the child module's `required_providers`.

Answer

Define the aliased provider block a second time inside the child module so it inherits automatically at apply time.

Answer

Set an input variable in the child module equal to `aws.secondary` and reference that variable in each resource's `provider` argument.

Answer

Do nothing; a child module always inherits all aliased provider configurations from the root module automatically.

Question 2

A platform team publishes reusable Terraform modules as versioned .zip archives on an internal artifact server reachable at https://artifacts.example.com. A downstream team wants to consume a specific packaged version of the networking module without using Git or the public/private registry. Which module source configuration correctly references the archive?

Accepted Answer

source = "https://artifacts.example.com/modules/networking-1.4.0.zip"

Answer

source = "artifacts.example.com/networking/aws"
  version = "1.4.0"

Answer

source = "git::https://artifacts.example.com/modules/networking-1.4.0.zip"

Answer

source = "https://artifacts.example.com/modules/networking-1.4.0.zip"
  version = "1.4.0"

Question 3

Your team is splitting a large Terraform configuration into two separate root modules, each with its own remote backend state file. A resource named aws_db_instance.primary currently exists in the original state file but should now be managed by the new configuration without destroying and recreating the live database. Which approach correctly moves this resource between the two separate state files?

Accepted Answer

Run 'terraform state mv -state-out=new.tfstate aws_db_instance.primary aws_db_instance.primary' after pulling both states locally, then push the updated states to their respective backends

Answer

Run 'terraform state rm aws_db_instance.primary' in the old configuration and 'terraform apply' in the new configuration to recreate it

Answer

Run 'terraform import aws_db_instance.primary <db-id>' in the new configuration only, leaving the old state untouched

Answer

Copy the entire old state file into the new backend and run 'terraform refresh'

Question 4

A teammate manually renamed an S3 bucket in the AWS console, breaking the mapping in your Terraform state. The next terraform plan proposes to destroy the old bucket (which no longer exists) and create a new one. You want to keep the current live bucket under Terraform management without destroying it, and without changing its resource address in the configuration. Which approach accomplishes this?

Accepted Answer

Run terraform state rm to remove the stale entry, then terraform import to bind the existing live bucket to the same resource address.

Answer

Run terraform apply to let Terraform destroy the missing bucket and recreate a matching one from configuration.

Answer

Run terraform state mv to rename the resource address to match the new bucket name.

Answer

Run terraform refresh so Terraform automatically discovers and re-adopts the renamed bucket.

Question 5

A DevOps engineer manually created an EC2 instance directly in the AWS console. It is not tracked by Terraform, but a colleague accidentally added a matching resource block and ran 'terraform apply', which created a SECOND duplicate instance that Terraform now tracks in state. The team wants Terraform to manage the ORIGINAL console-created instance and delete the accidental duplicate. What is the correct sequence of actions?

Accepted Answer

Run 'terraform state rm' on the duplicate's address, manually terminate the duplicate in AWS, then 'terraform import' to associate the resource block with the original instance's ID

Answer

Run 'terraform destroy' to remove the duplicate, then 'terraform import' to bring the original instance under management

Answer

Run 'terraform state mv' to point the resource block at the original instance's real-world ID

Answer

Run 'terraform apply -refresh-only' so Terraform automatically reconciles the state to the original instance

Question 6

Your team initially configured Terraform with a local backend. After creating a shared S3 backend block in the configuration, a colleague runs 'terraform init' and is prompted about copying existing state to the new backend. They accidentally decline, and later realize the backend settings in the configuration have changed again. They want to re-run initialization to apply the new backend configuration WITHOUT being prompted to migrate or copy existing state. Which command should they use?

Accepted Answer

terraform init -reconfigure

Answer

terraform init -migrate-state

Answer

terraform init -upgrade

Answer

terraform refresh -reconfigure