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: Validate that the infrastructure automatically detects and recovers from application-level failures (such as process freezes or crashes). Verify that routine Compute Engine host maintenance does not inadvertently trigger unnecessary failovers or application downtime. Monitor performance metrics, uptime, and incident alerts during simulated failure scenarios. Which testing and validation strategy should the team implement?

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.: ### What this strategy is 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. ### How it meets the requirements - **Application-level recovery**: Configuring **HTTP health checks** on the Managed Instance Group (MIG) ensures that the group continuously monitors application health. If an application crashes or becomes unresponsive, the health check fails, and the MIG automatically recreates the unhealthy instance without manual intervention. - **Maintenance event validation**: Running `gcloud 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. - **Telemetry and monitoring**: **Cloud Monitoring** gathers performance metrics, error rates, and instance states during the simulated failures, enabling the team to evaluate system recovery times and alerting policies against their Service Level Objectives (SLOs). ### Key advantages and capabilities - **Automated instance recreation**: Ensures rapid recovery from software deadlocks, crashes, and memory exhaustion. - **Controlled chaos testing**: Allows safe validation of host maintenance resilience in staging or production environments. - **Unified observability**: Integrates metrics, logs, and dashboard alerts into a single management pane. - **Zero-touch recovery**: Confirms that high-availability failover mechanisms function autonomously. ### Why this is optimal 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.

StudyCerts

Resiliency Testing Compute Engine Mig Failover | 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! | StudyCerts

Professional Cloud Architect

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!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Resiliency Testing Compute Engine Mig Failover

Section: Testing and validation of software and infrastructure

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.

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:

Validate that the infrastructure automatically detects and recovers from application-level failures (such as process freezes or crashes).
Verify that routine Compute Engine host maintenance does not inadvertently trigger unnecessary failovers or application downtime.
Monitor performance metrics, uptime, and incident alerts during simulated failure scenarios.

Which testing and validation strategy should the team implement?

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.

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.

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 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.

Professional Cloud Architect

Resiliency Testing Compute Engine Mig Failover

Related questions