Ultimate access to all questions.
You are designing a joint-ownership model for a service hosted on Google Cloud Platform (GCP) to improve collaboration between the DevOps team and the Software Development team. The DevOps team manages the service infrastructure and handles on-call responsibilities for incidents, while the Software Development team writes, submits, and reviews code. Neither team has established Service Level Objectives (SLOs). In the new joint-ownership model, how should responsibilities be assigned to each team to align with SRE best practices, ensure effective incident management, and support the creation and monitoring of SLOs using GCP tools?
A
DevOps Team: Fully responsible for defining and monitoring SLOs, managing infrastructure, and handling all on-call duties. Software Development Team: Solely responsible for writing and reviewing code, with no involvement in SLOs or incident response. Joint Responsibilities: None.
B
DevOps Team: Manages infrastructure, automates deployments using Cloud Build, and monitors SLOs using Cloud Monitoring. Software Development Team: Writes and tests code, participates in code reviews incorporating observability metrics, and shares on-call duties for application-level incidents. Joint Responsibilities: Co-develop SLOs and error budgets, conduct blameless post-incident reviews using Cloud Logging, and collaborate on CI/CD pipelines.
C
DevOps Team: Manages infrastructure and handles all incident response, including application-level issues. Software Development Team: Writes code and defines SLOs independently based on application performance metrics. Joint Responsibilities: Monitor SLOs using Cloud Monitoring and implement CI/CD pipelines using Cloud Build.
D
DevOps Team: Fully responsible for code development, infrastructure management, and incident response. Software Development Team: Only responsible for reviewing code and providing feedback. Joint Responsibilities: Define SLOs and monitor them using Cloud Monitoring.