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.
A retail organization recently completed a major peak sales event on Google Cloud. During the event, a critical microservice suffered intermittent downtime when backend database connections were exhausted following an unexpected spike in checkout transactions. The on-call operations team mitigated the outage by restarting backend instances and manually raising connection limits.
Now that the event has concluded, the cloud architecture team is initiating the analysis phase. Which approach should the team adopt to conduct an effective root cause analysis and post-mortem to prevent future recurrence?
This approach represents a punitive, blame-centric review that seeks to attribute failure to individual human error rather than identifying systemic and architectural vulnerabilities.
The organization were conducting an internal security forensics audit specifically targeting malicious insider activity or policy violations, rather than conducting an operational incident post-mortem.
This option immediately implements a complex architectural redesign (multi-region database migration) based on premature assumptions without conducting a structured root cause analysis (RCA) or reviewing operational metrics.
A thorough root cause analysis had already established that regional compute/storage capacity limits were exceeded and business continuity requirements mandated cross-region failover.
This approach treats incident mitigation as the completion of the incident lifecycle, neglecting the essential analysis phase and post-mortem review entirely.
The incident was a confirmed false positive or an external network probe requiring no infrastructure adjustments or internal process changes.
A blameless post-mortem and structured root cause analysis (RCA) process is an operational methodology designed to investigate system failures, understand why failures occurred, and build systemic guardrails against recurrence without pointing fingers or punishing individuals.
This approach directly aligns with established event management best practices and Google Site Reliability Engineering (SRE) principles. It transforms an operational failure into actionable architectural enhancements without creating organizational friction.
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 Validated