Outputs for module communication in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an output variable in a Terraform module.

Terraform

output "instance_ip" {
  value = [1]
}

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

Aaws_instance.example.public_ip

Bvar.instance_ip

Cmodule.network.subnet_id

Dlocal.ip_address

Attempts:

3 left

💡 Hint

Common Mistakes

Referencing a variable instead of a resource attribute.

Using a module output inside the same module.

The output value should reference the resource attribute you want to expose, here the public IP of the AWS instance.

2fill in blank

medium

Complete the code to access an output from a child module in the root module.

Terraform

output "db_endpoint" {
  value = module.database.[1]
}

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

Adb_endpoint

Boutput_endpoint

Cendpoint_url

Ddatabase_url

Attempts:

3 left

💡 Hint

Common Mistakes

Guessing output names instead of matching the child module's output.

Using resource names instead of output names.

To access a module output, use the exact output name defined in the child module, here 'db_endpoint'.

3fill in blank

hard

Fix the error in the output block to correctly expose the subnet ID from the module.

Terraform

output "subnet_id" {
  value = [1]
  description = "Subnet ID from the network module"
}

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

Alocal.subnet_id

Bvar.subnet_id

Cmodule.network.subnet_id

Daws_subnet.main.id

Attempts:

3 left

💡 Hint

Common Mistakes

Referencing a variable instead of a module output.

Using a resource directly inside an output in the root module.

The output should reference the module's output attribute, not a variable or local value.

4fill in blank

hard

Fill both blanks to define and access an output named 'bucket_name' from a module.

Terraform

module "storage" {
  source = "./modules/storage"
}

output "bucket_name" {
  value = module.storage.[1]
}

# Inside the storage module:
output "[2]" {
  value = aws_s3_bucket.main.bucket
}

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

Abucket_name

Bbucket_id

Cbucket

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the output inside and outside the module.

Referencing resource attributes directly outside the module.

The output name must be consistent inside the module and when accessed outside. Both blanks should be 'bucket_name'.

5fill in blank

hard

Fill all three blanks to correctly define outputs in a module and access them in the root module.

Terraform

module "web" {
  source = "./modules/webserver"
}

output "web_ip" {
  value = module.web.[1]
}

# Inside the webserver module:
output "[2]" {
  value = aws_instance.web.public_ip
}

output "[3]" {
  value = aws_instance.web.id
}

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

Ainstance_ip

Bweb_ip

Cinstance_id

Dweb_id

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching output names between module and root.

Trying to access resource attributes directly outside the module.

The root module accesses outputs by the exact names defined inside the child module. Here, 'web_ip' and 'instance_id' are the output names inside the module, and 'web_ip' is accessed outside.

Practice

1. What is the main purpose of output blocks in Terraform modules?

easy

A. To share values from one module to another or to the user

B. To create new resources in the cloud

C. To define variables for user input

D. To delete resources after deployment

Solution

1. Step 1: Understand the role of output blocks

   Output blocks are used to expose values from a module so other modules or users can access them.

2. Step 2: Differentiate outputs from other blocks

   Unlike resource or variable blocks, outputs do not create or accept input but share information.

3. Final Answer:

   To share values from one module to another or to the user -> Option A

4. Quick Check:

   Outputs share values = D [OK]

Hint: Outputs share info between modules or users [OK]

Common Mistakes:

• Confusing outputs with resource creation
• Thinking outputs accept user input
• Assuming outputs delete resources

2. Which of the following is the correct syntax to define an output named instance_ip with value aws_instance.web.private_ip?

easy

A. output instance_ip = aws_instance.web.private_ip

B. output "instance_ip" { value = aws_instance.web.private_ip }

C. output "instance_ip" = aws_instance.web.private_ip

D. output { instance_ip = aws_instance.web.private_ip }

Solution

1. Step 1: Recall Terraform output block syntax

   Outputs use the syntax: output "name" { value = expression }

2. Step 2: Match syntax with options

   output "instance_ip" { value = aws_instance.web.private_ip } matches the correct syntax with quotes and value assignment inside braces.

3. Final Answer:

   output "instance_ip" { value = aws_instance.web.private_ip } -> Option B

4. Quick Check:

   Correct output block syntax = B [OK]

Hint: Output blocks need quotes and value inside braces [OK]

Common Mistakes:

• Missing quotes around output name
• Using equals sign outside braces
• Placing value outside output block

3. Given this module output block:

output "db_endpoint" {
  value = aws_db_instance.main.endpoint
}

And this root module code:

module "database" {
  source = "./modules/db"
}

output "database_url" {
  value = module.database.db_endpoint
}

What will terraform output database_url show after deployment?

medium

A. The endpoint address of the AWS database instance

B. The string 'module.database.db_endpoint'

C. An error because outputs cannot be nested

D. The IP address of the AWS database instance

Solution

1. Step 1: Understand module output forwarding

   The module outputs 'db_endpoint' which is accessed in root as 'module.database.db_endpoint'.

2. Step 2: Check root output value

   The root output 'database_url' uses the module output value, so it will show the actual endpoint string.

3. Final Answer:

   The endpoint address of the AWS database instance -> Option A

4. Quick Check:

   Module output forwarded = A [OK]

Hint: Root output uses module output value directly [OK]

Common Mistakes:

• Thinking output shows variable name as string
• Assuming outputs cannot be nested
• Confusing endpoint with IP address

4. You wrote this output block inside a module:

output "server_ip" {
  value = aws_instance.app.private_ip
}

But when you run terraform apply, you get an error: Reference to undeclared resource. What is the likely cause?

medium

A. The output block is missing a description

B. Output blocks cannot reference resource attributes

C. Output names cannot contain underscores

D. The resource aws_instance.app is not defined in the module

Solution

1. Step 1: Analyze the error message

   'Reference to undeclared resource' means Terraform cannot find 'aws_instance.app' in the module.

2. Step 2: Check output references

   Outputs must reference existing resources; if resource is missing, error occurs.

3. Final Answer:

   The resource aws_instance.app is not defined in the module -> Option D

4. Quick Check:

   Missing resource causes reference error = A [OK]

Hint: Check resource exists before referencing in output [OK]

Common Mistakes:

• Assuming outputs can't reference resources
• Thinking underscores are invalid in output names
• Believing description is mandatory

5. You have a module that creates multiple AWS instances and outputs a list of their private IPs:

output "instance_ips" {
  value = [for i in aws_instance.app : i.private_ip]
}

How can you use this output in the root module to create a security group rule allowing SSH from all these IPs?

hard

A. Use count = length(module.app.instance_ips) but no for_each

B. Directly assign cidr_blocks = module.app.instance_ips without conversion

C. Use for_each = toset(module.app.instance_ips) in the security group rule resource

D. Outputs cannot be used to create security group rules

Solution

1. Step 1: Understand output is a list of IPs

   The output returns a list of private IP addresses from multiple instances.

2. Step 2: Use for_each with a set for unique IPs

   Security group rules can be created per IP using for_each with toset() to avoid duplicates.

3. Final Answer:

   Use for_each = toset(module.app.instance_ips) in the security group rule resource -> Option C

4. Quick Check:

   Use for_each with toset for multiple IP rules = C [OK]

Hint: Use for_each with toset() for list outputs in resources [OK]

Common Mistakes:

• Assigning list directly to cidr_blocks without for_each
• Using count without mapping IPs
• Thinking outputs can't be used in resource blocks