TF-003 Practice Test 19 — 15 Questions

Question 1

A root module uses a module that creates an AWS EC2 instance. The module outputs the instance ID. The root module then uses this output in a null_resource provisioner. After modifying the module, terraform plan shows that the EC2 instance will be destroyed and recreated. What is the impact on the null_resource?

Accepted Answer

The null_resource will be destroyed and recreated alongside the EC2 instance.. Option A is correct because the null_resource depends on the output, so when the module instance is destroyed and recreated, the output value changes, triggering destruction and recreation of the null_resource. Option B is wrong because it will be recreated. Option C is wrong because the dependency is implicit through the output. Option D is wrong because module dependency is automatically inferred.

Answer

The null_resource prompts the user to confirm before any changes.

Answer

The null_resource will remain unchanged because it is not directly attached to the module.

Answer

The null_resource will fail to run because the output is temporarily unavailable during destroy.

Question 2

Which TWO are benefits of using Terraform modules?

Accepted Answer

Encapsulation of complexity, providing a clean interface.. Modules promote reusability and encapsulation of complex infrastructure components. Option C is wrong because modules do not inherently improve performance; they add overhead. Option D is wrong because modules are not specifically for security; they can be used for any resource. Option E is wrong because modules do not reduce state file size; they may increase it.

Answer

Faster execution of terraform plan and apply.

Answer

Reduction in state file size.

Answer

Enhanced security by automatically encrypting state files.

Question 3

A developer creates a module in a subdirectory called 'networking' relative to the root module. How should the module source be specified in the root module?

Accepted Answer

./networking. Option A is correct because local module paths must start with './' or '../'. './networking' correctly references the 'networking' subdirectory relative to the root. Option B (../networking) would go up one level. Option C assumes a 'modules' subdirectory. Option D is not a valid relative path.

Answer

./modules/networking

Answer

../networking

Answer

networking

Question 4

A team is using a private module registry from a third-party vendor. When running terraform init, they receive an error: 'Error downloading module: could not download module... server responded with 401 Unauthorized'. What is the most likely cause?

Accepted Answer

The registry credentials are missing or invalid.. The 401 Unauthorized error indicates authentication failure. Option B is correct because the module registry requires valid credentials, and they are missing or incorrect. Option A is wrong because registry URL typo usually gives a 404 or connection timeout. Option C is wrong because network firewall usually gives connection refused or timeout. Option D is wrong because Terraform version incompatibility gives a different error about required_version.

Answer

The module source URL is incorrect.

Answer

The Terraform version is too old for the module.

Answer

The network firewall is blocking outbound connections.

Question 5

After running `terraform plan`, the user receives an error: `Error: Missing required variable`. The variable 'vpc_cidr' is provided. What is the most likely cause?

Accepted Answer

The module requires a variable 'environment' that is not passed.. The module defines a second required variable 'environment' that has no default value and is not set in the module block, causing the error. Option B is wrong because 'vpc_cidr' is provided. Option C is wrong because syntax is correct. Option D is wrong because there is no conflict; the variable is simply unset.

Answer

The module block syntax is incorrect.

Answer

The variable 'vpc_cidr' is misspelled.

Answer

The variable 'vpc_cidr' conflicts with a provider variable.

Question 6

Which THREE of the following are valid ways to reference a module output value within the same Terraform configuration?

Accepted Answer

In the count or for_each of another module or resource.. Options A, B, and D are correct. A: Direct reference in resource arguments. B: Use in count or for_each arguments of resources. D: Use in locals block for complex expressions. C is wrong because module outputs aren't used in provider configurations. E is wrong because data sources are for external data, not module outputs.

Answer

In a data source definition as a filter.

Answer

In a provider block to set endpoints.

Question 7

You are developing a module. Which TWO actions are recommended best practices?

Accepted Answer

Use local values to simplify expressions.. Options B and C are correct. Defining outputs for important resources (B) allows consumers to access module results. Using local values (C) simplifies expressions and improves readability. Option A (hardcoding defaults) reduces flexibility. Option D (absolute paths) makes modules less portable. Option E is unnecessary because provider configurations are inherited.

Answer

Use the same provider configuration as the root module.

Answer

Hardcode default values for all variables.

Answer

Use absolute paths in module source.

Question 8

Given the plan output, how is the module 'instances' configured in the root module?

Accepted Answer

The root module uses for_each in the module block with a map variable.. Option D is correct because for_each with a map creates one instance per key, and each instance can have different variables like ami and instance_type. Option A is wrong because count would show index numbers, not keys. Option B is wrong because using module multiple times would show different module addresses. Option C is wrong because a module with a single resource but for_each inside would still show one instance per key.

Answer

The module uses count with a list variable.

Answer

The module is declared twice with different names.

Answer

The module contains a resource with for_each inside.

Question 9

A module block references a module with version constraint '>= 2.0, < 3.0'. An older version 1.5 is already cached from a previous init. The team wants to ensure they use a newer version. After running terraform init -upgrade, what happens?

Accepted Answer

Terraform upgrades to the latest version in the range 2.x that is not yet cached.. Option B is correct because terraform init -upgrade re-checks the source and uses the latest version matching the constraint. Option A is wrong because it ignores the cache if -upgrade is used. Option C is wrong because it will upgrade within constraint. Option D is wrong because no error occurs.

Answer

Terraform upgrades to version 3.0 because it is the latest.

Answer

Terraform returns an error because version 1.5 is incompatible with the constraint.

Answer

Terraform uses the cached version 1.5 because it is already present.

Question 10

What is the correct way to resolve this provider version conflict?

Accepted Answer

Change the root module's required version to ~> 2.70.. The conflict arises because the module requires a provider version (~> 2.70) that is incompatible with the root's requirement (>= 3.0). The best solution is to update the module's required provider version, if possible, to be compatible with the root. Option A is wrong because removing the root constraint may allow a version that satisfies both, but it's better to update the module. Option B is wrong because downgrading the root version to 2.x may lose features. Option D is wrong because manually editing .terraform is not supported.

Answer

Ignore the module's required_providers and force install the root version.

Answer

Remove the required_providers block from the root module.

Answer

Manually edit the .terraform/modules/consul/main.tf to change the version.

Question 11

A developer creates a directory structure with a module located at './modules/networking'. The root configuration references it with source = './modules/networking'. What is the behavior when running terraform init from the root directory?

Accepted Answer

Terraform uses the module directly from the local filesystem.. Option C is correct because local path modules are detected automatically without registry. Option A is wrong because local paths don't require registry. Option B is wrong because no internet needed. Option D is wrong because it will be found.

Answer

Terraform requires a network connection to verify the module.

Answer

Terraform attempts to download the module from the public registry.

Answer

Terraform returns an error because the module path is not absolute.

Question 12

A module defines an input variable with 'sensitive = true'. The root module tries to use that variable in an output block. What happens when running 'terraform apply'?

Accepted Answer

The output value is hidden in the CLI output but still available in the state.. Sensitive variables are obfuscated in the command line output. Option A is wrong because terraform apply will succeed; the value is just hidden. Option B is wrong because the output is not removed, just masked. Option D is wrong because the variable is still available programmatically.

Answer

The apply fails with an error because sensitive variables cannot be used in outputs.

Answer

The output is displayed normally because outputs are always visible.

Answer

The output is removed from the plan entirely to protect the sensitive value.

Question 13

A module 'web_app' defines an input variable 'instance_count' with type = number and a validation block ensuring it is between 1 and 10. What happens if a user sets instance_count = 0?

Accepted Answer

Terraform returns an error during validation and stops execution.. Option B is correct because the validation rule will fail, causing Terraform to return an error during plan or apply. Option A is wrong because validation occurs before apply. Option C is wrong because the validation block overrides default. Option D is wrong because the default is irrelevant if a value is provided.

Answer

Terraform applies the module with zero instances, as a value of 0 is allowed.

Answer

Terraform ignores the validation if the variable is explicitly set.

Answer

Terraform uses the default value for instance_count from the module.

Question 14

A team renamed a module from 'module.network' to 'module.vpc' in their configuration. They run 'terraform plan' and see that Terraform wants to destroy the old network resources and create new ones. They want to preserve the existing resources without downtime. What should they do?

Accepted Answer

Add a 'moved' block to the configuration to map the old module address to the new one.. Using the 'moved' block is the recommended way to refactor module names without destroying/recreating resources. Option A is wrong because 'terraform state mv' would also work but requires manual commands; 'moved' is declarative. Option B is wrong because changing the source would change the module content, not just the name. Option C is wrong because destroying and recreating causes downtime.

Answer

Use 'terraform state mv' to move the resources to the new module address.

Answer

Update the module source to a new version.

Answer

Accept the destroy and recreate since it's the only way.

Question 15

Which of the following files is NOT required in a Terraform module?

Accepted Answer

providers.tf. Option D is correct because a module does not require its own providers.tf; it inherits provider configurations from the root module. Options A, B, and C are all standard files commonly found in a module (main.tf, variables.tf, outputs.tf).

Answer

outputs.tf

Answer

variables.tf

Answer

main.tf