Question

A retail company runs a customer-facing order platform on Google Cloud. During on-call rotations, engineers report that resolving production incidents takes far longer than expected because each engineer investigates issues differently, relies on tribal knowledge, and manually queries logs and metrics. Leadership wants to formalize the troubleshooting process to reduce mean time to resolution (MTTR) and make incident response repeatable across the team. Which approach best defines a consistent, effective troubleshooting process?

Accepted Answer

Create standardized, versioned runbooks for common failure scenarios that document diagnostic steps, key Cloud Monitoring dashboards and log queries, and escalation paths, and keep them current after each incident review.

Answer

Increase the size of the on-call rotation so that more engineers are available to investigate incidents in parallel whenever an alert fires.

Answer

Grant all on-call engineers Project Owner so they can access any resource immediately without waiting for permission escalations during an outage.

Answer

Disable non-critical alerting policies to reduce noise so that engineers only respond to the highest-severity pages.