Terraform Associate (004) · Free practice question 6 of 12
Run triggers between workspaces
At Calloway Retail, an application workspace reads networking outputs from a network workspace in HCP Terraform. The team wants the application workspace to queue a run automatically after each successful apply in the network workspace. Which feature does this?
- A.A Sentinel policy that references both workspaces
- B.A variable set shared by both workspaces
- C.A run trigger on the application workspace with the network workspace as its source
- D.A run task attached to the network workspace's post-plan stage
Show answer and explanation
Correct answer: C. A run trigger on the application workspace with the network workspace as its source
Why: Run triggers connect workspaces so that a successful apply in a source workspace queues a run in the dependent workspace. Sentinel policies evaluate runs rather than starting them. Variable sets share variable values, and run tasks call external services during a run instead of starting runs elsewhere.
More free Terraform Associate (004) questions
- Skipping refresh during plan
- Local state backup file
- Default CLI workspace cannot be deleted
- Local execution mode in HCP Terraform
- Self-hosted agents for private networks
- Health assessments for drift detection
- Dynamic provider credentials with OIDC
- terraform_data triggers_replace argument
- Provisioners as a last resort
- Running tests with terraform test
- Lock file hashes for multiple platforms