Question 343 of 519
Use Terraform outside the core workflowmediumMultiple SelectObjective-mapped

Quick Answer

The answer is using the Terraform CLI with the -auto-approve flag in a pipeline script and using the Terraform Cloud API to trigger runs and check results. These two options are valid because they represent the primary methods for integrating Terraform into automation and CI/CD pipelines outside the standard interactive workflow: the CLI allows direct execution with automated approval, while the API enables programmatic control over remote runs and status checks. On the HashiCorp Terraform Associate TF-003 exam, this question tests your understanding of how Terraform fits into continuous delivery, specifically distinguishing between core workflow commands and automation patterns. A common trap is confusing state migration commands or visualization tools with pipeline automation, so remember that valid automation methods must either execute plans and applies directly or trigger and monitor runs remotely. For a quick memory tip, think “CLI auto-approve or API trigger” as the two reliable paths for hands-off Terraform in your CI/CD pipelines.

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. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 TWO of the following are valid ways to use Terraform outside the core workflow (i.e., in automation or CI/CD pipelines)?

Question 1mediummulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Using the Terraform CLI in a CI/CD pipeline with -auto-approve after a successful plan.

Options A and D are correct. A uses the CLI with -auto-approve in a pipeline. D uses the Terraform Cloud API to trigger runs. B is not a common pattern. C is for state migration. E is a tool for visualization, not automation.

Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Using the Terraform CLI in a CI/CD pipeline with -auto-approve after a successful plan.

    Why this is correct

    Common automation pattern.

    Related concept

    Static NAT maps one inside address to one outside address.

  • Using 'terraform state mv' to reorganize state files.

    Why it's wrong here

    Not directly part of automation workflow.

  • Using 'terraform init -from-module' to force module re-download.

    Why it's wrong here

    Not a typical automation pattern.

  • Using the Terraform Cloud API to trigger runs and check results.

    Why this is correct

    API-driven automation.

    Related concept

    Static NAT maps one inside address to one outside address.

  • Using 'terraform graph' to generate visual output.

    Why it's wrong here

    Graph is for visualization, not automation.

Common exam traps

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Detailed technical explanation

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Key takeaway

NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

Real-world example

How this comes up in practice

A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.

What to study next

Got this wrong? Here's your next step.

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.

Related practice questions

Related TF-003 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free TF-003 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this TF-003 question test?

Use Terraform outside the core workflow — This question tests Use Terraform outside the core workflow — Static NAT maps one inside address to one outside address..

What is the correct answer to this question?

The correct answer is: Using the Terraform CLI in a CI/CD pipeline with -auto-approve after a successful plan. — Options A and D are correct. A uses the CLI with -auto-approve in a pipeline. D uses the Terraform Cloud API to trigger runs. B is not a common pattern. C is for state migration. E is a tool for visualization, not automation.

What should I do if I get this TF-003 question wrong?

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.

What is the key concept behind this question?

Static NAT maps one inside address to one outside address.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

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.