- A
One branch per cluster, with manual merge from development to production branches.
Why wrong: This is not a standard branching strategy and does not leverage GitOps automation effectively.
- B
Trunk-based development where all changes are merged into the main branch frequently, and Config Sync watches the main branch.
Trunk-based development ensures that main branch is always the single source of truth, which is ideal for GitOps.
- C
Gitflow with separate develop and release branches, merging to main only for production releases.
Why wrong: Gitflow is overly complex for GitOps; delays between merge and deployment contradict the 'desired state' model.
- D
Feature branching with long-lived branches per environment (dev, staging, prod).
Why wrong: This leads to drift between branches and requires manual promotion, defeating GitOps automation.
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 company is adopting GitOps for managing their Kubernetes infrastructure with Config Sync. They want to ensure that any changes to the cluster's desired state are automatically applied from a Git repository. Which branching strategy is MOST suitable for this workflow?
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
Trunk-based development where all changes are merged into the main branch frequently, and Config Sync watches the main branch.
Trunk-based development with short-lived feature branches and direct commits to main (or a single release branch) is the simplest and most aligned with GitOps principles where main branch represents the desired state.
Key principle: A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
One branch per cluster, with manual merge from development to production branches.
Why it's wrong here
This is not a standard branching strategy and does not leverage GitOps automation effectively.
- ✓
Trunk-based development where all changes are merged into the main branch frequently, and Config Sync watches the main branch.
- ✗
Gitflow with separate develop and release branches, merging to main only for production releases.
Why it's wrong here
Gitflow is overly complex for GitOps; delays between merge and deployment contradict the 'desired state' model.
- ✗
Feature branching with long-lived branches per environment (dev, staging, prod).
Why it's wrong here
This leads to drift between branches and requires manual promotion, defeating GitOps automation.
Common exam traps
Common exam trap: an active trunk can still block the VLAN you need
A trunk being up does not prove every VLAN is crossing it. Check allowed VLAN lists, native VLAN mismatch, VLAN existence and access-port assignment.
Detailed technical explanation
How to think about this question
VLAN questions usually combine access-port and trunking clues. The key is to identify whether the issue is local to one switchport, caused by the trunk, or caused by the VLAN not existing where it needs to exist.
KKey Concepts to Remember
- Access ports place end devices into a single VLAN.
- Trunk ports carry multiple VLANs between switches.
- Allowed VLAN lists decide which VLANs can cross a trunk.
- Native VLAN mismatch can create confusing symptoms.
TExam Day Tips
- Use show vlan brief to verify access VLANs.
- Use show interfaces trunk to verify trunk state and allowed VLANs.
- Do not treat every same-VLAN issue as a routing problem.
Key takeaway
A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related PCDE questions on switching, trunking, and access-port configuration.
- →
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 — Access ports place end devices into a single VLAN..
What is the correct answer to this question?
The correct answer is: Trunk-based development where all changes are merged into the main branch frequently, and Config Sync watches the main branch. — Trunk-based development with short-lived feature branches and direct commits to main (or a single release branch) is the simplest and most aligned with GitOps principles where main branch represents the desired state.
What should I do if I get this PCDE question wrong?
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related PCDE questions on switching, trunking, and access-port configuration.
What is the key concept behind this question?
Access ports place end devices into a single VLAN.
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 →
Keep practising
More PCDE practice questions
- A company stores sensor data in BigQuery. They have a table 'sensor_readings' with columns: sensor_id, reading_time, val…
- Which THREE are valid considerations when designing BigQuery tables for BI reporting?
- A company uses Cloud Build to build Docker images. They want to cache intermediate layers to speed up subsequent builds.…
- A company is adopting GitOps for their GKE clusters using Config Sync. They need to meet the following requirements: (1)…
- A team is migrating an on-premises PostgreSQL database to Cloud SQL for PostgreSQL. The existing schema uses a large num…
- A DevOps engineer is setting up Docker credential helper for Artifact Registry on a Cloud Build worker. They want the bu…
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.