The answer is to use the version argument in the module block to lock the Terraform module version. This is correct because the version argument allows you to specify an exact semantic version constraint—such as version = "~> 3.0" or version = "3.2.1"—which Terraform evaluates against the registry’s metadata during terraform init, ensuring every deployment pulls the identical module code. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of module source versioning and the difference between pinning a registry module versus using a local path or Git ref. A common trap is confusing the version argument with the source argument or assuming that simply specifying a source URL locks the version; it does not. Remember the memory tip: “Version in the block, version on the lock” — if you want to lock a module from the public registry, always include the version argument inside the module block itself.
TF-003 Read, generate and modify configuration Practice Question
This TF-003 practice question tests your understanding of read, generate and modify configuration. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
A team is writing Terraform configurations for a multi-region deployment. They want to use a module from the public Terraform Registry that provisions AWS VPCs. The module has been updated recently, but the team wants to ensure that all deployments use the same version of the module to avoid unexpected changes. Which configuration approach should they take to lock the module version?
Run 'terraform lock' on the module to record its version in the dependency lock file.
Why wrong: The dependency lock file is for providers, not modules.
B
Use the 'version' argument in the module block to specify the exact version.
The 'version' argument in a module block pins the module to a specific version.
C
Reference the module source with a git URL and tag, such as 'git::https://github.com/...?ref=v1.0'.
Why wrong: While this approach works for private modules, the question specifies using the public registry, and the version argument is the standard method.
D
Set the 'required_version' argument in the root module to match the module's version.
Why wrong: The 'required_version' argument is for Terraform CLI version, not module version.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the 'version' argument in the module block to specify the exact version.
Option B is correct because the 'version' argument in a module block is the standard Terraform mechanism for pinning a module from the Terraform Registry to a specific semantic version. This ensures that all deployments use the exact same module version, preventing unexpected changes from newer releases. The version constraint is evaluated against the registry's metadata and enforces the specified version during 'terraform init'.
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.
✗
Run 'terraform lock' on the module to record its version in the dependency lock file.
Why it's wrong here
The dependency lock file is for providers, not modules.
✓
Use the 'version' argument in the module block to specify the exact version.
Why this is correct
The 'version' argument in a module block pins the module to a specific version.
Related concept
Read the scenario before looking for a memorised answer.
✗
Reference the module source with a git URL and tag, such as 'git::https://github.com/...?ref=v1.0'.
Why it's wrong here
While this approach works for private modules, the question specifies using the public registry, and the version argument is the standard method.
✗
Set the 'required_version' argument in the root module to match the module's version.
Why it's wrong here
The 'required_version' argument is for Terraform CLI version, not module version.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the distinction between module version pinning (using 'version' in the module block) and provider version pinning (using 'required_providers' and the lock file), leading candidates to confuse 'terraform lock' or 'required_version' as valid mechanisms for locking module versions.
Detailed technical explanation
How to think about this question
When a module block includes a 'version' argument, Terraform queries the registry's API to resolve the constraint and downloads the matching release. The resolved version is recorded in the .terraform/modules/modules.json file, but the lock file only tracks provider versions; module versions are pinned purely by the configuration. A subtle behavior is that if the version constraint uses a range (e.g., '~> 1.0'), 'terraform init' may upgrade to a newer patch or minor version within the range, so for absolute locking an exact version like '1.2.3' should be specified.
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.
Read, generate and modify configuration — This question tests Read, generate and modify configuration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the 'version' argument in the module block to specify the exact version. — Option B is correct because the 'version' argument in a module block is the standard Terraform mechanism for pinning a module from the Terraform Registry to a specific semantic version. This ensures that all deployments use the exact same module version, preventing unexpected changes from newer releases. The version constraint is evaluated against the registry's metadata and enforces the specified version during 'terraform init'.
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.
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.