Writing configuration for imported resources in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a resource block for an imported AWS S3 bucket.

Terraform

resource "aws_s3_bucket" "[1]" {
  bucket = "my-imported-bucket"
}

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

Aimported_bucket

Bmy_bucket

Cbucket_resource

Ds3bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the actual bucket name as the resource block name (it should be a local name).

Including spaces or special characters in the resource name.

The resource block name must match the local name you want to use for the imported bucket. Here, imported_bucket is a clear and valid name.

2fill in blank

medium

Complete the code to import an existing AWS EC2 instance by specifying its ID.

Terraform

resource "aws_instance" "example" {
  instance_id = "[1]"
}

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

Ainstance-01

Bi-1234567890abcdef0

Cec2-instance

Daws_instance_1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a made-up name instead of the real instance ID.

Confusing the resource name with the instance ID.

The instance_id must be the actual EC2 instance ID, which starts with i- followed by hexadecimal characters.

3fill in blank

hard

Fix the error in the Terraform resource block by completing the missing attribute for an imported AWS VPC.

Terraform

resource "aws_vpc" "main" {
  cidr_block = "[1]"
}

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

A192.168.0.0/24

Bvpc-12345678

C10.0.0.0/16

Dvpc-main

Attempts:

3 left

💡 Hint

Common Mistakes

Using the VPC ID instead of the CIDR block.

Using an invalid IP range format.

The cidr_block attribute requires a valid IP range in CIDR notation, such as 10.0.0.0/16. The VPC ID or name is not valid here.

4fill in blank

hard

Fill both blanks to correctly define an imported AWS security group with a description and a VPC ID.

Terraform

resource "aws_security_group" "[1]" {
  name        = "imported_sg"
  description = "[2]"
  vpc_id      = "vpc-0abc1234def56789"
}

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

Aimported_sg

BSecurity group for imported resources

Cdefault_sg

DImported security group

Attempts:

3 left

💡 Hint

Common Mistakes

Using the VPC ID as the resource name.

Leaving the description empty or unclear.

The resource name should be a simple identifier like imported_sg. The description should clearly explain the purpose, such as Security group for imported resources.

5fill in blank

hard

Fill all three blanks to complete the Terraform configuration for an imported AWS RDS instance with allocated storage, engine type, and instance class.

Terraform

resource "aws_db_instance" "[1]" {
  allocated_storage    = [2]
  engine               = "[3]"
  instance_class       = "db.t3.medium"
  identifier           = "my-imported-db"
}

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

Aimported_db

B20

Cmysql

Dpostgres

Attempts:

3 left

💡 Hint

Common Mistakes

Using the engine name as the resource name.

Putting the storage size in quotes (it should be a number).

Using an unsupported engine name.

The resource name is a local label like imported_db. Allocated storage is a number representing GB, here 20. The engine must be a valid database engine like mysql.

Practice

1. What is the main purpose of writing Terraform configuration for an imported resource?

easy

A. To delete the resource automatically

B. To create a new resource from scratch

C. To match the existing resource so Terraform can manage it

D. To backup the resource data externally

Solution

1. Step 1: Understand Terraform import

   Terraform import links an existing resource to Terraform state but requires matching configuration to manage it.

2. Step 2: Purpose of configuration

   Writing configuration that matches the existing resource allows Terraform to track and manage it properly.

3. Final Answer:

   To match the existing resource so Terraform can manage it -> Option C

4. Quick Check:

   Import needs matching config = A [OK]

Hint: Import needs matching config to manage resource [OK]

Common Mistakes:

• Thinking import creates new resources
• Assuming import deletes resources
• Believing import backs up data

2. Which Terraform block is required before importing an existing AWS S3 bucket named my-bucket?

easy

A. resource "aws_s3_bucket" "my_bucket" { bucket_name = "my-bucket" }

B. resource "aws_s3_bucket" "my_bucket" { bucket = "my-bucket" }

C. resource "aws_s3_bucket" "my_bucket" { name = "my-bucket" }

D. resource "aws_s3_bucket" "my_bucket" { id = "my-bucket" }

Solution

1. Step 1: Identify correct attribute for S3 bucket

   The correct attribute to specify the bucket name in Terraform AWS provider is bucket.

2. Step 2: Match syntax for resource block

   The resource block must use resource "aws_s3_bucket" "my_bucket" { bucket = "my-bucket" } to match the existing bucket.

3. Final Answer:

   resource "aws_s3_bucket" "my_bucket" { bucket = "my-bucket" } -> Option B

4. Quick Check:

   Correct attribute is bucket = name [OK]

Hint: Use 'bucket' attribute for S3 bucket name [OK]

Common Mistakes:

• Using 'name' instead of 'bucket' attribute
• Using 'bucket_name' which is invalid
• Using 'id' attribute in config

3. Given this Terraform configuration for an imported AWS EC2 instance:

resource "aws_instance" "web" {
  ami           = "ami-12345678"
  instance_type = "t2.micro"
}

What happens if you run terraform import aws_instance.web i-0abcd1234efgh5678?

medium

A. Terraform state links to the existing instance without changing it

B. Terraform creates a new instance with the given AMI

C. Terraform deletes the existing instance and creates a new one

D. Terraform throws an error because AMI does not match

Solution

1. Step 1: Understand import behavior

   Terraform import links the existing resource ID to the resource block in state without changing the actual resource.

2. Step 2: Effect of running import

   Running import with the instance ID associates the existing EC2 instance with the Terraform resource, no creation or deletion occurs.

3. Final Answer:

   Terraform state links to the existing instance without changing it -> Option A

4. Quick Check:

   Import links state, no resource change [OK]

Hint: Import links existing resource to state, no creation [OK]

Common Mistakes:

• Thinking import creates or deletes resources
• Assuming import validates AMI matches
• Expecting import to modify resource

4. You wrote this Terraform configuration for an imported AWS VPC:

resource "aws_vpc" "main" {
  cidr_block = "10.0.0.0/16"
}

After running terraform import aws_vpc.main vpc-1234abcd, Terraform plan shows it wants to change the CIDR block. What is the likely cause?

medium

A. The actual VPC CIDR block differs from the configured one

B. Terraform import failed and did not link the resource

C. The resource name in config does not match the import command

D. Terraform requires a different syntax for VPC import

Solution

1. Step 1: Analyze import and plan behavior

   Import links the existing VPC to Terraform state, but if the configuration CIDR block differs from the actual VPC, Terraform plans to update it.

2. Step 2: Identify cause of plan changes

   The difference in CIDR block values causes Terraform to want to change the resource to match config, which is not allowed for VPC CIDR.

3. Final Answer:

   The actual VPC CIDR block differs from the configured one -> Option A

4. Quick Check:

   Config mismatch causes plan changes [OK]

Hint: Check config matches actual resource attributes exactly [OK]

Common Mistakes:

• Assuming import failed without checking state
• Confusing resource name with import ID
• Thinking import syntax is wrong

5. You have an existing Azure resource group named rg-prod created outside Terraform. You want to import it and manage it with Terraform. Which steps correctly describe the process?

hard

A. Create a new resource group in Terraform, then delete the existing one manually.

B. Run 'terraform import' first without any resource block, then write the resource block after.

C. Write a resource block with any name, run 'terraform import' with resource group name only, then apply.

D. Write a resource block with name 'rg-prod', run 'terraform import azurerm_resource_group.prod /subscriptions/0000/resourceGroups/rg-prod', then run 'terraform plan' to verify.

Solution

1. Step 1: Write matching resource block

   Before importing, write a resource block with the correct resource type and name matching the existing resource group.

2. Step 2: Run terraform import with full resource ID

   Use the full Azure resource ID to import the existing resource group into Terraform state.

3. Step 3: Verify with terraform plan

   Run 'terraform plan' to confirm Terraform recognizes the imported resource and no unexpected changes are planned.

4. Final Answer:

   Write a resource block with name 'rg-prod', run 'terraform import azurerm_resource_group.prod /subscriptions/0000/resourceGroups/rg-prod', then run 'terraform plan' to verify. -> Option D

5. Quick Check:

   Config first, import with full ID, then plan [OK]

Hint: Write config first, import with full ID, then plan [OK]

Common Mistakes:

• Importing without resource block
• Using partial resource ID in import
• Creating duplicate resources instead of importing