Terraform Associate (004) · Free practice question 4 of 12
Local execution mode in HCP Terraform
Wyvern Tools wants to run Terraform on its own build servers but keep state in an HCP Terraform workspace. Which workspace execution mode fits?
- A.Remote, where every plan and apply runs on HCP Terraform's workers
- B.Speculative, where runs cannot apply changes
- C.Agent mode without any agent pool configured
- D.Local, where operations run on the machine that starts them and HCP Terraform stores state
Show answer and explanation
Correct answer: D. Local, where operations run on the machine that starts them and HCP Terraform stores state
Why: With local execution mode, plans and applies run on the user's or CI machine, and HCP Terraform is used to store and synchronize state. Remote execution runs operations on HCP Terraform's infrastructure. Speculative is a type of plan, not an execution mode, and agent mode requires an agent pool.
More free Terraform Associate (004) questions
- Skipping refresh during plan
- Local state backup file
- Default CLI workspace cannot be deleted
- Self-hosted agents for private networks
- Run triggers between workspaces
- 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