In HCP Terraform, what distinguishes a CLI-driven run from an API-driven run?
- AA CLI-driven run is started by running terraform commands locally against a workspace configured with a cloud block, while an API-driven run is triggered by uploading a configuration version through the runs API. Correct
- BA CLI-driven run always skips the plan phase, whereas an API-driven run always performs both plan and apply automatically.
- CA CLI-driven run can only execute against local state, while an API-driven run is the sole way to use remote state in a workspace.
- DA CLI-driven run requires a connected version control repository, while an API-driven run works without any workspace at all.
Why A is correct: Correct: CLI-driven runs originate from local terraform commands mapped to a workspace, whereas API-driven runs come from programmatically uploading a configuration version and creating a run via the API.
Why B is wrong: Tempting because the two feel like they should differ in phases, but both workflows run plan and apply; neither skips the plan stage by definition.
Why C is wrong: Plausible if you tie state location to trigger method, but both run types use the workspace's remote state; the trigger mechanism does not determine where state lives.
Why D is wrong: Sounds reasonable given VCS integration exists, but CLI-driven runs do not need a VCS connection, and every run, including API-driven, executes within a workspace.