What is the standard workflow that a developer follows while working with terraform open source version?

The correct answer is D. Write the terraform code on the developer machine , run terraform plan to check the. The canonical Terraform OSS workflow is Write → Plan → Apply. (D) Describes this correctly: write infrastructure code on your local machine, run 'terraform plan' to preview changes against the current state without modifying anything, then run 'terraform apply' to provision or…

Use the Terraform CLI (terraform plan, apply, destroy, fmt, init, validate, workspace, import, taint, providers, output)

Question

Options

ARun terraform refresh to update the terraform state , then write the terraform code , and
BRun terraform destroy first since you need to start from fresh every time , before running
CWrite terraform code , and run terraform push , to update the terraform state to the
DWrite the terraform code on the developer machine , run terraform plan to check the

How the community answered

(24 responses)

A
4% (1)
C
4% (1)
D
92% (22)

Explanation

The canonical Terraform OSS workflow is Write → Plan → Apply. (D) Describes this correctly: write infrastructure code on your local machine, run 'terraform plan' to preview changes against the current state without modifying anything, then run 'terraform apply' to provision or modify the real infrastructure. (A) is wrong because 'terraform refresh' is not the starting point and is not part of the standard workflow for new code. (B) is wrong - you do not destroy first; that would delete production infrastructure unnecessarily. (C) is wrong because 'terraform push' is not a valid OSS command (it was a legacy Terraform Enterprise command that has since been removed).

Topics

#Terraform workflow#Terraform CLI#terraform plan#Developer workflow

Community Discussion

No community discussion yet for this question.

Full TA-002-P Practice