20+ practice questions focused on Use Terraform outside the core workflow — one of the most tested topics on the HashiCorp Terraform Associate TF-004 exam. Each question includes a detailed explanation so you learn why the right answer is correct.
Start Use Terraform outside the core workflow PracticeWhich TWO of the following are valid use cases for using Terraform Cloud's Sentinel policies? (Choose two.)
Explanation: Sentinel policies can enforce that all AWS instances are of a specific type by using a `validate` rule that checks the `aws_instance` resource's `instance_type` attribute against an allowed list. This is a common compliance use case for Sentinel in Terraform Cloud, where policy-as-code ensures infrastructure adheres to organizational standards before provisioning. Similarly, Sentinel can enforce that all resources have required tags by inspecting the `tags` attribute in the Terraform plan and ensuring specific keys and values are present, which is another common compliance and governance use case.
Which TWO of the following are true about Terraform Cloud's run lifecycle? (Choose two.)
Explanation: Terraform Cloud allows users to discard a plan without applying it, which is useful when the proposed changes are not desired or need to be revised. This is a standard part of the run lifecycle where a plan can be reviewed and then discarded, preventing any infrastructure changes from being made. Additionally, if auto-apply is disabled for a workspace, every plan requires explicit manual confirmation before the apply phase can proceed, giving users control over when changes are deployed.
Which three of the following are valid ways to use Terraform outside the core provisioning workflow? (Choose three.)
Explanation: The correct options are `terraform import`, `terraform state push`, `terraform plan -out=tfplan`, and `terraform console`. `terraform import` is a non‑provisioning workflow that maps existing infrastructure into Terraform state without creating or destroying resources. `terraform state push` manually uploads a state file to a remote backend, bypassing the normal `apply` workflow. `terraform plan -out=tfplan` generates a plan file that can be applied later, decoupling the planning phase from the apply phase and thus operating outside the core provisioning loop. `terraform console` is a utility for interactively evaluating expressions in the Terraform language, which is also outside the core provisioning workflow.
Which four of the following are valid ways to integrate Terraform into an automated pipeline or use it outside the core manual workflow? (Choose all that apply.)
Explanation: All four correct options represent valid methods for using Terraform outside the core interactive manual workflow. Running `terraform plan` and `terraform apply` in a CI/CD pipeline with environment variables for backend configuration is a standard automation pattern. Terraform Cloud's API-driven run workflow allows programmatic triggering of runs, which is essential for integration with external systems. The `-auto-approve` flag skips the interactive approval prompt, enabling non-interactive execution in scripts. Using `terraform output` in shell scripts is a common way to extract and pass infrastructure data to downstream tools.
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?
Explanation: To prevent sensitive information like access keys from appearing in Terraform plan output, the values should be defined as `sensitive` variables. These variables are then referenced within the provider configuration. The `sensitive` attribute itself is applied to the `variable` block (e.g., `variable "access_key" { sensitive = true }`), not directly to the `provider` block. Therefore, none of the provided options are attributes that can be used directly on a `provider` block for this purpose.
+15 more Use Terraform outside the core workflow questions available
Practice all Use Terraform outside the core workflow questions1. Baseline your knowledge
Start with 10 questions to gauge your current understanding of Use Terraform outside the core workflow. This tells you whether you need a concept refresher or just practice.
2. Review every explanation
For each question — right or wrong — read the full explanation. Understanding why an answer is correct is more valuable than knowing the answer itself.
3. Focus on exam traps
Use Terraform outside the core workflow questions on the TF-004 frequently use trap wording. Look for subtle differences in answers that test your precision, not just general knowledge.
4. Reach 80% consistently
Do repeated sessions until you score 80%+ three times in a row. Then move to mixed-mode practice to test cross-topic recall under realistic conditions.
The exact number varies per candidate. Use Terraform outside the core workflow is tested as part of the HashiCorp Terraform Associate TF-004 blueprint. Practicing with targeted Use Terraform outside the core workflow questions ensures you can handle any format or difficulty that appears.
Yes. Courseiva provides free TF-004 practice questions across all exam topics and domains. The platform includes topic-based practice, mock exams, missed-question review, bookmarked questions, and readiness tracking — no account required.
Difficulty is subjective, but Use Terraform outside the core workflow is a high-priority exam concept tested in multiple ways — direct recall, scenario analysis, and command-output interpretation. Consistent practice is the best way to build confidence.
Launch a full Use Terraform outside the core workflow practice session with instant scoring and detailed explanations.
Start Use Terraform outside the core workflow Practice →