TF-003 Practice Test 20 — 15 Questions

Question 1

After adding a new module sourced from a Git repository with a specific tag, terraform init reports that the module is being downloaded. What is the best practice to ensure the team uses the same version of this module consistently?

Accepted Answer

Use a Git tag, like '?ref=v1.0.0', to pin the version.. Option C is correct because using a specific Git tag ensures version control and reproducibility. Option A is wrong because 'latest' tag is not deterministic. Option B is wrong because branch names change over time. Option D is wrong although version constraints work with registries, not Git sources directly without metadata.

Answer

Use a version constraint in the module block, e.g., version = 1.0.0.

Answer

Specify the source as the branch name 'main'.

Answer

Use the 'latest' tag in the source URL.

Question 2

An organization stores their Terraform modules in a private Git repository. They need to reference a module that resides in a subdirectory called 'modules/rds' within the repository 'infra-modules' on the main branch. Which source argument should be used?

Accepted Answer

source = "git::https://github.com/org/infra-modules.git//modules/rds". The generic Git source format with a double-slash (//) to specify a subdirectory is correct. Option A is wrong because it uses a single slash and would reference the root of the repository. Option C is wrong because the subdirectory path should come after // not before. Option D is wrong because it uses an incorrect format with a colon before the //.

Answer

source = "git::https://github.com/org/infra-modules.git"

Answer

source = "git::https://github.com/org/infra-modules.git:modules/rds"

Answer

source = "git::https://github.com/org/infra-modules.git//rds"

Question 3

Which THREE files are considered part of the standard module structure?

Accepted Answer

main.tf. The standard module structure includes main.tf, variables.tf, and outputs.tf. Option C is wrong because terraform.tfvars is used to assign values, not part of module definition. Option E is wrong because backend.tf is for state configuration, which belongs in the root module.

Answer

backend.tf

Answer

terraform.tfvars

Question 4

Which TWO module source types are supported by Terraform natively?

Accepted Answer

Terraform Registry (e.g., hashicorp/consul/aws). Options A and D are correct. A: Local paths are supported. D: Terraform Registry is supported. B is wrong because npm is not a Terraform source. C is wrong because Docker Hub is not a Terraform source. E is wrong because there is no built-in Jenkins module source.

Answer

Docker Hub repositories

Answer

Jenkins plugin repository

Answer

npm packages

Question 5

Which THREE statements about module configuration are correct?

Accepted Answer

Module sources can be local paths or remote URLs.. Options A, B, and E are correct. Module sources can be local paths or remote URLs (A). A module block can contain multiple resources and even child modules (B). Module inputs can be optional if the module defines a default value (E). Option C is false because outputs from a module can be known during planning (using terraform plan) if the values are deterministic. Option D is false because not all source types support version constraints (e.g., local paths).

Answer

Version constraints can be specified for any module source.

Answer

The outputs of a module are available after apply only.

Question 6

A team is using a module from the Terraform Registry. When they run 'terraform init', they receive an error stating that the module source cannot be downloaded. The module source is correct. What is the most likely cause?

Accepted Answer

The user forgot to run 'terraform init' before 'terraform plan' or 'apply'.. The most common cause is that the user forgot to run 'terraform init' before attempting to use the module, as modules must be downloaded first. Option A is wrong because if the source is correct, a network issue might cause a different error (timeout, 404). Option C is wrong because provider version issues are separate from module download errors. Option D is wrong because output variable names don't affect init.

Answer

The module output variable names are misspelled.

Answer

The provider version in the module conflicts with the root provider version.

Answer

The internet connection is down.

Question 7

Which version of the module was downloaded and why?

Accepted Answer

3.19.0, because it is the latest version matching the constraint ~> 3.0, which allows any 3.x version.. The version constraint ~> 3.0 allows any version in the 3.x range, and 3.19.0 is the latest version within that constraint at the time of init. Option B is wrong because '~> 3.0' does not allow 3.0.0 only; it allows all 3.x versions. Option C is wrong because 3.19.0 is higher than 3.0.0, but still matches. Option D is wrong because the constraint does not limit to patch updates; it allows minor updates as well (since '~> 3.0' is equivalent to '>= 3.0, < 4.0').

Answer

3.0.0, because ~> 3.0 only allows the exact version 3.0.0.

Answer

3.19.0, because it is the latest version and version constraints are ignored.

Answer

3.0.0, because ~> 3.0 is limited to patch updates within 3.0.x.

Question 8

A developer wants to create multiple instances of a module that provisions a single EC2 instance. They want to create 3 EC2 instances. Which approach is most efficient and concise?

Accepted Answer

Use the 'count' meta-argument in the module block.. Using 'count' in the module block is the recommended way to create multiple instances of a module. Option B is wrong because copying the module block three times is not DRY. Option C is wrong because for_each requires a map or set of strings, not just a number. Option D is wrong because a module can only have one source; you cannot specify a list of sources.

Answer

Set the source argument to a list of three URLs.

Answer

Use the 'for_each' meta-argument with a list of numbers.

Answer

Copy the module block three times with different names.

Question 9

A team is using a module from the Terraform Registry and wants to ensure they always get the latest patch version of the 3.2.x series. Which version constraint should they use?

Accepted Answer

~> 3.2.0. Option C is correct because the pessimistic constraint operator ~> with three parts (e.g., ~> 3.2.0) allows only patch-level changes (3.2.0, 3.2.1, etc.). Option A (~> 3.2) allows minor version updates (3.3, 3.4). Option B (>= 3.2, < 4.0) also allows minor updates. Option D is invalid syntax.

Answer

~> 3.2

Answer

3.2.*

Answer

>= 3.2, < 4.0

Question 10

A module outputs a map of security group IDs keyed by name. In the root module, a resource needs to reference the security group ID for the name 'web-sg'. How should the root configuration access this value?

Accepted Answer

module.sg["web-sg"]. Using a 'for' expression with a condition is the correct way to filter a map. Option A is wrong because map syntax uses brackets, not dot notation. Option B is wrong because you need to look up by key, not index. Option D is wrong because module outputs are not accessed via data sources.

Answer

module.sg.web-sg

Answer

data.module.sg["web-sg"]

Answer

module.sg[0]

Question 11

You have two modules that create resources in different providers. Module A creates a VPC in AWS, Module B creates a Kubernetes cluster that requires the VPC ID. You want to ensure Module B runs after Module A but avoid hardcoding the VPC ID. Which approach is most appropriate?

Accepted Answer

Output the VPC ID from Module A and pass it as input to Module B.. Option B is correct because using outputs from Module A and passing them as inputs to Module B establishes both ordering and data flow. Option A (depends_on) ensures ordering but does not pass data. Option C (data source) would require the VPC to already exist. Option D (terraform graph) only visualizes, not enforces.

Answer

Use a data source in Module B to look up the VPC.

Answer

Use terraform graph to order modules.

Answer

Use module dependency via depends_on in the root module.

Question 12

A large organization uses Terraform to manage infrastructure across multiple AWS accounts. They have a shared module for VPC stored in a private Git repository (git::https://github.com/org/terraform-aws-vpc.git?ref=v1.0.0). After updating the module source to ref=v1.2.0, they run terraform init and then terraform plan. The plan still shows the old module's resources and behavior. They confirm the new tag exists and the module code has changed. The root module source line is correct. What is the most likely cause?

Accepted Answer

Terraform cached the previous module version and did not download the new one.. Option C is correct. Terraform caches modules locally; after changing the source ref, terraform init must be run to download the new version. If the user forgot to include the -upgrade flag or did not clean the cache, Terraform may use the cached version. Option A is not a standard command. Option B would cause an error. Option D (output changes) would not cause the plan to show old behavior if the module code is new.

Answer

They forgot to run terraform get.

Answer

The module source URL is incorrect.

Answer

The module's outputs changed and they need to update the root module.

Question 13

Which Terraform feature helps manage dependencies between resources?

Accepted Answer

depends_on. The `depends_on` argument explicitly specifies dependencies, ensuring resources are created or destroyed in the correct order.

Answer

data source

Answer

output

Answer

provisioner

Question 14

Which TWO of the following are key advantages of using Terraform over manual infrastructure management? (Select TWO.)

Accepted Answer

Consistent and repeatable deployments. Options B and E are correct. Version-controlled infrastructure code enables collaboration and audit trails. Consistent and repeatable deployments reduce errors. Option A is incorrect because Terraform does not auto-discover resources. Option C is not guaranteed. Option D is not a Terraform feature.

Answer

Guaranteed zero downtime during updates

Answer

Automatic discovery of existing resources

Answer

Self-healing infrastructure

Question 15

What is the primary purpose of Terraform's state file?

Accepted Answer

Map configurations to real-world resources. The state file maps Terraform configurations to real-world resources, allowing Terraform to track resource metadata and detect drift.

Answer

Provide a GUI

Answer

Execute scripts

Answer

Store secrets