The answer is creating an IAM role in the cloud that the CI job can assume, as this is the foundational step for OIDC authentication in a CI/CD pipeline. This works because OIDC eliminates long-lived static credentials by having the CI platform (like GitHub Actions or GitLab CI) issue a short-lived JSON Web Token (JWT), which the cloud provider’s OIDC identity provider validates before allowing the CI job to assume a pre-configured IAM role. On the HashiCorp Terraform Associate TF-003 exam, this tests your understanding of secure authentication patterns versus hardcoding secrets—a common trap is confusing OIDC with static access keys or thinking the CI platform itself stores the cloud credentials. Remember the mnemonic: “JWT to Role, no secrets to hold.”
TF-003 Use Terraform outside the core workflow Practice Question
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.
Which THREE of the following are necessary steps to configure OIDC (OpenID Connect) for authenticating Terraform in a CI/CD pipeline?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set up an OIDC provider in the target cloud (e.g., AWS IAM OIDC provider).
Option B is correct because to authenticate Terraform in a CI/CD pipeline using OIDC, you must first establish trust between the CI platform and the cloud provider by creating an OIDC identity provider (e.g., an AWS IAM OIDC provider). This provider validates the JSON Web Token (JWT) issued by the CI platform (e.g., GitHub Actions, GitLab CI) and maps it to an IAM role, enabling token-based authentication without long-lived secrets.
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.
✗
Generate a long-lived API token and store it as a secret.
Why it's wrong here
Long-lived tokens are against OIDC purpose.
✓
Set up an OIDC provider in the target cloud (e.g., AWS IAM OIDC provider).
Why this is correct
Trust must be established between cloud and CI.
Related concept
Read the scenario before looking for a memorised answer.
✗
Configure remote backend with static credentials.
Why it's wrong here
OIDC replaces static credentials.
✓
Add a provider block with assume_role and web_identity_token attributes in Terraform configuration.
Why this is correct
Terraform needs to know how to authenticate.
Related concept
Read the scenario before looking for a memorised answer.
✓
Create an IAM role in the cloud that the CI job can assume.
Why this is correct
Role assumed by CI with OIDC token.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that OIDC requires storing a long-lived token (Option A) or that the remote backend must use static credentials (Option C), when in fact OIDC replaces both with a trust-based, token-exchange mechanism that uses the `assume_role` and `web_identity_token` attributes.
Detailed technical explanation
How to think about this question
Under the hood, OIDC works by having the CI platform sign a JWT containing claims like the subject (sub) and audience (aud), which the cloud provider's OIDC provider verifies using the platform's public keys (published at a well-known JWKS URI). The IAM role's trust policy then uses the `sts:AssumeRoleWithWebIdentity` API with the `web_identity_token` attribute in Terraform's provider block, allowing the pipeline to obtain temporary AWS credentials valid for up to 1 hour, which is critical for pipelines that run multiple Terraform operations without exposing secrets.
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.
Use Terraform outside the core workflow — This question tests Use Terraform outside the core workflow — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Set up an OIDC provider in the target cloud (e.g., AWS IAM OIDC provider). — Option B is correct because to authenticate Terraform in a CI/CD pipeline using OIDC, you must first establish trust between the CI platform and the cloud provider by creating an OIDC identity provider (e.g., an AWS IAM OIDC provider). This provider validates the JSON Web Token (JWT) issued by the CI platform (e.g., GitHub Actions, GitLab CI) and maps it to an IAM role, enabling token-based authentication without long-lived secrets.
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.