AWS provider Terraform Modules Practice Test 2 — 15 Questions

Question 1

What is the primary benefit of using a module registry compared to a local file path for module distribution?

Accepted Answer

It enables version control and easier sharing across the organization.. A module registry (such as the public Terraform Registry or a private registry like Terraform Cloud's) provides a centralized, versioned catalog of modules. When you reference a module via a registry source, you can pin an exact version (e.g., `version = "1.2.0"`), which enables reproducible deployments and safe upgrades. It also makes modules discoverable and shareable across teams and organizations without manually copying files or managing relative paths. Local file paths offer none of these versioning or sharing capabilities.

Answer

It allows you to run Terraform commands faster.

Answer

It removes the need for input variables.

Answer

It automatically converts your code to a higher-level language.

Question 2

When refactoring a large infrastructure configuration, you move a resource into a child module. How do you handle the existing state to prevent Terraform from destroying and recreating the resource?

Accepted Answer

Use the 'terraform state mv' command to move the resource address.. When a resource is moved into a child module, its address in state changes from something like 'aws_instance.web' to 'module.child.aws_instance.web'. Terraform sees these as different resources and would plan a destroy/create. The 'terraform state mv' command updates the state address in place, preserving the existing resource without any API calls.

Answer

Run 'terraform refresh' to automatically detect the move.

Answer

Rename the resource in the configuration to match the old state.

Answer

Delete the state file and run 'terraform apply'.

Question 3

You have a nested module structure. How can you pass a variable from the root module through an intermediate module to a leaf module?

Accepted Answer

You must define the variable in the intermediate module and pass it to the leaf module.. In Terraform, variables are not automatically inherited by child modules. To pass a variable from the root module to a leaf module through an intermediate module, you must explicitly define the variable in the intermediate module and pass it to the leaf module. This means declaring the variable in the intermediate module's variables.tf and then using it in the module block that calls the leaf module.

Answer

Define the variable only in the leaf module and refer to root by index.

Answer

You can use the 'global_vars' block in the root.

Answer

The intermediate module automatically inherits all root variables.

Question 4

You are designing a module that should conditionally create resources based on a boolean input. What feature should you use?

Accepted Answer

Use the 'count' meta-argument with a ternary expression.. The `count` meta-argument accepts a numeric value, and combining it with a ternary expression (e.g., `count = var.enabled ? 1 : 0`) is the canonical Terraform pattern for conditionally creating a resource. When count evaluates to 0, no instances are created; when it evaluates to 1, a single instance is provisioned. This is the idiomatic way to implement conditional resource creation in Terraform.

Answer

Define multiple resources and use 'depends_on' to link them.

Answer

Use an 'if' block around the resource definition.

Answer

Use the 'module' meta-argument inside the resource.

Question 5

You need to output a complex object from a child module to be used by the root module. What is the best practice for defining the output?

Accepted Answer

Define an output block in the child module and reference it in the root module using the module prefix.. Using explicit output blocks in the child module makes the data available for access via 'module..'.

Answer

Assign the output to a global variable in the root module.

Answer

Use a data source to read the child module's internal state.

Answer

Write the output to a local file inside the module and read it in the root.

Question 6

Your team requires a custom module to be versioned strictly to prevent breaking changes during deployments. What is the recommended way to reference a module from a private Git repository?

Accepted Answer

Use the 'ref' parameter in the source URL string.. For modules sourced from a private Git repository, Terraform does not support a separate 'version' argument; instead, you pin to a specific commit, tag, or branch using the 'ref' query parameter appended to the source URL (e.g., 'git::https://example.com/module.git?ref=v1.2.0'). This locks the module to an immutable Git reference, preventing unexpected breaking changes when the repository's default branch moves forward. The 'ref' parameter is the only supported mechanism for version pinning with Git-based module sources.

Answer

Set the 'version' block inside the module definition.

Answer

Copy the module code locally every time a new version is released.

Answer

Use the 'module_version' argument in the module block.

Question 7

You are building a module that needs to be consumed by multiple teams. How should you structure your module to ensure that the root module can provide values for variable definitions without hardcoding them in the module itself?

Accepted Answer

Define variables in a variables.tf file within the module directory.. Using input variables allows the module to be generic and reusable by accepting values defined in the calling configuration.

Answer

Hardcode the values into the resource blocks directly.

Answer

Use terraform.tfvars files inside the module folder.

Answer

Define all values in a locals.tf file within the module.

Question 8

When should you use the 'for_each' meta-argument within a module?

Accepted Answer

To instantiate multiple copies of a module based on a map or set.. The for_each meta-argument is used to instantiate multiple copies of a resource or module based on a map or set of values, giving each instance a stable key. When applied to a module block, it creates one module instance per element in the map or set, and each instance can be referenced by its key. This is the correct use case for for_each within a module.

Answer

To iterate over a list of variables inside a resource block.

Answer

To replace the 'count' meta-argument when you only need one instance.

Answer

To speed up the execution of the provider.

Question 9

Where do module outputs appear after a 'terraform apply'?

Accepted Answer

In the CLI output and the state file.. After 'terraform apply', module outputs are displayed in the CLI output (as part of the apply summary) and are persisted in the Terraform state file. The state file records output values so they can be referenced by other configurations or retrieved later via 'terraform output'.

Answer

In a file named 'outputs.json'.

Answer

They are automatically emailed to the Terraform administrator.

Answer

In the '.terraform/modules' directory.

Question 10

How can you protect a module's inputs from receiving incorrect types of data?

Accepted Answer

Use a 'validation' block with a condition inside the variable declaration.. Terraform's variable validation block, introduced in Terraform 0.13, allows you to define a condition expression that must evaluate to true for the variable value to be accepted. When placed inside a variable declaration, it can check the type, format, or range of the input and produce a custom error message if the condition fails. This is the native, declarative way to enforce input constraints at plan time, preventing invalid data from propagating into the module.

Answer

Use the 'provider' block to enforce input types.

Answer

Write a custom bash script to check the inputs.

Answer

Terraform automatically validates all inputs as strings.

Question 11

You want to use a module that is hosted in a private GitHub repository. Which authentication method should Terraform use to access it?

Accepted Answer

Use the same credentials that 'git clone' would use for that repository.. Terraform's module source supports Git URLs and delegates authentication to the underlying Git client. For a private GitHub repository, Terraform uses the same credentials that 'git clone' would use, such as SSH keys, a credential helper, or a personal access token configured in '~/.netrc' or Git config.

Answer

The module must be public for Terraform to access it.

Answer

Terraform requires a special 'git_token' variable in the module block.

Answer

Embed your GitHub password in the source URL.

Question 12

What is the purpose of the 'terraform init' command when working with modules?

Accepted Answer

It downloads and installs the modules specified in the configuration.. 'terraform init' downloads and installs the modules specified in the configuration into the '.terraform/modules' directory.

Answer

It compiles the modules into machine code.

Answer

It pushes your local modules to the registry.

Answer

It updates the state file to match the modules.

Question 13

If a module has a required variable but you do not provide it in the calling configuration, what happens?

Accepted Answer

Terraform fails with an error during the planning phase.. If a module declares a variable without a default and the calling configuration does not supply a value, Terraform raises an error during the planning phase, stating that the required variable has not been set. Terraform does not invent a value or fall back to prior state. This fail-fast behavior ensures module contracts are honored.

Answer

Terraform uses 'null' for the value.

Answer

Terraform uses the variable value from the previous state.

Answer

Terraform automatically sets the value to an empty string.

Question 14

You are using a module that depends on a specific provider version. Where should this constraint be defined?

Accepted Answer

In the 'required_providers' block within the module's 'terraform' block.. Provider version constraints belong in the 'required_providers' block inside the module's 'terraform' block. This ensures the module declares its own compatibility requirements, which Terraform merges with the root module's constraints during initialization. It makes the module self-contained and portable.

Answer

In the 'provider' block of the calling root module.

Answer

In the root module only.

Answer

In a shell environment variable.

Question 15

Which argument in a module block allows you to provide a custom name to the module instance?

Accepted Answer

The label immediately following the 'module' keyword.. In Terraform, a module block is declared as `module "<LABEL>" { ... }`, where the label immediately following the `module` keyword is the local name (instance name) used to reference the module within the configuration. This label is how you distinguish multiple instances of the same module source and how you reference module outputs (e.g., `module.my_module.output_name`).

Answer

'name'

Answer

'instance_name'

Answer

'alias'