Quick Answer
The answer is the `sensitive` attribute, which must be applied to provider configuration variables to prevent access keys and other credentials from appearing in plan output. This works because Terraform marks the variable as sensitive at the configuration level, causing the CLI to redact its value in all output, including plan, apply, and state displays. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of output security and the distinction between provider-level and resource-level sensitive handling. A common trap is confusing `sensitive` with `secret` or `encrypted`—neither of which exist as Terraform attributes for this purpose. The exam often presents a scenario where a practitioner needs to hide provider credentials from plan output, and the correct choice is always to mark the relevant variable as `sensitive`. Remember the mnemonic: "Sensitive secures the sensitive stuff in the plan—no secrets, no encryption, just redaction."
This TF-003 practice question tests your understanding of use terraform outside the core workflow. 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 Terraform practitioner wants to ensure that the access keys used by a provider are not visible in plan output. Which Terraform attribute should be used when defining the provider?
encrypted
Why wrong: Terraform does not have an encrypted attribute for masking output.
sensitive
Marks a variable as sensitive so its value is not displayed in CLI output.
hidden
Why wrong: No such attribute exists in Terraform.
secret
Why wrong: No such attribute exists in Terraform.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
sensitive
The `sensitive` attribute on provider configuration (via variables) prevents values from being displayed in CLI output, including plan output. There is no `secret` or `hidden` attribute. `encrypted` is not a Terraform attribute for this purpose.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
encrypted
Why it's wrong here
Terraform does not have an encrypted attribute for masking output.
sensitive
Why this is correct
Marks a variable as sensitive so its value is not displayed in CLI output.
Related concept
Read the scenario before looking for a memorised answer.
hidden
Why it's wrong here
No such attribute exists in Terraform.
secret
Why it's wrong here
No such attribute exists in Terraform.
Common exam traps
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Trap categories for this question
Command / output trap
Terraform does not have an encrypted attribute for masking output.
Detailed technical explanation
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which TF-003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Use Terraform outside the core workflow — study guide chapter
Learn the concepts, then practise the questions
Use Terraform outside the core workflow practice questions
Targeted practice on this topic area only
All TF-003 questions
519 questions across all exam domains
HashiCorp Terraform Associate TF-003 study guide
Full concept coverage aligned to exam objectives
TF-003 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise TF-003 questions linked to Understand IaC concepts.
Practise TF-003 questions linked to Understand Terraform basics.
Practise TF-003 questions linked to Understand Terraform's purpose.
Practise TF-003 questions linked to Use Terraform outside the core workflow.
Practise TF-003 questions linked to Interact with Terraform modules.
Practise TF-003 questions linked to Use the core Terraform workflow.
Practise TF-003 questions linked to Implement and maintain state.
Practise TF-003 questions linked to Read, generate and modify configuration.
Practise TF-003 questions linked to TF-003 fundamentals.
Practise TF-003 questions linked to TF-003 scenario.
Practise TF-003 questions linked to TF-003 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Use Terraform outside the core workflow — This question tests Use Terraform outside the core workflow — Read the scenario before looking for a memorised answer..
The correct answer is: sensitive — The `sensitive` attribute on provider configuration (via variables) prevents values from being displayed in CLI output, including plan output. There is no `secret` or `hidden` attribute. `encrypted` is not a Terraform attribute for this purpose.
Identify which TF-003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
Last reviewed: Jun 24, 2026
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.