A DevOps team is using Terraform to manage their infrastructure across multiple environments. Currently, the Terraform state file is stored locally on a developer's machine. The team decides to…

Question

Options

• AIt eliminates the need to define provider configurations in the state file.
• BIt ensures that the state file is encrypted.
• CIt prevents the accidental deletion of the state file.
• DIt enables collaboration among multiple team members.

• B
  7% (1)
• C
  7% (1)
• D
  87% (13)

Explanation

Storing Terraform state remotely enables team collaboration (D) because multiple developers can reference the same shared state file, preventing conflicts where two engineers might apply changes based on stale or out-of-sync local state - a critical problem in any team environment.

Why the distractors are wrong:

• A is wrong: provider configurations live in .tf files, not the state file, and remote backends don't change that.
• B is wrong: encryption is possible with some backends (like S3 with SSE), but it's not guaranteed or inherent to remote storage itself - it's a separate configuration concern.
• C is wrong: remote storage doesn't inherently prevent deletion; a team member or misconfigured pipeline could still delete it. Versioning and access controls address this, but they're separate features.

Memory tip: Think of remote state as a shared whiteboard - if one developer keeps the whiteboard in their desk drawer, nobody else can see the current picture. Moving it to a shared wall (remote backend) is fundamentally about visibility and collaboration, which maps directly to D.

No community discussion yet for this question.