In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when you merge or commit changes to version control.

In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when you merge or commit changes to version control.

• A. True
• B. False
• C. Only on manual trigger
• D. It depends on workspace settings

Answer: (A)

Terraform Cloud automatically creates a speculative plan whenever a workspace is connected to a version control repository and changes are pushed to that repository. This speculative plan is a preview of the proposed changes, shown for review before any apply action. You’ll see the plan results in the Runs view (and often surfaced in pull requests if your VCS integration is configured). No changes are applied automatically unless you enable auto-apply; the default behavior is to generate the plan for review while leaving apply as a separate, deliberate step. This automatic behavior depends on VCS-driven runs being enabled for the workspace, so if that setting is turned off, the automatic speculative planning wouldn’t occur. In the common setup, the statement is true.

Terraform Cloud automatically creates a speculative plan whenever a workspace is connected to a version control repository and changes are pushed to that repository. This speculative plan is a preview of the proposed changes, shown for review before any apply action. You’ll see the plan results in the Runs view (and often surfaced in pull requests if your VCS integration is configured). No changes are applied automatically unless you enable auto-apply; the default behavior is to generate the plan for review while leaving apply as a separate, deliberate step. This automatic behavior depends on VCS-driven runs being enabled for the workspace, so if that setting is turned off, the automatic speculative planning wouldn’t occur. In the common setup, the statement is true.