Question 71 of 519
Implement and maintain statemediumMultiple SelectObjective-mapped

Quick Answer

The correct answer is that four key statements about Terraform state management are accurate: remote state backends support locking to prevent concurrent modifications, `terraform state rm` removes a resource from state without destroying infrastructure, encrypting the state backend at rest protects sensitive data, and `terraform import` updates the state file to include an existing resource. These practices are essential because Terraform state maps real-world resources to your configuration, and mismanagement can lead to drift, corruption, or security leaks. On the HashiCorp Terraform Associate TF-003 exam, this topic tests your understanding of how state locking, removal, encryption, and import work together to maintain consistency and safety. A common trap is confusing `terraform state rm` with `terraform destroy`—the former only detaches management, while the latter deletes infrastructure. Remember the mnemonic "L.I.E.S." for Locking, Import, Encryption, and State rm to recall these four correct practices.

TF-003 Implement and maintain state Practice Question

This TF-003 practice question tests your understanding of implement and maintain state. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Which four of the following statements about Terraform state management are correct? (Choose all that apply. There are four correct answers.)

Question 1mediummulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Using remote state storage with a backend like S3 or Azure Storage provides locking to prevent concurrent modifications.

Remote state backends like S3 or Azure Storage support state locking (via DynamoDB or Azure Blob lease) to prevent concurrent modifications, ensuring consistency. The `terraform state rm` command removes a resource from state without destroying the real infrastructure, which is useful for detaching management. Encrypting the state backend at rest (e.g., S3 server-side encryption or Azure Storage encryption) protects sensitive data like passwords or keys stored in the state file. The `terraform import` command updates the state file to include an existing resource, allowing Terraform to take over its management without recreating it.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Common exam traps

Common exam trap: answer the scenario, not the keyword

HashiCorp often tests the misconception that `terraform state list` can modify state or that automatic backups are built-in, when in fact Terraform requires explicit backend versioning or manual backup configuration.

Detailed technical explanation

How to think about this question

State locking mechanisms vary by backend: S3 uses DynamoDB for consistency, while Azure Storage uses blob leases. The `terraform state rm` command does not affect the real infrastructure, but subsequent plans may show the resource as 'to be created' if the configuration still references it. Terraform import requires the resource configuration to already exist in your code; otherwise, it will cause a plan to destroy the resource. Backend encryption at rest (e.g., AES-256 for S3) protects state data, but sensitive values may still be visible in logs or plan output unless you use `sensitive` parameters.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the TF-003 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related TF-003 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free TF-003 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this TF-003 question test?

Implement and maintain state — This question tests Implement and maintain state — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Using remote state storage with a backend like S3 or Azure Storage provides locking to prevent concurrent modifications. — Remote state backends like S3 or Azure Storage support state locking (via DynamoDB or Azure Blob lease) to prevent concurrent modifications, ensuring consistency. The `terraform state rm` command removes a resource from state without destroying the real infrastructure, which is useful for detaching management. Encrypting the state backend at rest (e.g., S3 server-side encryption or Azure Storage encryption) protects sensitive data like passwords or keys stored in the state file. The `terraform import` command updates the state file to include an existing resource, allowing Terraform to take over its management without recreating it.

What should I do if I get this TF-003 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This TF-003 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the TF-003 exam.