Exam Terraform Associate topic 1 question 330 discussion

False as speculative plan runs in Terraform Cloud do not automatically start

In a Terraform Cloud or HCP Terraform workspace linked to a version control system (VCS) repository, speculative plan runs are not automatically triggered when changes are merged or committed to the repository. Instead, speculative plans are typically triggered when a pull request or merge request is created or updated, allowing teams to preview the potential impact of proposed changes before they are merged into the main branch. Once changes are merged, Terraform runs (not speculative plans) are triggered to apply the updates A speculative plan is automatically created in VCS-backed Terraform Cloud workspaces when a pull request is opened or updated, allowing teams to preview changes without affecting real infrastructure A regular plan can be saved and later applied, enabling controlled execution of infrastructure changes

1. SHOULD BE SETUP, NOT SOMETHING AUTOMATIC AND 2. SPECULATIVE PLANS TYPICALLY ARE DONE UPON PR OR MR

False Speculative plans only run when you have Pull requests or Merge request

https://developer.hashicorp.com/terraform/cloud-docs/run/ui#automatically-starting-runs

B. False Speculative plan runs in Terraform Cloud do not automatically start with every commit or merge. They are a feature that can be triggered manually or as part of specific workflows but do not automatically execute with every change in the version control system.