Import limitations and considerations in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Terraform Import Limitations

Which of the following is NOT a limitation when using terraform import?

A Terraform import does not create resource configuration in code; it only maps existing resources to state.

B Imported resources must have a unique ID that Terraform can recognize.

C Terraform import cannot import resources that are managed outside of Terraform.

D Terraform import can import multiple resources at once using a single command.

💡 Hint

Think about what terraform import actually does versus what it cannot do.

terraform import only maps existing resources to Terraform state. It does not create or modify configuration files. It cannot import multiple resources in one command, and it requires a unique resource ID. It can import resources managed outside Terraform by mapping them.

❓ Architecture

intermediate

Importing Resources with Complex Dependencies

You have a Terraform configuration with resources that depend on each other. What is the best practice when importing these resources?

A Import resources starting from the ones with no dependencies, then import dependent resources in order.

B Import only the top-level resource; dependent resources will be imported automatically.

C Delete dependent resources before importing the main resource.

D Import all resources in any order; Terraform will automatically resolve dependencies.

💡 Hint

Think about how Terraform manages dependencies and state.

Terraform requires importing resources in dependency order to maintain correct state and avoid errors. Importing resources with dependencies first can cause errors.

❓ security

advanced

Security Considerations When Importing Resources

Which security risk is most relevant when importing existing cloud resources into Terraform?

A Terraform import automatically encrypts all resource data during import.

B Terraform import deletes existing resources to secure them.

C Terraform import exposes resource secrets in the state file if not handled properly.

D Terraform import disables all resource access policies temporarily.

💡 Hint

Consider what information Terraform state files contain after import.

Terraform state files can contain sensitive data such as secrets or passwords. Importing resources without securing the state file can expose this data.

✅ Best Practice

advanced

Handling Resource Configuration After Import

After importing a resource into Terraform state, what is the recommended next step to ensure proper management?

A Run <code>terraform apply</code> immediately without any configuration changes.

B Manually write the resource configuration in Terraform code to match the imported resource.

C Delete the imported resource from the cloud provider to avoid conflicts.

D Ignore the imported resource and manage it outside Terraform.

💡 Hint

Think about how Terraform manages resources and configuration files.

Terraform import only adds the resource to state. To manage it properly, the resource must be defined in the configuration files matching the actual resource.

❓ service_behavior

expert

Terraform Import Behavior with Resources Having Dynamic IDs

Consider a cloud resource whose ID changes dynamically after creation (e.g., a load balancer with a generated ID). What happens if you import this resource into Terraform and then the ID changes in the cloud provider?

A Terraform state will become out of sync, causing errors on next plan or apply.

B Terraform automatically updates the state with the new resource ID without user action.

C Terraform deletes the resource and recreates it with the old ID.

D Terraform ignores the ID change and continues managing the resource without issues.

💡 Hint

Think about how Terraform tracks resources using IDs in state.

Terraform relies on resource IDs in state to track resources. If the ID changes outside Terraform, the state becomes invalid and errors occur during operations.