- A
Store state in a single file and use IAM to allow only one user at a time.
Why wrong: IAM cannot enforce serial execution across users.
- B
Use `terraform force_unlock` before each run.
Why wrong: That is a manual override that can cause corruption if used incorrectly.
- C
Configure the GCS backend with `prefix` per project and rely on Terraform's built-in state locking via GCS.
GCS backend automatically uses locking via object writes. Using separate prefixes isolates states, and locking prevents concurrent operations.
- D
Enable object versioning on the GCS bucket.
Why wrong: Versioning helps with recovery but does not prevent concurrent modifications.
Question 771 of 1,000
PCDE Practice Question: Bootstrapping a Google Cloud Organisation for DevOps
This PCDE practice question tests your understanding of bootstrapping a google cloud organisation for devops. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
A team manages Terraform state for multiple projects using a single GCS bucket. They need to ensure that state operations are not concurrent to avoid corruption. What should they do?
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
✓
Configure the GCS backend with `prefix` per project and rely on Terraform's built-in state locking via GCS.
Option C is correct because Terraform's GCS backend natively supports state locking using the GCS object's generation number. By configuring a unique `prefix` per project, each project's state is stored in a separate object within the same bucket. Terraform automatically acquires a lock by creating a temporary lock file in GCS before any state operation, and releases it afterward, preventing concurrent modifications and state corruption.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store state in a single file and use IAM to allow only one user at a time.
Why it's wrong here
IAM cannot enforce serial execution across users.
- ✗
Use `terraform force_unlock` before each run.
Why it's wrong here
That is a manual override that can cause corruption if used incorrectly.
- ✓
Configure the GCS backend with `prefix` per project and rely on Terraform's built-in state locking via GCS.
Why this is correct
GCS backend automatically uses locking via object writes. Using separate prefixes isolates states, and locking prevents concurrent operations.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Enable object versioning on the GCS bucket.
Why it's wrong here
Versioning helps with recovery but does not prevent concurrent modifications.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse object versioning (which provides history) with state locking (which prevents concurrent writes), or think that IAM alone can manage concurrency, when in fact Terraform's built-in locking via GCS is the correct and automated solution.
Detailed technical explanation
How to think about this question
Under the hood, Terraform's GCS backend uses a separate lock object (e.g., `.terraform.lock`) that is created with a specific generation ID. When a state operation begins, Terraform attempts to create this lock object; if it already exists, the operation fails with a locking error. The `prefix` configuration ensures each project's state and lock files are isolated, allowing multiple projects to use the same bucket safely. In real-world scenarios, teams often combine this with bucket lifecycle policies to clean up stale lock files.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Visual reference
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.
- →
Bootstrapping a Google Cloud Organisation for DevOps — study guide chapter
Learn the concepts, then practise the questions
- →
Bootstrapping a Google Cloud Organisation for DevOps practice questions
Targeted practice on this topic area only
- →
All PCDE questions
1,000 questions across all exam domains
- →
Google Professional Cloud Database Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCDE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Building and Implementing CI/CD Pipelines for a Service practice questions
Practise PCDE questions linked to Building and Implementing CI/CD Pipelines for a Service.
Bootstrapping a Google Cloud Organisation for DevOps practice questions
Practise PCDE questions linked to Bootstrapping a Google Cloud Organisation for DevOps.
Applying Site Reliability Engineering Practices to a Service practice questions
Practise PCDE questions linked to Applying Site Reliability Engineering Practices to a Service.
Implementing Service Monitoring Strategies practice questions
Practise PCDE questions linked to Implementing Service Monitoring Strategies.
Optimising Service Performance practice questions
Practise PCDE questions linked to Optimising Service Performance.
Plan and manage database infrastructure practice questions
Practise PCDE questions linked to Plan and manage database infrastructure.
Define data structures and implement SQL for Business Intelligence practice questions
Practise PCDE questions linked to Define data structures and implement SQL for Business Intelligence.
Design and implement database schemas practice questions
Practise PCDE questions linked to Design and implement database schemas.
Monitor and optimize database performance practice questions
Practise PCDE questions linked to Monitor and optimize database performance.
PCDE fundamentals practice questions
Practise PCDE questions linked to PCDE fundamentals.
PCDE scenario practice questions
Practise PCDE questions linked to PCDE scenario.
PCDE troubleshooting practice questions
Practise PCDE questions linked to PCDE troubleshooting.
Practice this exam
Start a free PCDE 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 PCDE question test?
Bootstrapping a Google Cloud Organisation for DevOps — This question tests Bootstrapping a Google Cloud Organisation for DevOps — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure the GCS backend with `prefix` per project and rely on Terraform's built-in state locking via GCS. — Option C is correct because Terraform's GCS backend natively supports state locking using the GCS object's generation number. By configuring a unique `prefix` per project, each project's state is stored in a separate object within the same bucket. Terraform automatically acquires a lock by creating a temporary lock file in GCS before any state operation, and releases it afterward, preventing concurrent modifications and state corruption.
What should I do if I get this PCDE 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 →
Last reviewed: Jul 4, 2026
This PCDE practice question is part of Courseiva's free Google Cloud 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 PCDE exam.
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.
Sign in to join the discussion.