Module registry for organization in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Understanding Module Registry Structure

You want to organize your Terraform modules in a private module registry for your organization. Which naming convention correctly identifies a module source in the registry?

A "org-name/app1/vpc"

B "app1/network/vpc"

C "registry.terraform.io/org-name/app1/vpc"

D "app1/vpc"

💡 Hint

Think about how Terraform identifies modules by organization, name, and provider.

Terraform module registry uses the format organization/module-name/provider. The correct format includes the organization name first.

❓ Configuration

intermediate

Referencing a Module from Organization Registry

Given a module published in your organization's private registry as org-name/app1/vpc, which Terraform block correctly references this module?

A

module "vpc" {
  source = "org-name/app1/vpc"
  version = "1.0.0"
}

B

module "vpc" {
  source = "terraform.io/org-name/app1/vpc"
  version = "1.0.0"
}

C

module "vpc" {
  source = "app1/vpc"
  version = "1.0.0"
}

D

module "vpc" {
  source = "registry.terraform.io/org-name/app1/vpc"
  version = "1.0.0"
}

💡 Hint

Check the exact source format for modules in Terraform registries.

The source should be org-name/module-name/provider without the registry URL prefix.

❓ security

advanced

Securing Access to Private Module Registry

Your organization uses a private Terraform module registry. What is the best practice to securely authenticate Terraform CLI to access private modules?

A Embed the username and password directly in the module source URL.

B Store the registry credentials in plain text in the Terraform configuration file.

C Use environment variables or CLI login commands to authenticate Terraform CLI securely.

D Disable authentication and allow anonymous access to the private registry.

💡 Hint

Think about secure ways to handle credentials without exposing them in code.

Terraform CLI supports authentication via environment variables or CLI login commands, which keeps credentials out of code and configuration files.

❓ service_behavior

advanced

Module Versioning Behavior in Registry

If you specify version = ">= 1.0.0, < 2.0.0" in your module block, what version of the module will Terraform select from the registry?

A The earliest version that matches the range.

B The latest available version that is at least 1.0.0 but less than 2.0.0.

C The exact version 1.0.0 only.

D Any version regardless of the specified range.

💡 Hint

Consider how Terraform handles version constraints and selects module versions.

Terraform picks the newest version that satisfies the version constraint range.

✅ Best Practice

expert

Organizing Modules for Reusability and Maintenance

Your organization has many Terraform modules for different projects. Which approach best supports maintainability and reuse in a private module registry?

A Use local paths for modules instead of the registry to simplify access.

B Publish all modules as a single large module to reduce the number of modules to manage.

C Duplicate modules for each project to avoid dependency conflicts.

D Create small, focused modules with clear responsibilities and version them independently.

💡 Hint

Think about modular design principles and version control.

Small, focused modules are easier to maintain, test, and reuse. Independent versioning allows safe updates.