Which of these statements about HCP Terraform/Terraform Cloud workspaces is false?

The statement that you must use the Command Line Interface (CLI) to switch between HCP Terraform/Terraform Cloud workspaces is false. Workspaces are primarily managed and navigated through the web-based user interface (UI). Within the UI, users can select and switch between different workspaces to view their states, variables, and run histories. While the CLI can be configured to target a specific remote workspace for CLI-driven runs, it is not the exclusive method for interaction. The UI provides a complete graphical environment for managing and switching between workspaces, which is a fundamental aspect of the platform's user experience.

A. HCP Terraform/Terraform Cloud workspaces are designed to securely store secrets, including cloud credentials, as sensitive variables, preventing their exposure in the UI or logs.

B. The platform provides granular role-based access controls (RBAC), allowing organizations to assign specific permissions (e.g., read, plan, apply) to teams for each workspace.

C. A core feature is the version control system (VCS) driven workflow, where commits to a connected repository can automatically trigger terraform plan and terraform apply operations.

1. HashiCorp Terraform Documentation, "Workspaces": This document describes workspaces as "separate working directories for a single Terraform configuration." It details management through both the UI and API, contradicting the claim that the CLI is mandatory. (Refer to the "Terraform Cloud and Terraform Enterprise" section).

2. HashiCorp Terraform Documentation, "Permissions": This page outlines the role-based access control system in HCP Terraform, explaining how permissions are granted to users and teams on a per-workspace basis. (Refer to the "Workspace Permissions" table).

3. HashiCorp Terraform Documentation, "VCS-Driven Workflow": This guide explains how to connect a workspace to a version control repository. It states, "When you push changes to your VCS repository, Terraform Cloud can automatically queue a plan for your workspace." (Refer to the "Connect a Workspace to a VCS Repository" section).

4. HashiCorp Terraform Documentation, "Variables": This page details how to manage variables within workspaces, including the option to mark them as "Sensitive." It states, "Terraform Cloud and Terraform Enterprise always treat sensitive values as confidential." (Refer to the "Sensitive Variables" section).