- A
Feature branching with long-lived branches for each environment (dev, staging, prod).
Why wrong: Long-lived branches lead to drift and manual merges, contradicting GitOps principles.
- B
Trunk-based development with short-lived feature branches and automated CI/CD pipelines that apply changes upon merge to main.
This aligns with GitOps: main is the source of truth, and merges trigger automated deployment.
- C
Each team maintains its own fork and periodically submits pull requests to a central repository.
Why wrong: Forking is more common for open-source; in a monorepo, it adds overhead and can delay integration.
- D
GitFlow with separate branches for develop, release, and hotfixes.
Why wrong: GitFlow introduces long-lived branches, which can cause divergence and is not ideal for GitOps where main should reflect desired state.
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.
An organization uses Terraform to manage infrastructure across multiple teams. They want to implement a branching strategy that supports rapid iteration and continuous integration for infrastructure changes while ensuring that the main branch always reflects the desired state. Which Git branching model is most aligned with GitOps principles for IaC?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"always"Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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 with short-lived feature branches and automated CI/CD pipelines that apply changes upon merge to main.
Trunk-based development with short-lived feature branches is recommended for GitOps. Developers branch off main, make changes, commit frequently, and merge back to main after automated testing. This keeps main deployable and reduces merge conflicts.
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.
- ✗
Feature branching with long-lived branches for each environment (dev, staging, prod).
Why it's wrong here
Long-lived branches lead to drift and manual merges, contradicting GitOps principles.
- ✓
Trunk-based development with short-lived feature branches and automated CI/CD pipelines that apply changes upon merge to main.
Why this is correct
This aligns with GitOps: main is the source of truth, and merges trigger automated deployment.
Clue confirmation
The clue word "always" in the question point toward this answer.
Related concept
Access ports place end devices into a single VLAN.
- ✗
Each team maintains its own fork and periodically submits pull requests to a central repository.
Why it's wrong here
Forking is more common for open-source; in a monorepo, it adds overhead and can delay integration.
- ✗
GitFlow with separate branches for develop, release, and hotfixes.
Why it's wrong here
GitFlow introduces long-lived branches, which can cause divergence and is not ideal for GitOps where main should reflect desired state.
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 with short-lived feature branches and automated CI/CD pipelines that apply changes upon merge to main. — Trunk-based development with short-lived feature branches is recommended for GitOps. Developers branch off main, make changes, commit frequently, and merge back to main after automated testing. This keeps main deployable and reduces merge conflicts.
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.
Are there clue words in this question I should notice?
Yes — watch for: "always". Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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.