- A
Longer maintenance windows scheduled during off-peak hours to minimize customer impact
Why wrong: Scheduling maintenance during off-peak hours reduces impact but doesn't eliminate downtime. The SRE team's argument is that downtime should not be necessary at all with proper cloud architecture.
- B
Zero-downtime deployment strategies like rolling updates and blue/green deployments, combined with cloud live migration for infrastructure maintenance
This is the architectural answer to planned downtime. Rolling updates deploy new code gradually (some instances get new version while others serve traffic). Blue/green deployments switch traffic atomically. Live migration moves VMs between physical hosts for maintenance without rebooting. Together, these eliminate the need for maintenance windows.
- C
Notifying customers in advance of the maintenance window and offering service credits for the downtime
Why wrong: Customer notification is a communication best practice but doesn't eliminate the downtime. The SRE argument is that the downtime itself should be eliminated through architecture.
- D
Backing up all data before the maintenance window to ensure recovery if something goes wrong
Why wrong: Backup is a resilience measure but doesn't prevent downtime during the maintenance window. It would allow recovery if the maintenance causes data loss, but customers still experience unavailability during the window.
Quick Answer
The answer is zero-downtime deployment strategies like rolling updates and blue/green deployments, combined with cloud live migration for infrastructure maintenance. These capabilities eliminate planned downtime because rolling updates incrementally replace instances without dropping traffic, blue/green deployments switch user traffic to a fully updated environment before decommissioning the old one, and live migration transparently moves running VMs between physical hosts with no OS or application interruption. On the Google Cloud Digital Leader exam, this concept tests your understanding of how cloud architecture removes the need for traditional maintenance windows, often appearing in scenario-based questions where an SRE team argues against scheduled downtime. A common trap is assuming maintenance windows are unavoidable, but the correct insight is that cloud-native strategies decouple infrastructure updates from service availability. Memory tip: think of “swap and slide”—blue/green swaps environments while live migration slides VMs between hosts, keeping the service always on.
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 product team is discussing how to handle a planned 48-hour maintenance window for a critical customer-facing service. The SRE team argues the maintenance window is unnecessary with proper cloud architecture. Which cloud capability eliminates the need for planned downtime maintenance windows?
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
Zero-downtime deployment strategies like rolling updates and blue/green deployments, combined with cloud live migration for infrastructure maintenance
Option B is correct because cloud platforms like Google Cloud support zero-downtime deployment strategies (rolling updates, blue/green deployments) and live migration for infrastructure maintenance. Live migration transparently moves running VMs between hosts without interrupting the OS or applications, while blue/green deployments allow traffic to be switched to a fully updated environment before the old one is taken down. Together, these capabilities eliminate the need for planned downtime maintenance windows entirely.
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.
- ✗
Longer maintenance windows scheduled during off-peak hours to minimize customer impact
Why it's wrong here
Scheduling maintenance during off-peak hours reduces impact but doesn't eliminate downtime. The SRE team's argument is that downtime should not be necessary at all with proper cloud architecture.
- ✓
Zero-downtime deployment strategies like rolling updates and blue/green deployments, combined with cloud live migration for infrastructure maintenance
Why this is correct
This is the architectural answer to planned downtime. Rolling updates deploy new code gradually (some instances get new version while others serve traffic). Blue/green deployments switch traffic atomically. Live migration moves VMs between physical hosts for maintenance without rebooting. Together, these eliminate the need for maintenance windows.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Notifying customers in advance of the maintenance window and offering service credits for the downtime
Why it's wrong here
Customer notification is a communication best practice but doesn't eliminate the downtime. The SRE argument is that the downtime itself should be eliminated through architecture.
- ✗
Backing up all data before the maintenance window to ensure recovery if something goes wrong
Why it's wrong here
Backup is a resilience measure but doesn't prevent downtime during the maintenance window. It would allow recovery if the maintenance causes data loss, but customers still experience unavailability during the window.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'reducing impact' (options A, C, D) with 'eliminating downtime' (option B), failing to recognize that only architectural strategies like live migration and zero-downtime deployments remove the need for a maintenance window altogether.
Detailed technical explanation
How to think about this question
Live migration in Google Compute Engine uses pre-copy memory synchronization and a final stop-and-copy phase that typically completes in under 100 ms, making the transition imperceptible to most workloads. Blue/green deployments rely on a load balancer (e.g., Google Cloud HTTP(S) Load Balancer) to shift traffic from the 'blue' environment to the 'green' environment with no connection draining delay when using session affinity. This architecture ensures that even kernel-level updates (e.g., hypervisor patches) can be applied without any customer-facing interruption.
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: Zero-downtime deployment strategies like rolling updates and blue/green deployments, combined with cloud live migration for infrastructure maintenance — Option B is correct because cloud platforms like Google Cloud support zero-downtime deployment strategies (rolling updates, blue/green deployments) and live migration for infrastructure maintenance. Live migration transparently moves running VMs between hosts without interrupting the OS or applications, while blue/green deployments allow traffic to be switched to a fully updated environment before the old one is taken down. Together, these capabilities eliminate the need for planned downtime maintenance windows entirely.
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 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.