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.