Import state verification in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens after importing a resource state in Terraform?

You run terraform import aws_instance.example i-1234567890abcdef0 to import an existing AWS EC2 instance into your Terraform state. What is the immediate effect on your Terraform state and configuration?

A The resource is added to the state file but must be defined in the configuration before applying changes.

B The resource is deleted from AWS and replaced by Terraform-managed resource.

C The resource is added to the configuration but not to the state file until you run <code>terraform apply</code>.

D The resource is added to both the state file and the configuration automatically.

💡 Hint

Think about what terraform import does versus what Terraform configuration files do.

Importing a resource adds it to the Terraform state file, but the resource must already be declared in the configuration files to be managed properly. Terraform does not modify configuration files automatically.

🧠 Conceptual

intermediate

Why verify Terraform state after import?

After importing a resource into Terraform state, why is it important to verify the state matches the actual resource?

A Because the import command deletes the resource if state is not verified.

B Because Terraform automatically fixes any mismatches during import.

C Because verifying state is optional and has no impact on Terraform behavior.

D Because mismatches can cause Terraform to attempt to recreate or destroy the resource on next apply.

💡 Hint

Consider what happens if Terraform's state does not reflect reality.

If the state does not match the actual resource, Terraform may try to change or replace the resource during the next apply, causing unintended disruptions.

❓ Configuration

advanced

Identify the Terraform import command for a GCP Compute Instance

You have a Google Cloud Compute Instance named my-instance in project my-project and zone us-central1-a. Which import command correctly imports this instance into Terraform resource google_compute_instance.vm?

A terraform import google_compute_instance.vm my-project/us-central1-a/my-instance

B terraform import google_compute_instance.vm projects/my-project/zones/us-central1-a/instances/my-instance

C terraform import google_compute_instance.vm my-instance

D terraform import google_compute_instance.vm zones/us-central1-a/projects/my-project/instances/my-instance

💡 Hint

Check the required resource ID format for GCP Compute Instances in Terraform import.

The correct format for importing a GCP Compute Instance includes the full resource path: projects/{project}/zones/{zone}/instances/{instance}.

❓ security

advanced

Security risk when importing Terraform state from external resources

What is a potential security risk when importing resources into Terraform state from external cloud accounts or projects?

A Importing resources disables cloud provider security groups temporarily.

B Terraform automatically encrypts all imported state files, so no risk exists.

C Sensitive data like passwords or keys may be stored in the state file if not handled properly.

D Importing resources deletes all existing state data, causing data loss.

💡 Hint

Think about what information Terraform state files contain.

Terraform state files can contain sensitive information. Importing resources may add secrets or credentials to the state, so secure storage and encryption are important.

❓ Architecture

expert

Effect of mismatched Terraform configuration after import

You imported an AWS S3 bucket into Terraform state with terraform import aws_s3_bucket.mybucket my-bucket-name. However, your Terraform configuration defines the bucket with versioning enabled, but the actual bucket has versioning disabled. What will happen when you run terraform plan?

A Terraform will show a plan to enable versioning on the bucket to match the configuration.

B Terraform will ignore the versioning difference and show no changes.

C Terraform will delete the bucket and recreate it with versioning enabled.

D Terraform will fail with an error about versioning mismatch.

💡 Hint

Consider how Terraform handles differences between state and configuration.

Terraform compares the imported state with the configuration. If versioning is disabled in the actual bucket but enabled in config, Terraform plans to update the bucket to enable versioning.