Terraform Registry modules - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Terraform Registry handle module versioning?

When you specify a module from the Terraform Registry with a version constraint, what happens if a newer version that satisfies the constraint is released?

A Terraform automatically upgrades to the newest version that fits the constraint on the next terraform init.

B Terraform always uses the exact version specified and ignores newer versions.

C Terraform downloads all versions that satisfy the constraint and uses the oldest one.

D Terraform prompts the user to manually select a version each time.

💡 Hint

Think about how version constraints work in package managers.

Terraform Registry modules support version constraints. When you run terraform init, Terraform fetches the latest module version that matches the constraint, automatically upgrading if a newer compatible version exists.

❓ Configuration

intermediate

Correct source syntax for a Terraform Registry module

Which of the following is the correct way to specify a module source from the Terraform Registry for the module networking/vpc/aws version 3.2.0?

A source = "terraform-registry/networking/vpc/aws" version = "3.2.0"

B source = "registry.terraform.io/networking/vpc/aws" version = "3.2.0"

C source = "networking/vpc/aws" version = "3.2.0"

D source = "terraform.io/modules/networking/vpc/aws" version = "3.2.0"

💡 Hint

Terraform Registry modules use a short source address format.

The correct source format for Terraform Registry modules is namespace/module_name/provider. The version is specified separately with the version argument.

❓ Architecture

advanced

Impact of using multiple versions of the same module in one Terraform configuration

You include two modules from the Terraform Registry in your configuration, both named database/mysql/aws, but with different versions: 1.0.0 and 2.0.0. What is the expected behavior during terraform plan and apply?

A Terraform throws an error because multiple versions of the same module are not allowed.

B Terraform uses only the higher version and ignores the lower version module.

C Terraform merges both versions into one module, causing resource conflicts.

D Terraform treats them as separate modules and manages resources independently without conflict.

💡 Hint

Consider how Terraform identifies modules by their source and version.

Terraform allows multiple instances of the same module with different versions by treating each as a separate module instance. Resources are managed independently.

❓ security

advanced

Security best practice when using Terraform Registry modules

What is the best security practice when using modules from the Terraform Registry in your infrastructure code?

A Always pin the module version to a specific release to avoid unexpected changes.

B Disable module version checks to speed up terraform init.

C Modify the module source code directly in the Terraform Registry to add security fixes.

D Use the latest version without pinning to get all security updates automatically.

💡 Hint

Think about stability and predictability in infrastructure code.

Pinning module versions ensures your infrastructure does not unexpectedly change due to module updates, which is critical for security and stability.

🧠 Conceptual

expert

How Terraform Registry modules handle provider dependencies

If a Terraform Registry module declares a provider dependency (for example, AWS), how does Terraform handle the provider configuration when you use that module in your root configuration?

A The module downloads and configures its own provider independently of the root configuration.

B Terraform requires the root configuration to provide the provider configuration; the module uses that configuration automatically.

C Terraform duplicates the provider configuration inside the module, causing conflicts.

D Terraform ignores provider dependencies declared in modules.

💡 Hint

Think about how Terraform shares providers between root and modules.

Terraform expects the root configuration to configure providers. Modules declare provider requirements but do not configure them; they use the root's provider configuration.

Practice

1. What is the main purpose of using Terraform Registry modules in your infrastructure code?

easy

A. To reuse tested infrastructure code easily

B. To write all infrastructure code from scratch

C. To avoid using any external code

D. To manually configure cloud resources without code

Solution

1. Step 1: Understand Terraform Registry modules

   Terraform Registry modules are pre-built, reusable pieces of infrastructure code shared publicly or privately.

2. Step 2: Identify the main benefit

   Using these modules helps you avoid rewriting code and ensures you use tested, reliable configurations.

3. Final Answer:

   To reuse tested infrastructure code easily -> Option A

4. Quick Check:

   Terraform Registry modules = reuse code easily [OK]

Hint: Modules = reuse tested code, save time [OK]

Common Mistakes:

• Thinking modules require writing all code manually
• Believing modules prevent code reuse
• Confusing modules with manual resource setup

2. Which of the following is the correct syntax to include a Terraform Registry module in your configuration?

easy

A. module "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" }

B. resource "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" }

C. module "example" (source = "terraform-aws-modules/vpc/aws", version = "3.0.0")

D. include "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" }

Solution

1. Step 1: Recognize the correct block type

   Terraform modules are included using the module block, not resource or include.

2. Step 2: Check syntax for module block

   The correct syntax uses curly braces with key-value pairs for source and version.

3. Final Answer:

   module "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" } -> Option A

4. Quick Check:

   Use module block with source and version [OK]

Hint: Use module block with source and version keys [OK]

Common Mistakes:

• Using resource block instead of module
• Using parentheses instead of braces
• Using include keyword which is invalid

3. Given this Terraform module block:

module "network" {
  source  = "terraform-aws-modules/vpc/aws"
  version = "3.0.0"
  name    = "my-vpc"
  cidr    = "10.0.0.0/16"
}

What will happen when you run terraform init?

medium

A. Terraform downloads the latest version ignoring the specified version

B. Terraform throws an error because version is missing

C. Terraform downloads version 3.0.0 of the VPC module from the registry

D. Terraform ignores the module and continues without it

Solution

1. Step 1: Understand terraform init behavior with modules

   When terraform init runs, it downloads modules specified with source and version.

2. Step 2: Check version usage

   The version is specified as "3.0.0", so Terraform downloads exactly that version from the registry.

3. Final Answer:

   Terraform downloads version 3.0.0 of the VPC module from the registry -> Option C

4. Quick Check:

   terraform init downloads specified module version [OK]

Hint: terraform init downloads modules with specified version [OK]

Common Mistakes:

• Assuming version is optional and causes error
• Thinking terraform ignores version and downloads latest
• Believing terraform skips modules on init

4. You wrote this module block:

module "db" {
  source = "terraform-aws-modules/rds/aws"
  version = "1.0.0"
  engine = "mysql"
}

When running terraform init, you get an error: Module version 1.0.0 not found. What is the likely cause?

medium

A. The source URL is incorrect and does not point to a module

B. The specified version 1.0.0 does not exist in the Terraform Registry for this module

C. The engine parameter is invalid and causes version error

D. Terraform init requires internet disabled to find modules

Solution

1. Step 1: Analyze the error message

   The error says version 1.0.0 not found, meaning Terraform cannot find that version in the registry for the module.

2. Step 2: Check common causes

   Either the version is mistyped or does not exist. The source looks correct, and engine parameter does not affect version lookup.

3. Final Answer:

   The specified version 1.0.0 does not exist in the Terraform Registry for this module -> Option B

4. Quick Check:

   Version not found error = wrong or missing version [OK]

Hint: Check module version exists in registry before using [OK]

Common Mistakes:

• Blaming source URL when it is correct
• Thinking parameters cause version errors
• Assuming terraform init works offline for modules

5. You want to use a Terraform Registry module but customize it with your own settings. Which approach is best practice?

hard

A. Use the module without specifying version to always get latest

B. Copy the module code into your project and edit it directly

C. Ignore the module and write all resources manually

D. Use the module with source and version, then override variables in your configuration

Solution

1. Step 1: Understand module customization

   Terraform modules accept input variables to customize behavior without changing module code.

2. Step 2: Identify best practice

   Using source and version ensures stable code, and overriding variables lets you customize safely.

3. Final Answer:

   Use the module with source and version, then override variables in your configuration -> Option D

4. Quick Check:

   Customize modules via variables, keep source and version fixed [OK]

Hint: Override variables, don't copy module code [OK]

Common Mistakes:

• Copying module code causes maintenance issues
• Not specifying version risks unexpected changes
• Ignoring modules wastes time and effort