Which action statement best describes how Terraform Cloud runs are triggered in a VCS-connected workspace?

Which action statement best describes how Terraform Cloud runs are triggered in a VCS-connected workspace?

• A. A run is triggered by a direct API call
• B. Commit a change to the VCS working directory and branch
• C. Scheduling a run in advance
• D. Manually starting in the UI

Answer: (B)

In a VCS-connected workspace, the trigger for runs is driven by changes in your version control system. When you commit and push changes to the configured branch of the linked repository, Terraform Cloud automatically starts a plan (and, if allowed, proceeds to apply) for that workspace. This setup enables a seamless, automated workflow where code changes in Git control the infrastructure updates. Other ways to trigger runs exist—such as initiating a run via the API, scheduling runs in advance, or starting one manually in the UI—but they aren’t the automatic mechanism that the VCS-integrated workflow relies on. The defining action is the commit to the VCS working directory and the designated branch.

In a VCS-connected workspace, the trigger for runs is driven by changes in your version control system. When you commit and push changes to the configured branch of the linked repository, Terraform Cloud automatically starts a plan (and, if allowed, proceeds to apply) for that workspace. This setup enables a seamless, automated workflow where code changes in Git control the infrastructure updates.

Other ways to trigger runs exist—such as initiating a run via the API, scheduling runs in advance, or starting one manually in the UI—but they aren’t the automatic mechanism that the VCS-integrated workflow relies on. The defining action is the commit to the VCS working directory and the designated branch.