The answer is that the module does not reference the `enable_xray` variable in any resource, so setting it has no effect. In Terraform, declaring a variable in a module’s `variables.tf` file only makes it available for input; it does not automatically apply that value to any infrastructure. For a variable to cause changes in a plan, it must be explicitly consumed—typically by assigning it to an argument within a resource block, such as `enable_xray = var.enable_xray` in the ECS task definition. This question tests your understanding of Terraform’s variable mechanics and the separation between input and usage, a common pitfall on the HashiCorp Terraform Associate TF-003 exam. Many candidates mistakenly assume that setting a variable in the root module will automatically propagate to resources, but without a direct reference, the plan remains unchanged. Remember the tutor’s tip: “A variable declared but not consumed is just a placeholder—no consumption, no change.”
TF-003 Interact with Terraform modules Practice Question
This TF-003 practice question tests your understanding of interact with terraform modules. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are a DevOps engineer at a company that manages infrastructure for multiple environments (dev, staging, prod) using Terraform. The team has created a reusable module for deploying an AWS ECS Fargate service. The module accepts variables for environment name, container image tag, and desired count. The module is stored in a private Git repository. The root configurations for each environment are stored in separate directories, each with its own backend configuration. Recently, a developer added a new feature to the module that requires a new variable 'enable_xray' (boolean, default false). After updating the module source to point to the new commit, the developer runs 'terraform init' and 'terraform plan' in the dev environment. The plan shows that the ECS service will be updated, but the output does not show any changes related to X-Ray. The developer expected that setting 'enable_xray = true' in the dev root module would enable X-Ray tracing. However, the plan shows no changes to the task definition. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The module does not reference the 'enable_xray' variable in any resource, so setting it has no effect.
Option D is correct because the `enable_xray` variable, even when set to `true` in the root module, will not cause any changes in the plan unless the module's resources actually reference that variable. In Terraform, a variable declared in a module has no effect on infrastructure unless it is used in a resource argument. The developer saw no changes to the task definition because the module's code likely does not include a condition or argument that uses `enable_xray` to enable X-Ray tracing on the ECS task definition.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The module source was not updated correctly; it still points to the old commit.
Why it's wrong here
If the source were old, the new variable would not be recognized, causing an error.
✗
The developer forgot to run 'terraform init' after changing the module source.
Why it's wrong here
The developer ran init, so modules are updated.
✗
The variable 'enable_xray' is not declared in the module's variables.tf file.
Why it's wrong here
If it were undeclared, Terraform would error during plan, not show no changes.
✓
The module does not reference the 'enable_xray' variable in any resource, so setting it has no effect.
Why this is correct
The variable was added but not used in the module's resources, so no changes occur.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume declaring a variable and setting its value automatically triggers infrastructure changes, but Terraform only applies changes when the variable is actually consumed by a resource argument.
Trap categories for this question
Command / output trap
If it were undeclared, Terraform would error during plan, not show no changes.
Detailed technical explanation
How to think about this question
In Terraform, a variable declared in a module's `variables.tf` is only an input placeholder; it does not automatically wire into any resource. For the variable to affect infrastructure, it must be explicitly referenced in a resource block (e.g., `aws_ecs_task_definition`'s `container_definitions` JSON or a `count`/`for_each` condition). A common real-world scenario is when a module author adds a variable but forgets to update the resource configurations to use it, leading to a silent no-op even when the variable is set.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the TF-003 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Interact with Terraform modules — This question tests Interact with Terraform modules — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The module does not reference the 'enable_xray' variable in any resource, so setting it has no effect. — Option D is correct because the `enable_xray` variable, even when set to `true` in the root module, will not cause any changes in the plan unless the module's resources actually reference that variable. In Terraform, a variable declared in a module has no effect on infrastructure unless it is used in a resource argument. The developer saw no changes to the task definition because the module's code likely does not include a condition or argument that uses `enable_xray` to enable X-Ray tracing on the ECS task definition.
What should I do if I get this TF-003 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This TF-003 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the TF-003 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.