- A
Manually applying Terraform changes from engineers' local machines and documenting changes in a shared wiki
Why wrong: Manual local applies with wiki documentation is not GitOps. There's no single source of truth (different engineers may have different local state), no automated reconciliation, and documentation diverges from actual state over time.
- B
Storing all infrastructure as code (Terraform or Config Connector) in a Git repository, using pull requests for all changes, and automated CI/CD pipelines that apply changes and detect drift from the declared state
This is GitOps. Git repo as truth: ✓. Pull request process for changes: ✓ (provides review, approval, audit trail). Automated reconciliation: ✓ (CI/CD applies changes and detects drift). This pattern makes infrastructure management reproducible, auditable, and collaborative.
- C
Using the Google Cloud Console to make infrastructure changes and exporting the configuration to Git after each change
Why wrong: Post-hoc export to Git is backwards GitOps — Git becomes a documentation store rather than the source of truth. Console changes that aren't reviewed via PR bypass governance controls.
- D
GitOps only applies to application code deployment, not to cloud infrastructure management
Why wrong: GitOps originated in application deployment but has been widely adopted for infrastructure management (infrastructure as code via Terraform, Pulumi, or Kubernetes-native Config Connector). It applies equally to both.
Quick Answer
The correct answer is storing all infrastructure as code in a Git repository, using pull requests for all changes, and automated CI/CD pipelines that apply changes and detect drift. This defines GitOps because it establishes Git as the single source of truth for your declarative infrastructure, meaning every change to your Google Cloud environment must first be proposed, reviewed, and merged through a pull request before an automated pipeline reconciles the live state with the declared state in the repository. On the Google Cloud Digital Leader exam, this question tests your understanding of how GitOps enforces version control, auditability, and drift detection at scale, often using tools like Terraform or Config Connector. A common trap is confusing GitOps with simple CI/CD automation—remember that GitOps requires the Git repo to be the authoritative source, not just a trigger for scripts. Memory tip: think “Git is the truth, PRs are the gate, pipelines are the hands.”
Cloud Digital Leader Scaling with Google Cloud operations Practice Question
This GCDL practice question tests your understanding of scaling with google cloud operations. 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 DevOps team wants to adopt GitOps practices for managing their Google Cloud infrastructure. Which combination of tools and practices defines a GitOps approach to cloud infrastructure management?
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
Storing all infrastructure as code (Terraform or Config Connector) in a Git repository, using pull requests for all changes, and automated CI/CD pipelines that apply changes and detect drift from the declared state
Option B is correct because GitOps is defined by using a Git repository as the single source of truth for declarative infrastructure, with pull requests driving changes and automated CI/CD pipelines reconciling the actual state with the declared state. This approach enforces version control, auditability, and drift detection, which are core to managing Google Cloud infrastructure at scale with tools like Terraform or Config Connector.
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.
- ✗
Manually applying Terraform changes from engineers' local machines and documenting changes in a shared wiki
Why it's wrong here
Manual local applies with wiki documentation is not GitOps. There's no single source of truth (different engineers may have different local state), no automated reconciliation, and documentation diverges from actual state over time.
- ✓
Storing all infrastructure as code (Terraform or Config Connector) in a Git repository, using pull requests for all changes, and automated CI/CD pipelines that apply changes and detect drift from the declared state
Why this is correct
This is GitOps. Git repo as truth: ✓. Pull request process for changes: ✓ (provides review, approval, audit trail). Automated reconciliation: ✓ (CI/CD applies changes and detects drift). This pattern makes infrastructure management reproducible, auditable, and collaborative.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Using the Google Cloud Console to make infrastructure changes and exporting the configuration to Git after each change
Why it's wrong here
Post-hoc export to Git is backwards GitOps — Git becomes a documentation store rather than the source of truth. Console changes that aren't reviewed via PR bypass governance controls.
- ✗
GitOps only applies to application code deployment, not to cloud infrastructure management
Why it's wrong here
GitOps originated in application deployment but has been widely adopted for infrastructure management (infrastructure as code via Terraform, Pulumi, or Kubernetes-native Config Connector). It applies equally to both.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse GitOps with simply storing code in Git (Option A) or think it only applies to applications (Option D), when in fact GitOps requires automated reconciliation and pull-request-driven workflows for infrastructure as code.
Detailed technical explanation
How to think about this question
Under the hood, GitOps relies on a reconciliation loop, often implemented by operators like Config Sync or Flux, that continuously compares the live state of Google Cloud resources against the desired state defined in the Git repository. If drift is detected (e.g., a manual change via the Console or an API call), the operator automatically reverts the resource to the declared state, ensuring self-healing infrastructure. In a real-world scenario, this prevents configuration drift during incident response, where an engineer might temporarily modify a firewall rule via the Console, only for the GitOps operator to restore it to the approved state within minutes.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
- →
Scaling with Google Cloud operations — study guide chapter
Learn the concepts, then practise the questions
- →
Scaling with Google Cloud operations practice questions
Targeted practice on this topic area only
- →
All GCDL questions
507 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Fundamental cloud concepts practice questions
Practise GCDL questions linked to Fundamental cloud concepts.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL 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 GCDL question test?
Scaling with Google Cloud operations — This question tests Scaling with Google Cloud operations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Storing all infrastructure as code (Terraform or Config Connector) in a Git repository, using pull requests for all changes, and automated CI/CD pipelines that apply changes and detect drift from the declared state — Option B is correct because GitOps is defined by using a Git repository as the single source of truth for declarative infrastructure, with pull requests driving changes and automated CI/CD pipelines reconciling the actual state with the declared state. This approach enforces version control, auditability, and drift detection, which are core to managing Google Cloud infrastructure at scale with tools like Terraform or Config Connector.
What should I do if I get this GCDL 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 →
Keep practising
More GCDL practice questions
- What is virtualization in the context of cloud computing, and why is it fundamental to how cloud providers deliver servi…
- A company stores its data in Google Cloud. The security team asks: can Google employees access our customer data without…
- A company is evaluating whether to use a content delivery network (CDN) for its e-commerce website. Which scenario would…
- A company's SRE team is debating whether to automate a frequently performed manual operational task. The automation woul…
- A startup is building an application that sends daily promotional push notifications to millions of mobile users on both…
- A development team uses Cloud Build to automatically build, test, and create container images whenever code is pushed to…
Last reviewed: Jun 11, 2026
This GCDL 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 GCDL 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.