Bulk import strategies in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Choosing the best bulk import method for large resource sets

You have thousands of existing cloud resources to manage with Terraform. Which bulk import strategy is most efficient and scalable?

A Manually write all resource blocks in Terraform and skip importing existing resources.

B Manually run terraform import for each resource one by one using a shell script loop.

C Use terraform import with a generated script that runs imports in parallel batches.

D Delete all existing resources and recreate them with Terraform from scratch.

💡 Hint

Think about automation and speed when importing many resources.

Running imports in parallel batches automates the process and speeds it up, making it scalable for thousands of resources. Manual one-by-one imports are slow. Skipping import loses existing state. Deleting resources is risky and unnecessary.

❓ Configuration

intermediate

Terraform import command for multiple resources

You want to import multiple AWS S3 buckets into Terraform state using a script. Which command snippet correctly imports all buckets listed in a file named buckets.txt?

A terraform import aws_s3_bucket.* buckets.txt

B for bucket in $(cat buckets.txt); do terraform import aws_s3_bucket.$bucket $bucket; done

C terraform import aws_s3_bucket.buckets.txt buckets.txt

D terraform import aws_s3_bucket $bucket < buckets.txt

💡 Hint

Consider how to loop over each bucket name and run import separately.

Option B loops over each bucket name from the file and runs terraform import for each, which is the correct way. Other options misuse terraform import syntax or do not loop.

❓ service_behavior

advanced

Effect of importing resources without matching configuration

What happens if you run terraform import on a resource that is not defined in your Terraform configuration files?

A Terraform imports the resource into state but will ignore it during plan and apply until configuration exists.

B Terraform imports the resource into state but will show it as 'tainted' until configuration is added.

C Terraform throws an error and refuses to import the resource without matching configuration.

D Terraform imports the resource and automatically creates a default configuration block.

💡 Hint

Think about how Terraform manages state versus configuration.

Terraform allows importing resources into state even if no configuration exists yet. However, without configuration, Terraform ignores the resource during plan and apply. It does not error or create config automatically.

❓ security

advanced

Security risks during bulk import of cloud resources

Which security risk is most relevant when performing bulk import of existing cloud resources into Terraform state?

A Terraform may overwrite resource permissions during import causing privilege escalation.

B Bulk import deletes existing resources to recreate them with default security settings.

C Terraform import automatically disables resource encryption during import.

D Importing resources requires exposing sensitive credentials in scripts or logs.

💡 Hint

Consider what credentials and data are needed to run import commands safely.

Bulk import requires credentials with read access to resources. If scripts or logs expose these credentials, it risks leakage. Terraform import does not overwrite permissions, disable encryption, or delete resources.

✅ Best Practice

expert

Best practice for managing state consistency during bulk import

When importing thousands of resources in bulk, what is the best practice to ensure Terraform state consistency and avoid conflicts?

A Lock the remote state backend and run imports sequentially or in controlled batches.

B Run all imports concurrently on multiple machines writing to the same remote state backend.

C Disable state locking and run imports in parallel to speed up the process.

D Export the state to local files and merge manually after imports complete.

💡 Hint

Think about how Terraform prevents state corruption during concurrent operations.

Terraform uses state locking to prevent concurrent writes. Locking the remote state backend and running imports sequentially or in controlled batches avoids conflicts and corruption. Disabling locking or concurrent writes risks state corruption. Manual merges are error-prone.