Dependency inversion with modules in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

How does dependency inversion improve Terraform module design?

In Terraform, dependency inversion helps create modules that are more reusable and less tightly coupled. Which statement best describes this benefit?

A Modules depend on concrete resource names inside other modules to ensure exact resource usage.

B Modules avoid using variables and outputs to reduce complexity.

C Modules hardcode provider configurations to avoid external dependencies.

D Modules depend on abstract input variables and outputs rather than specific resource implementations.

💡 Hint

Think about how modules can be flexible and reusable without knowing internal details of other modules.

Dependency inversion means modules rely on abstractions (inputs/outputs) instead of concrete details. This makes modules reusable and easier to maintain.

❓ Configuration

intermediate

Identify the correct way to invert dependency between Terraform modules

Given two Terraform modules, network and app, the app module needs the subnet ID created by network. Which code snippet correctly applies dependency inversion?

Terraform

module "network" {
  source = "./network"
}

module "app" {
  source    = "./app"
  subnet_id = ???
}

A subnet_id = module.network.subnet_id

B subnet_id = "network_subnet_id"

C subnet_id = var.subnet_id

D subnet_id = aws_subnet.network.id

💡 Hint

Remember that modules expose outputs to share data.

The network module should expose the subnet ID as an output. The app module receives it via input variable. Using module.network.subnet_id correctly passes the value.

❓ security

advanced

What security risk arises from tightly coupling Terraform modules without dependency inversion?

When Terraform modules directly reference each other's internal resources instead of using inputs and outputs, what security risk is most likely?

A Modules automatically encrypt all data, reducing security risks.

B Accidental modification or deletion of resources due to unclear ownership.

C Increased risk of provider credential leakage.

D Exposing sensitive data by hardcoding secrets inside modules.

💡 Hint

Think about what happens if one module changes internal resource names used by another module.

Without dependency inversion, modules tightly coupled to internal resources can cause accidental changes or deletions because ownership and boundaries are unclear.

❓ service_behavior

advanced

How does dependency inversion affect Terraform plan and apply behavior?

When Terraform modules use dependency inversion properly, how does it affect the terraform plan and terraform apply commands?

A Terraform can correctly determine resource dependencies and apply changes in the right order.

B Terraform fails to detect dependencies and applies resources in random order.

C Terraform ignores module outputs and applies all resources simultaneously.

D Terraform requires manual intervention to order resource creation.

💡 Hint

Consider how Terraform uses inputs and outputs to build a dependency graph.

Proper dependency inversion with inputs and outputs allows Terraform to build an accurate dependency graph, ensuring resources are created or updated in the correct order.

✅ Best Practice

expert

Which Terraform module design best follows dependency inversion principles for multi-environment deployment?

You want to deploy the same infrastructure modules to multiple environments (dev, staging, prod) with different configurations. Which design best applies dependency inversion?

A Embed environment logic inside resource names within modules to differentiate environments.

B Create separate copies of modules for each environment with hardcoded values inside.

C Use a single module with input variables for environment-specific settings and outputs for shared data.

D Avoid using modules and write all resources inline for each environment.

💡 Hint

Think about how to reuse code and separate configuration from implementation.

Using input variables for environment-specific settings and outputs for sharing data follows dependency inversion. It keeps modules reusable and decoupled from environment details.