Bulk import strategies in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import a resource using Terraform CLI.

Terraform

terraform import [1] my_resource_id

Drag options to blanks, or click blank then click option'

Aimport.aws_instance

Bresource.aws_instance

Caws_instance.example

Dexample.aws_instance

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect resource address format.

Confusing resource type and resource name order.

The correct syntax for importing a resource is terraform import <resource_type>.<resource_name> <id>. Here, aws_instance.example is the resource address.

2fill in blank

medium

Complete the code to import multiple resources using a script loop.

Terraform

for id in resource_ids; do terraform import [1] "$id"; done

Drag options to blanks, or click blank then click option'

Aaws_instance.example

Baws_instance

Cexample

Dresource.aws_instance

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the resource type without the resource name.

Using only the resource name without the type.

When importing multiple resources in a loop, you must specify the full resource address like aws_instance.example for each import command.

3fill in blank

hard

Fix the error in the bulk import command by completing the missing part.

Terraform

terraform import -input=false -lock=false [1] resource_id

Drag options to blanks, or click blank then click option'

Aexample.aws_instance

Bresource.example

Caws_instance

Daws_instance.example

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the resource type without the name.

Swapping the order of resource name and type.

The import command requires the full resource address. aws_instance.example is the correct format.

4fill in blank

hard

Fill both blanks to create a Terraform script snippet that imports resources from a list.

Terraform

for id in resource_ids; do terraform import [1] "$id"; done
resource_address = "[2]"

Drag options to blanks, or click blank then click option'

Aaws_s3_bucket.mybucket

Baws_s3_bucket

Cmybucket

Dresource.aws_s3_bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource name alone in the import command.

Using incorrect resource address format.

The import command needs the full resource address aws_s3_bucket.mybucket. The resource type alone is aws_s3_bucket, which can be used as a variable or reference.

5fill in blank

hard

Fill all three blanks to define a Terraform import command inside a loop with dynamic resource names.

Terraform

for id in ids; do terraform import [1].$[2] "$id"; done
resource_type = "[3]"

Drag options to blanks, or click blank then click option'

Aaws_instance

Bname

Dresource_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect variable names for resource name.

Mixing resource type and name in the wrong order.

The import command uses the resource type aws_instance and a dynamic resource name variable resource_name. The resource type is assigned to resource_type.

Practice

1. What is the main purpose of using bulk import strategies in Terraform?

easy

A. To automatically generate Terraform code for new resources

B. To create new resources faster than usual

C. To delete multiple resources simultaneously

D. To efficiently bring many existing resources under Terraform management at once

Solution

1. Step 1: Understand Terraform import

   Terraform import lets you bring existing cloud resources into Terraform state so you can manage them.

2. Step 2: Recognize bulk import purpose

   Bulk import strategies help import many resources quickly instead of one by one.

3. Final Answer:

   To efficiently bring many existing resources under Terraform management at once -> Option D

4. Quick Check:

   Bulk import = manage many existing resources [OK]

Hint: Bulk import means importing many existing resources at once [OK]

Common Mistakes:

• Thinking bulk import creates new resources
• Confusing import with resource deletion
• Assuming import auto-generates Terraform code

2. Which Terraform command is used to import a resource into the state file?

easy

A. terraform import

B. terraform plan

C. terraform init

D. terraform apply

Solution

1. Step 1: Recall Terraform commands

   terraform apply creates or updates resources, terraform init initializes, terraform plan previews changes.

2. Step 2: Identify import command

   terraform import is the command that brings existing resources into Terraform state.

3. Final Answer:

   terraform import -> Option A

4. Quick Check:

   Import command = terraform import [OK]

Hint: Import existing resources with 'terraform import' command [OK]

Common Mistakes:

• Using terraform apply to import
• Confusing init with import
• Trying terraform plan to import

3. Given this script snippet to bulk import AWS EC2 instances:

for id in i-12345678 i-87654321; do terraform import aws_instance.example_$id $id; done

What will be the result after running this script?

medium

A. Terraform will create new instances instead of importing

B. Only the first instance will be imported, second will fail

C. Both instances will be imported with resource names aws_instance.example_i-12345678 and aws_instance.example_i-87654321

D. The script will cause a syntax error and not run

Solution

1. Step 1: Analyze the for loop

   The loop iterates over two instance IDs: i-12345678 and i-87654321.

2. Step 2: Understand terraform import usage

   Each iteration runs terraform import with resource name aws_instance.example_$id and the ID as argument, importing both instances.

3. Final Answer:

   Both instances will be imported with resource names aws_instance.example_i-12345678 and aws_instance.example_i-87654321 -> Option C

4. Quick Check:

   Loop imports both instances correctly [OK]

Hint: Loop imports each resource with unique name using ID [OK]

Common Mistakes:

• Assuming only one import runs
• Thinking terraform creates new instances
• Believing script syntax is invalid

4. You wrote a bulk import script but get errors: "Error: Resource name must not contain '-'". What is the likely cause?

medium

A. Using resource names with dashes (-) which Terraform disallows

B. Missing terraform init before import

C. Incorrect AWS credentials causing import failure

D. Trying to import resources that do not exist

Solution

1. Step 1: Understand Terraform resource naming rules

   Terraform resource names must use underscores (_) not dashes (-).

2. Step 2: Identify cause of error

   The error says resource name must not contain '-', so using dashes in resource names causes this error.

3. Final Answer:

   Using resource names with dashes (-) which Terraform disallows -> Option A

4. Quick Check:

   Resource names cannot have '-' [OK]

Hint: Use underscores (_) in resource names, not dashes (-) [OK]

Common Mistakes:

• Ignoring naming rules and using dashes
• Assuming missing init causes this error
• Blaming credentials for naming errors

5. You want to bulk import 100 existing Azure VMs into Terraform. Which approach best follows Terraform bulk import best practices?

hard

A. Run terraform import once with all VM IDs separated by commas

B. Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files

C. Manually import each VM one by one using terraform import command

D. Create new Terraform resources and delete existing VMs to sync state

Solution

1. Step 1: Understand bulk import best practice

   Bulk import works best with automation scripts looping over resource IDs to import each resource.

2. Step 2: Match Terraform configuration

   Terraform requires matching resource blocks in config files for imported resources to manage them properly.

3. Step 3: Evaluate options

   Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files uses scripting and matching config, Run terraform import once with all VM IDs separated by commas is invalid syntax, Manually import each VM one by one using terraform import command is slow manual work, Create new Terraform resources and delete existing VMs to sync state deletes resources which is unsafe.

4. Final Answer:

   Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files -> Option B

5. Quick Check:

   Automate import with matching config files [OK]

Hint: Automate imports with scripts and matching config files [OK]

Common Mistakes:

• Trying to import multiple IDs in one command
• Manually importing many resources without automation
• Deleting resources instead of importing