What is the recommended way to secure access to a remote state backend?

Use IAM policies or role-based access control to restrict who can read and write the state

Disable encryption on the backend to simplify access

Share the backend credentials with all team members

Store the state in a public bucket to ensure availability

A small team is evaluating whether to move from local state to a remote backend. They are concerned about the complexity of setting up authentication and locking. Which benefit of remote state directly addresses their concern about concurrent modifications?

Remote state provides a central location for the state file, making it accessible to all team members

Remote state automatically encrypts the state file at rest

Remote state enables versioning of the state file for rollback

Remote state supports state locking, which prevents two team members from running apply at the same time

When using an AzureRM backend, how does Terraform authenticate to access the remote state?

By embedding a SAS token directly in the backend block

By specifying an access_key in the provider block

By using the Azure CLI only, with no other options

By using the same credentials as the AzureRM provider

An application team needs to reference a database connection string that is an output of a database team's Terraform configuration. The database team stores state in an AzureRM backend. The application team has been granted read access to the storage account. What should the application team do to retrieve the connection string?

Add a resource "terraform_remote_state" block that points to the database team's backend

Use the Azure CLI to query the storage account for the state file and parse it manually

Add a data "terraform_remote_state" block that points to the database team's backend and reference the output

Ask the database team to output the connection string to a file and share it

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 3Objective 2

3b TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 1)

Part of the Develop collaborative Terraform workflows 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 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

8concepts

Questions 1–5

1foundation · medium
What is the recommended way to secure access to a remote state backend?
Select an answer first
2application · easy
A small team is evaluating whether to move from local state to a remote backend. They are concerned about the complexity of setting up authentication and locking. Which benefit of remote state directly addresses their concern about concurrent modifications?
Select an answer first
3foundation · medium
When using an AzureRM backend, how does Terraform authenticate to access the remote state?
Select an answer first
4application · medium
An application team needs to reference a database connection string that is an output of a database team's Terraform configuration. The database team stores state in an AzureRM backend. The application team has been granted read access to the storage account. What should the application team do to retrieve the connection string?
Select an answer first
5foundation · medium
What is the default workspace name in 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.

3b TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 1)

Questions 1–5

What is the recommended way to secure access to a remote state backend?

A small team is evaluating whether to move from local state to a remote backend. They are concerned about the complexity of setting up authentication and locking. Which benefit of remote state directly addresses their concern about concurrent modifications?

When using an AzureRM backend, how does Terraform authenticate to access the remote state?

What is the default workspace name in Terraform?

Keep studying — Develop collaborative Terraform workflows