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!
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise e-commerce team is transitioning from traditional operations to Site Reliability Engineering (SRE) and DevOps practices in Google Cloud. During an operational readiness assessment, the team presents their proposed strategy for managing automated CI/CD releases alongside Service Level Objectives (SLOs).
Which proposed approach demonstrates proper operational readiness and alignment with SRE and DevOps methodologies?
Rely exclusively on virtual machine CPU and memory utilization thresholds as the primary SLIs to trigger automated deployment rollbacks
Bypass continuous integration automated testing suites and conduct manual exploratory testing directly in production whenever error budgets are low
Target a 100% availability SLO for every production microservice and mandate Change Advisory Board (CAB) manual approval for each automated pipeline execution
Define user-centric Service Level Indicators (SLIs) to determine an error budget, automate releases while the budget is positive, and pause non-essential deployments to focus on reliability when the budget is exhausted
Rely exclusively on virtual machine CPU and memory utilization thresholds as the primary SLIs to trigger automated deployment rollbacks
Bypass continuous integration automated testing suites and conduct manual exploratory testing directly in production whenever error budgets are low
Target a 100% availability SLO for every production microservice and mandate Change Advisory Board (CAB) manual approval for each automated pipeline execution
Define user-centric Service Level Indicators (SLIs) to determine an error budget, automate releases while the budget is positive, and pause non-essential deployments to focus on reliability when the budget is exhausted
Site Reliability Engineering (SRE) uses Service Level Indicators (SLIs) and Service Level Objectives (SLOs) to quantify user happiness and establish an error budget. An error budget represents the acceptable amount of unreliability a service can experience over a given period while still meeting user expectations.
This approach directly aligns with core SRE and DevOps tenets by balancing product feature velocity with system stability:
Using SLIs to derive error budgets bridges the gap between fast continuous delivery and dependable service reliability. It ensures that development teams are empowered to innovate rapidly until reliability data objectively indicates that stabilization is necessary.
StudyCerts
StudyCerts