Why importing existing resources matters in Terraform - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import an existing AWS S3 bucket into Terraform state.

Terraform

terraform import aws_s3_bucket.my_bucket [1]

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

Amy-existing-bucket

Baws_s3_bucket.my_bucket

Cbucket_name

Dmy_bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the Terraform resource name instead of the actual bucket name.

Using an incorrect or placeholder name.

You need to specify the actual name of the existing bucket to import it into Terraform state.

2fill in blank

medium

Complete the Terraform resource block to define an imported AWS EC2 instance.

Terraform

resource "aws_instance" "[1]" {
  # Configuration will be managed after import
}

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

Anew_instance

Bimported_bucket

Cmy_s3_bucket

Dexisting_instance

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated resource names.

Using names that conflict with other resources.

The resource name should reflect the imported resource, such as 'existing_instance' for clarity.

3fill in blank

hard

Fix the error in the import command to correctly import an existing AWS VPC with ID 'vpc-123abc'.

Terraform

terraform import [1] vpc-123abc

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

Aaws_vpc.my_vpc

Bvpc-123abc

Cmy_vpc

Daws_vpc.vpc-123abc

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource ID as the resource address.

Using incorrect resource type or name.

The import command requires the Terraform resource address, which includes the resource type and resource name defined in the configuration, such as 'aws_vpc.my_vpc'.

4fill in blank

hard

Fill both blanks to complete the Terraform import command for an existing AWS IAM role named 'admin-role'.

Terraform

terraform import [1] [2]

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

Aaws_iam_role.admin

Baws_iam_role

Cadmin-role

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the resource address and resource ID.

Using incomplete resource addresses.

The import command needs the full resource address and the actual resource ID. Here, 'aws_iam_role.admin' is the resource address and 'admin-role' is the IAM role name in AWS.

5fill in blank

hard

Fill all three blanks to define a Terraform resource block for an imported AWS RDS instance named 'db-instance' with identifier 'prod-db'.

Terraform

resource "[1]" "[2]" {
  identifier = "[3]"
  # Additional configuration after import
}

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

Aaws_db_instance

Bimported_db

Cprod-db

Daws_instance

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong resource types like 'aws_instance' for RDS.

Confusing resource name with identifier.

Leaving identifier blank or incorrect.

The resource type is 'aws_db_instance', the resource name can be 'imported_db' to indicate it is imported, and the identifier is the actual RDS instance ID 'prod-db'.

Practice

1. Why is it important to import existing resources into Terraform before managing them?

easy

A. To automatically delete unused resources in the cloud

B. To avoid creating duplicate resources and keep infrastructure organized

C. To speed up Terraform plan execution by skipping resource checks

D. To convert resources into a different cloud provider format

Solution

1. Step 1: Understand Terraform resource management

   Terraform manages resources by tracking them in its state file. If a resource exists but is not in the state, Terraform may try to create it again.

2. Step 2: Role of importing existing resources

   Importing adds existing resources to the state, preventing duplication and keeping infrastructure consistent.

3. Final Answer:

   To avoid creating duplicate resources and keep infrastructure organized -> Option B

4. Quick Check:

   Importing prevents duplicates [OK]

Hint: Import existing resources to avoid duplicates and conflicts [OK]

Common Mistakes:

• Thinking import speeds up Terraform plan
• Believing import deletes resources
• Assuming import changes cloud provider

2. Which is the correct syntax to import an existing AWS S3 bucket named my-bucket into Terraform resource aws_s3_bucket.example?

easy

A. terraform import my-bucket aws_s3_bucket.example

B. terraform import aws_s3_bucket example my-bucket

C. terraform import aws_s3_bucket.example my-bucket

D. terraform import aws_s3_bucket.example bucket=my-bucket

Solution

1. Step 1: Understand terraform import command structure

   The command format is terraform import [resource_address] [resource_id]. The resource address comes first, then the ID.

2. Step 2: Apply to the example

   Here, resource address is aws_s3_bucket.example and ID is my-bucket. So the correct command is terraform import aws_s3_bucket.example my-bucket.

3. Final Answer:

   terraform import aws_s3_bucket.example my-bucket -> Option C

4. Quick Check:

   Command format = resource_address then ID [OK]

Hint: Remember: import command is 'terraform import resource_address resource_id' [OK]

Common Mistakes:

• Swapping resource address and ID order
• Adding extra keywords like 'bucket='
• Separating resource address incorrectly

3. Given this Terraform import command:
terraform import aws_instance.web i-1234567890abcdef0
What will Terraform do after this import?

medium

A. Add the EC2 instance with ID i-1234567890abcdef0 to the Terraform state under aws_instance.web

B. Create a new EC2 instance named aws_instance.web with ID i-1234567890abcdef0

C. Delete the EC2 instance i-1234567890abcdef0 from AWS

D. Export the EC2 instance configuration to a file named aws_instance.web

Solution

1. Step 1: Understand what terraform import does

   The import command adds an existing resource to Terraform's state file, linking the resource address to the real resource ID.

2. Step 2: Apply to the EC2 instance example

   Here, the EC2 instance with ID i-1234567890abcdef0 is linked to the Terraform resource aws_instance.web. No new resource is created or deleted.

3. Final Answer:

   Add the EC2 instance with ID i-1234567890abcdef0 to the Terraform state under aws_instance.web -> Option A

4. Quick Check:

   Import adds resource to state, no creation or deletion [OK]

Hint: Import links existing resource to Terraform state without changes [OK]

Common Mistakes:

• Thinking import creates or deletes resources
• Confusing import with export or backup
• Assuming import modifies resource configuration

4. You ran terraform import aws_s3_bucket.example my-bucket but Terraform shows an error: Resource aws_s3_bucket.example not found in configuration. What is the likely cause?

medium

A. The resource aws_s3_bucket.example is not defined in your Terraform files

B. The bucket my-bucket does not exist in AWS

C. You used the wrong AWS region in your provider configuration

D. Terraform import command requires a plan before importing

Solution

1. Step 1: Analyze the error message

   The error says the resource address aws_s3_bucket.example is not found in the Terraform configuration files.

2. Step 2: Understand import requirements

   Terraform import requires the resource block to be defined in the configuration before importing. Without it, Terraform cannot map the import.

3. Final Answer:

   The resource aws_s3_bucket.example is not defined in your Terraform files -> Option A

4. Quick Check:

   Resource must exist in config before import [OK]

Hint: Define resource in config before importing it [OK]

Common Mistakes:

• Assuming import creates resource block automatically
• Blaming AWS bucket existence without checking config
• Thinking import requires terraform plan first

5. You have an existing Azure virtual network created outside Terraform. You want to manage it with Terraform without recreating it. Which steps should you follow?

hard

A. Use terraform state rm to remove the network from state before importing

B. Run terraform apply immediately to let Terraform detect and manage the network

C. Delete the existing network and create it again with Terraform configuration

D. Write the Terraform resource block matching the existing network, then run terraform import with the resource address and network ID

Solution

1. Step 1: Define the resource in Terraform configuration

   Write a resource block that matches the existing Azure virtual network's settings so Terraform knows what to manage.

2. Step 2: Import the existing network into Terraform state

   Use terraform import with the resource address and the actual network ID to link the existing resource to Terraform.

3. Final Answer:

   Write the Terraform resource block matching the existing network, then run terraform import with the resource address and network ID -> Option D

4. Quick Check:

   Define resource then import existing resource [OK]

Hint: Define resource first, then import existing infrastructure [OK]

Common Mistakes:

• Running apply without import causes resource recreation
• Deleting existing resource unnecessarily
• Removing state before import causes loss of tracking