What is the workflow for deploying new infrastructure with Terraform?

• A. terraform plan to import the current infrastructure to the state file, make code changes, and terraform apply to update the infrastructure.
• B. Write a Terraform configuration, run terraform show to view proposed changes, and terraform apply to create new infrastructure.
• C. terraform import to import the current infrastructure to the state file, make code changes, and terraform apply to update the infrastructure.
• D. Write a Terraform configuration, run terraform init, run terraform plan to view planned infrastructure changes, and terraform apply to create new infrastructure

Answer: (D)

The workflow for deploying new infrastructure with Terraform centers on authoring the desired state in configuration files, initializing the working directory to set up providers, previewing what will change with a plan, and then applying those changes to create the resources. You start by writing the Terraform configuration that describes the resources you want. Then you run a command to initialize the project so Terraform can download the necessary providers and set up the backend. Next, you run a plan to see a detailed preview of what Terraform will create, change, or destroy based on that configuration and the current state. Finally, you apply the plan to actually provision the new infrastructure.

This sequence is correct because plan does not create resources by itself; it only shows what would happen. Initialization is required before planning to ensure Terraform can fetch the proper plugins. Applying uses the confirmed plan to enact the changes. The other options mix in commands that either import existing infrastructure (which is for bringing existing resources under management, not for starting fresh) or use commands that display current state rather than the proposed changes, which isn’t appropriate when deploying new resources.