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 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?
This approach disables automated continuous integration (CI) and test automation suites, replacing them with ad-hoc manual testing in live production environments when service error budgets are depleted.
The organization had no automated environments and was executing a live incident recovery protocol under extreme, temporary disaster recovery constraints.
This strategy attempts to achieve zero downtime by defining a 100% availability target and instituting a heavyweight Change Advisory Board (CAB) manual review process before any pipeline can deploy code to production.
The organization were managing an isolated, safety-critical hardware system where zero failures can be tolerated and automated deployments are strictly prohibited by regulation.
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.
This strategy relies strictly on low-level infrastructure metrics, such as virtual machine (VM) CPU and RAM utilization, as the core indicators of service health and criteria for automated rollbacks.
The assessment specifically focused on configuring automated horizontal pod or instance autoscaling rather than evaluating user-facing service health and release quality.
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