Your organization has separate HCP Terraform workspaces for 'dev', 'staging', and 'prod' environments. Each workspace uses the same Terraform configuration from a single repository, but with different variable values. You need to ensure that a change to the configuration in the repository triggers runs in all three workspaces. What should you do?

Connect each workspace to the same repository and configure the same VCS branch and path.

Create a run trigger from the dev workspace to the staging and prod workspaces.

Use a single workspace and rely on Terraform CLI workspaces to manage the three environments.

Configure a webhook in the repository that calls the HCP Terraform API for each workspace.

Your team has a workspace that uses a VCS-driven workflow. You need to ensure that the workspace uses a specific Terraform version that is not the default version available in HCP Terraform. You also need to ensure that the workspace's runs use a specific working directory within the repository. What should you do?

Add a terraform block in the configuration to specify the required version and use a separate workspace for the working directory.

Use a variable to set the Terraform version and working directory.

Set the Terraform version and working directory in the workspace settings.

Create a new workspace for each configuration and use run triggers.

A workspace in HCP Terraform is no longer needed because the infrastructure it manages has been decommissioned. You have already run terraform destroy and confirmed that all resources are removed. What is the next step to clean up the workspace?

Delete the workspace from the HCP Terraform UI or API.

Lock the workspace to prevent accidental changes.

Remove the workspace from the VCS repository.

Change the execution mode to 'manual'.

A developer accidentally triggered a plan on the production workspace, and the plan is currently running. You need to prevent any further runs from starting while the current plan completes, but you do not want to cancel the running plan. What should you do?

Change the workspace's execution mode to 'manual'.

Lock the workspace from the workspace settings page.

Cancel the current run and then lock the workspace.

Remove the developer's access to the workspace.

What is the purpose of locking a workspace in HCP Terraform?

To permanently delete the workspace and its state

To prevent any user from making changes to the workspace configuration

To prevent new runs from being queued or executed until the lock is released

To restrict access to the workspace to only the workspace owner

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 6Objective 2

6b TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 2)

Part of the Collaborate on infrastructure as code using HCP Terraform domain, which makes up ~16% of our current practice bank. HashiCorp does not publish an official question count, but from its 240-minute exam (~95–160 total, ~15–26 in this domain), expect 4–7 from this objective — we provide 16 practice questions to prepare you well beyond it. (estimate)

16questions here

4free pages

4concepts

Questions 6–10

6application · medium
Your organization has separate HCP Terraform workspaces for 'dev', 'staging', and 'prod' environments. Each workspace uses the same Terraform configuration from a single repository, but with different variable values. You need to ensure that a change to the configuration in the repository triggers runs in all three workspaces. What should you do?
Select an answer first
7expert · hard
Your team has a workspace that uses a VCS-driven workflow. You need to ensure that the workspace uses a specific Terraform version that is not the default version available in HCP Terraform. You also need to ensure that the workspace's runs use a specific working directory within the repository. What should you do?
Select an answer first
8application · medium
A workspace in HCP Terraform is no longer needed because the infrastructure it manages has been decommissioned. You have already run terraform destroy and confirmed that all resources are removed. What is the next step to clean up the workspace?
Select an answer first
9application · medium
A developer accidentally triggered a plan on the production workspace, and the plan is currently running. You need to prevent any further runs from starting while the current plan completes, but you do not want to cancel the running plan. What should you do?
Select an answer first
10foundation · easy
What is the purpose of locking a workspace in HCP Terraform?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by HashiCorp. “TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL” is a trademark of its owner, used for identification only.

6b TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 2)

Questions 6–10

A workspace in HCP Terraform is no longer needed because the infrastructure it manages has been decommissioned. You have already run terraform destroy and confirmed that all resources are removed. What is the next step to clean up the workspace?

A developer accidentally triggered a plan on the production workspace, and the plan is currently running. You need to prevent any further runs from starting while the current plan completes, but you do not want to cancel the running plan. What should you do?

What is the purpose of locking a workspace in HCP Terraform?

Keep studying — Collaborate on infrastructure as code using HCP Terraform