When managing provider credentials across workspaces with variable sets, what is the scope of a variable set?

It can be applied to multiple workspaces within the same organization

It can only be applied to workspaces in the same project

It is limited to a single workspace and cannot be shared

It is global and applies to all workspaces in all organizations

What is the recommended approach to rotate a provider credential in HCP Terraform without disrupting existing runs?

Update the sensitive variable's value in the workspace or variable set, and the new value will be used in subsequent runs

Wait for HCP Terraform to automatically detect and update the credential

Delete the workspace and recreate it with the new credential

Modify the provider block in the configuration to include the new credential

A security audit requires that all provider credentials in HCP Terraform be rotated immediately. You have updated the credentials in the variable set. What is the next step to ensure the new credentials are used?

Wait for the next scheduled run to use the new credentials.

Run a new plan in each workspace to verify the credentials work.

Restart the HCP Terraform agent to pick up the new credentials.

Delete the old credentials from the variable set.

Your team is adopting HCP Terraform and needs to store provider credentials for multiple cloud providers (AWS, Azure, GCP) securely. You want to ensure that the credentials are encrypted at rest and not visible in the UI or logs. What is the recommended way to store these credentials in HCP Terraform?

Store them as sensitive variables in variable sets or workspace variables.

Store them in the Terraform configuration files as variables with default values.

Store them in a shared backend configuration file.

Store them in a public GitHub repository and reference them in the configuration.

Which of the following is a valid use case for configuring provider credentials as environment variables in an HCP Terraform variable set?

To allow the credentials to be used only in the local development environment

To automatically rotate the credentials every time a run is triggered

To make the credentials available to all workspaces that apply the variable set, without hardcoding them in configuration

To store the credentials in the Terraform state file for easy retrieval

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 6Objective 3

6c TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 4)

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 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

6concepts

Questions 16–20

16foundation · easy
When managing provider credentials across workspaces with variable sets, what is the scope of a variable set?
Select an answer first
17foundation · easy
What is the recommended approach to rotate a provider credential in HCP Terraform without disrupting existing runs?
Select an answer first
18application · medium
A security audit requires that all provider credentials in HCP Terraform be rotated immediately. You have updated the credentials in the variable set. What is the next step to ensure the new credentials are used?
Select an answer first
19application · medium
Your team is adopting HCP Terraform and needs to store provider credentials for multiple cloud providers (AWS, Azure, GCP) securely. You want to ensure that the credentials are encrypted at rest and not visible in the UI or logs. What is the recommended way to store these credentials in HCP Terraform?
Select an answer first
20foundation · easy
Which of the following is a valid use case for configuring provider credentials as environment variables in an HCP Terraform variable set?
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.