Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An e-commerce platform running on Google Cloud uses Regional Managed Instance Groups (MIGs) behind an external Application Load Balancer, with Cloud Monitoring tracking Service Level Indicators (SLIs) against a 99.99% availability Service Level Objective (SLO). The Site Reliability Engineering (SRE) team wants to conduct a chaos engineering experiment in a staging environment that mirrors production to validate that automated recovery mechanisms function properly during infrastructure disruptions without exceeding the allocated error budget.
Which strategy should the team implement to design and validate this failure injection experiment?
Chaos engineering is the discipline of experimenting on a system to build confidence in its capability to withstand turbulent conditions in production. Combining chaos engineering with Site Reliability Engineering (SRE) principles involves defining a steady-state baseline using Service Level Indicators (SLIs) and verifying that automated resilience mechanisms operate within the boundaries of the defined Service Level Objectives (SLOs) and error budgets.

This method aligns with Google Cloud reliability engineering best practices. It tests the resilience of regional compositions against zonal failure domains, verifies automated platform recovery primitives (MIG autohealing and load balancer failover), and uses empirical SRE metrics to measure overall system health.
This approach simulates a catastrophic total-system outage by deliberately turning off load balancer health probing and destroying all running VM capacity across every zone, forcing operations teams to perform manual instance recreation and routing.
This strategy would be appropriate for a manual Disaster Recovery (DR) exercise designed strictly to test operational runbooks and personnel escalation paths in the event of an unrecoverable multi-zone catastrophe where all automated systems have failed.
This approach configures the Managed Instance Group autoscaler to an extreme target utilization (100%) and prevents horizontal scaling, allowing incoming traffic to overwhelm compute instances until CPU exhaustion causes request failures.
The objective were stress testing or capacity bottleneck identification to determine the breaking point of an individual VM's web server software under extreme computational load.
This option involves triggering Google Cloud's native live migration maintenance mechanism to move running VM instances to alternative physical hosts within the same zone without application downtime.
The team wanted to verify that specialized, performance-sensitive workloads do not experience unacceptable CPU jitter during underlying Google Cloud hypervisor maintenance.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated