Cloud Digital Leader Scaling with Google Cloud operations Practice Question
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?
⚠ Common exam trap
A common mix-up: 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.
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
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.
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 longer maintenance windows during off-peak hours assumes a relatively quiet period and reduces the number of users affected, but it still leaves the service unavailable for that block of time. Global applications often have no true off-peak period, and increasing the window length multiplies the exposure window for any lingering issue. This approach tries to minimize the blast radius of downtime rather than eliminate it, which is precisely what the SRE team is pushing back against.
- ✓
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.
- ✗
Notifying customers in advance of the maintenance window and offering service credits for the downtime
Why it's wrong here
Advance notification and service credits address the customer relationship and financial compensation, but they do nothing to keep the service running during the maintenance. Notifying customers sets expectations for the outage, while credits are a post-hoc remedy for the impact—neither changes the technical reality that the workload is unavailable. The SRE argument is not about mitigating the consequences of downtime but about architecting so that maintenance requires no downtime at all, which communication and credits cannot achieve.
- ✗
Backing up all data before the maintenance window to ensure recovery if something goes wrong
Why it's wrong here
Taking backups prior to a maintenance window is a defensive, recovery-oriented practice: it protects against data corruption or loss by allowing restore to a known-good state. However, it does not prevent the service from being unavailable during the maintenance itself, and the restore process adds further downtime. Backups are a safety net for failure, not a mechanism for continuous availability, so they cannot satisfy the SRE team's goal of eliminating planned downtime entirely.
Go deeper
Related to this question
Learn chapter
Cost Optimisation Strategies on GCP
Key term
Google Cloud
Google Cloud is a suite of cloud computing services offered by Google that provides infrastructure, platform, and software solutions over the internet.
Key term
Service
A service is a software component or system that performs a specific function and is available to be used by other programs or users over a network.
About these practice questions
Courseiva writes every GCDL question from scratch — 848 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.