When updating a provider credential in HCP Terraform, what happens to runs that are currently in progress?

They are paused until the credential update is complete

They are immediately cancelled and restarted with the new credential

They continue with the old credential, and new runs use the updated credential

They fail with an authentication error

Your organization uses HCP Terraform to manage infrastructure across several workspaces that all authenticate to the same Azure subscription. You want to configure the Azure provider credentials once and have them applied to all relevant workspaces, while keeping the credentials out of the Terraform configuration files. What should you do?

Create a variable set with the Azure credentials as environment variables and apply it to all workspaces.

Add the Azure credentials as variables in each workspace's Terraform configuration.

Store the Azure credentials in a single workspace and use remote state to share them.

Use the Azure CLI to authenticate on the HCP Terraform runner before each run.

Your team manages multiple Terraform workspaces in HCP Terraform, each deploying AWS resources in different accounts. You need to configure AWS provider credentials so that each workspace authenticates with its own account, without embedding secrets in the Terraform code. What is the most appropriate way to achieve this?

Store the AWS credentials in a shared variable set and apply it to all workspaces.

Define the AWS access key and secret key as sensitive workspace variables in each workspace.

Use the AWS CLI on the HCP Terraform runner to authenticate before each run.

Hardcode the AWS credentials in the provider block of the Terraform configuration.

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 6Objective 3

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

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 21–23

21foundation · easy
When updating a provider credential in HCP Terraform, what happens to runs that are currently in progress?
Select an answer first
22application · medium
Your organization uses HCP Terraform to manage infrastructure across several workspaces that all authenticate to the same Azure subscription. You want to configure the Azure provider credentials once and have them applied to all relevant workspaces, while keeping the credentials out of the Terraform configuration files. What should you do?
Select an answer first
23application · medium
Your team manages multiple Terraform workspaces in HCP Terraform, each deploying AWS resources in different accounts. You need to configure AWS provider credentials so that each workspace authenticates with its own account, without embedding secrets in the Terraform code. What is the most appropriate way to achieve this?
Select an answer first

Finished these 3 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack 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.

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

Questions 21–23

When updating a provider credential in HCP Terraform, what happens to runs that are currently in progress?

Keep studying — Collaborate on infrastructure as code using HCP Terraform