State replace-provider in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does the Terraform command 'state replace-provider' do?

Choose the correct description of the effect of running 'terraform state replace-provider'.

A It deletes the provider configuration from the Terraform state and forces reinitialization.

B It updates the provider references in the Terraform state from an old provider source to a new one without changing resources.

C It replaces all resources managed by a provider with new resources from a different provider.

D It upgrades the provider version in the Terraform configuration files automatically.

💡 Hint

Think about how Terraform manages provider references in the state file.

The 'terraform state replace-provider' command updates the provider source address in the state file, allowing Terraform to recognize resources as managed by a new provider without recreating them.

❓ Configuration

intermediate

Identify the correct syntax to replace a provider source in Terraform state

Given you want to replace the provider source 'registry.terraform.io/hashicorp/aws' with 'registry.terraform.io/custom/aws', which command is correct?

A terraform state replace-provider registry.terraform.io/hashicorp/aws registry.terraform.io/custom/aws

B terraform state replace-provider registry.terraform.io/hashicorp/aws:aws registry.terraform.io/custom/aws:aws

C terraform state replace-provider registry.terraform.io/custom/aws registry.terraform.io/hashicorp/aws

D terraform state replace-provider registry.terraform.io/hashicorp/aws:aws registry.terraform.io/custom/aws

💡 Hint

Provider source addresses are in the form 'registry.terraform.io/namespace/type', using slashes not colons.

The correct syntax uses the full provider source addresses, e.g., 'registry.terraform.io/hashicorp/aws' to 'registry.terraform.io/custom/aws'.

❓ Architecture

advanced

What is the impact on resource management after running 'terraform state replace-provider'?

After replacing the provider source in the Terraform state, what happens when you run 'terraform plan'?

A Terraform throws an error due to provider mismatch and halts the plan.

B Terraform destroys all resources managed by the old provider and creates new ones with the new provider.

C Terraform recognizes resources as managed by the new provider and plans no changes if configurations match.

D Terraform ignores the state changes and continues using the old provider references.

💡 Hint

Consider how Terraform matches resources in state with provider configurations.

Replacing the provider source updates the state so Terraform treats resources as managed by the new provider, avoiding resource recreation if configurations are consistent.

❓ security

advanced

Which security risk is most relevant when using 'terraform state replace-provider'?

What is a potential security concern when replacing a provider source in Terraform state?

A Replacing with a malicious or untrusted provider could lead to unauthorized resource changes.

B The command exposes provider credentials in plaintext in the state file.

C It automatically grants admin permissions to the new provider without user consent.

D It disables encryption of the Terraform state file during the operation.

💡 Hint

Think about trust boundaries and provider code origin.

Replacing the provider source with an untrusted provider risks unauthorized or malicious resource management actions.

❓ service_behavior

expert

What happens if you run 'terraform state replace-provider' with a provider source that does not exist in the state?

If you execute 'terraform state replace-provider old_provider new_provider' but 'old_provider' is not referenced in the current state, what is the result?

A Terraform replaces all providers in the state with the new provider regardless.

B Terraform deletes the entire state file to prevent inconsistencies.

C Terraform returns an error indicating the old provider source was not found in the state.

D Terraform completes successfully but makes no changes to the state.

💡 Hint

Consider how Terraform validates the presence of the old provider source in state.

If the old provider source is not present in the state, Terraform completes successfully but makes no changes, typically informing that no matching provider was found.