Which command saves the execution plan to a file?

Which command saves the execution plan to a file?

• A. terraform plan -save=FILE
• B. terraform plan -out=FILE
• C. terraform execute -save=FILE
• D. terraform save plan

Answer: (B)

The command that saves the execution plan to a file is utilized to create a snapshot of the changes Terraform will apply to your infrastructure. This is crucial for reviewing and applying changes in a controlled manner. Using `terraform plan -out=FILE`, the `-out` flag specifies the filename to which the execution plan will be written. This allows users to save the plan for later use, enabling them to review the scheduled changes or apply them later with the command `terraform apply FILE`. The term "execution plan" refers to the detailed outline of actions that Terraform will take based on the current infrastructure state and the described desired state in the configuration files. By saving it to a specified file, you can ensure that the exact same plan is reused for applying changes without any modifications or discrepancies since it captures the state and proposed changes at that moment. Using this command effectively helps in ensuring a repeatable and reliable deployment process. It also provides a layer of safety, as you can inspect the output of the plan file before committing to changes in the infrastructure.

The command that saves the execution plan to a file is utilized to create a snapshot of the changes Terraform will apply to your infrastructure. This is crucial for reviewing and applying changes in a controlled manner. Using terraform plan -out=FILE, the -out flag specifies the filename to which the execution plan will be written. This allows users to save the plan for later use, enabling them to review the scheduled changes or apply them later with the command terraform apply FILE.

The term "execution plan" refers to the detailed outline of actions that Terraform will take based on the current infrastructure state and the described desired state in the configuration files. By saving it to a specified file, you can ensure that the exact same plan is reused for applying changes without any modifications or discrepancies since it captures the state and proposed changes at that moment.

Using this command effectively helps in ensuring a repeatable and reliable deployment process. It also provides a layer of safety, as you can inspect the output of the plan file before committing to changes in the infrastructure.