- A
Increase the application's max_instances so it scales to handle the issue automatically.
Why wrong: Scaling up helps with capacity incidents but doesn't address the process gap: who to contact, how to coordinate, and what steps to follow during any type of production incident.
- B
Establish a documented incident response process with defined roles, escalation paths, and runbooks, supported by on-call rotation tooling and Cloud Monitoring alerting.
Incident response process defines what to do and who to involve. Runbooks provide step-by-step guidance. On-call rotation ensures 24/7 coverage. Cloud Monitoring alerting ensures rapid notification.
- C
Move all production deployments to Sunday nights to avoid weekday incident risk.
Why wrong: Deployment timing affects deployment-related incident rates but doesn't improve incident response capability. Incidents can occur anytime from any cause.
- D
Disable monitoring alerts to prevent false alarms that wake engineers unnecessarily.
Why wrong: Disabling alerts is an operational anti-pattern that increases MTTD (mean time to detect). The issue is refining alert quality, not eliminating alerting.
Quick Answer
The correct operational practice is to establish a documented incident response process with defined roles, escalation paths, and runbooks, supported by on-call rotation tooling and Cloud Monitoring alerting. This approach directly addresses the core problem: without a runbook, the on-call engineer wasted time figuring out whom to contact and what steps to follow, which a clear, repeatable procedure would have eliminated. On-call rotation tooling ensures the right person is always notified, while runbooks provide step-by-step instructions for diagnosing and resolving P1 incidents, drastically reducing mean time to acknowledge and resolve. On the Google Cloud Digital Leader exam, this scenario tests your understanding of operational excellence and incident management best practices, often appearing as a trap where candidates confuse tooling alone with the need for a documented process. A common memory tip is to think of the "three R's": Roles, Runbooks, and Rotation—if any one is missing, incident response breaks down.
Cloud Digital Leader Scaling with Google Cloud operations Practice Question
This GCDL practice question tests your understanding of scaling with google cloud operations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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's application experiences a P1 (critical) production incident at 2 AM on a Sunday. The on-call engineer resolves the issue after 3 hours but isn't sure which team members to contact or what steps to follow during an incident. What operational practice and tooling would have helped manage this incident better?
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
Establish a documented incident response process with defined roles, escalation paths, and runbooks, supported by on-call rotation tooling and Cloud Monitoring alerting.
Option B is correct because a documented incident response process with defined roles, escalation paths, and runbooks ensures that the on-call engineer knows exactly whom to contact and what steps to follow during a P1 incident. Combined with on-call rotation tooling (e.g., PagerDuty, Opsgenie) and Cloud Monitoring alerting, this practice reduces mean time to acknowledge (MTTA) and mean time to resolve (MTTR) by providing clear, repeatable procedures. Without such a process, the engineer wasted time determining the response, which a runbook would have eliminated.
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.
- ✗
Increase the application's max_instances so it scales to handle the issue automatically.
Why it's wrong here
Scaling up helps with capacity incidents but doesn't address the process gap: who to contact, how to coordinate, and what steps to follow during any type of production incident.
- ✓
Establish a documented incident response process with defined roles, escalation paths, and runbooks, supported by on-call rotation tooling and Cloud Monitoring alerting.
Why this is correct
Incident response process defines what to do and who to involve. Runbooks provide step-by-step guidance. On-call rotation ensures 24/7 coverage. Cloud Monitoring alerting ensures rapid notification.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Move all production deployments to Sunday nights to avoid weekday incident risk.
Why it's wrong here
Deployment timing affects deployment-related incident rates but doesn't improve incident response capability. Incidents can occur anytime from any cause.
- ✗
Disable monitoring alerts to prevent false alarms that wake engineers unnecessarily.
Why it's wrong here
Disabling alerts is an operational anti-pattern that increases MTTD (mean time to detect). The issue is refining alert quality, not eliminating alerting.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that scaling or automation alone can replace a documented incident response process, but the question explicitly asks about operational practice and tooling for managing the incident, not just fixing the technical issue.
Detailed technical explanation
How to think about this question
Under the hood, an incident response runbook is often stored as a version-controlled document (e.g., in a Git repository) and integrated with on-call tooling via webhooks and escalation policies. For example, Cloud Monitoring can trigger an alert that pages the on-call engineer through PagerDuty, which then provides a link to the relevant runbook in a knowledge base. A subtle behavior is that runbooks should include specific commands (e.g., `gcloud logging read`, `kubectl describe pod`) and escalation contacts with time-based triggers (e.g., if unresolved after 15 minutes, escalate to the incident commander).
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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: Establish a documented incident response process with defined roles, escalation paths, and runbooks, supported by on-call rotation tooling and Cloud Monitoring alerting. — Option B is correct because a documented incident response process with defined roles, escalation paths, and runbooks ensures that the on-call engineer knows exactly whom to contact and what steps to follow during a P1 incident. Combined with on-call rotation tooling (e.g., PagerDuty, Opsgenie) and Cloud Monitoring alerting, this practice reduces mean time to acknowledge (MTTA) and mean time to resolve (MTTR) by providing clear, repeatable procedures. Without such a process, the engineer wasted time determining the response, which a runbook would have eliminated.
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 →
Last reviewed: Jun 30, 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.