Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise runs a business-critical workload on Google Cloud Compute Engine virtual machines within a regional Managed Instance Group (MIG) behind an external Application Load Balancer. The operations team is preparing a resiliency and disaster recovery testing protocol to validate high availability and failover mechanisms before a major production release.
The testing strategy must satisfy the following requirements:
Which testing and validation strategy should the team implement?
Rely on Compute Engine automatic guest reboot policies, trigger maintenance tests by executing gcloud compute instances reset, and use Cloud Profiler to track timeout exceptions.
Configure HTTP health checks on the MIG for application-level auto-healing, simulate platform maintenance on active instances using the gcloud compute instances simulate-maintenance-event command, and track telemetry with Cloud Monitoring.
Configure Cloud Armor rate limiting rules to block synthetic traffic, inject memory pressure by modifying instance templates in production, and monitor failovers using Cloud Deploy execution logs.
Configure regional persistent disks for data synchronization, invoke gcloud compute instances stop across all zones simultaneously, and monitor recovery status exclusively via the public Google Cloud Service Health RSS feed.
Rely on Compute Engine automatic guest reboot policies, trigger maintenance tests by executing gcloud compute instances reset, and use Cloud Profiler to track timeout exceptions.
Configure HTTP health checks on the MIG for application-level auto-healing, simulate platform maintenance on active instances using the gcloud compute instances simulate-maintenance-event command, and track telemetry with Cloud Monitoring.
This strategy combines Compute Engine auto-healing, proactive chaos/maintenance simulation, and Google Cloud Observability to thoroughly validate system resilience across application and infrastructure layers.
StudyCerts
StudyCertsgcloud compute instances simulate-maintenance-event initiates a simulated live migration on the running VM. This validates that the host migration occurs transparently without false-positive health check failures or disruptive, unnecessary failover actions.Using native HTTP health checks alongside the official maintenance simulation command provides realistic testing of both software-layer failures and platform-level infrastructure events without causing unmanaged outages.
Configure Cloud Armor rate limiting rules to block synthetic traffic, inject memory pressure by modifying instance templates in production, and monitor failovers using Cloud Deploy execution logs.
Configure regional persistent disks for data synchronization, invoke gcloud compute instances stop across all zones simultaneously, and monitor recovery status exclusively via the public Google Cloud Service Health RSS feed.