Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise engineering team runs a critical web application hosted on Google Cloud and is implementing Site Reliability Engineering (SRE) practices to balance feature delivery velocity with system reliability. The team currently experiences frequent production regressions due to rapid deployments, while internal dashboards primarily track infrastructure health metrics like CPU and memory utilization.
You need to establish Service Level Indicators (SLIs) and Service Level Objectives (SLOs) that reflect actual user experience and implement an automated error budget policy that halts standard feature rollouts in your deployment pipeline when the error budget is exhausted.
Which strategy should you implement?
This option describes software supply chain security and compliance governance mechanisms, including tracking administrative audit trails in Cloud Logging, configuring vulnerability remediation timelines in Security Command Center, and enforcing SLSA Level 4 multi-party code reviews.
The primary objective were achieving SLSA Level 4 supply chain compliance and enforcing mandatory security patch timelines under regulatory requirements.
Apigee SpikeArrest and Quota policies are API management mechanisms designed to protect backend services from traffic bursts, Distributed Denial of Service (DDoS) spikes, and client contract overages by rejecting excess traffic with HTTP 429 status codes.
You needed to protect downstream microservices from API client abusive call patterns or enforce multi-tenant API monetization tiers.
This option relies on infrastructure-centric utilization metrics (CPU load, RAM consumption) as proxy indicators for service health and sets an absolute, zero-failure target (100% availability) for the service.
The goal were basic horizontal autoscaling thresholds or hardware capacity monitoring rather than defining user-aligned reliability objectives and error budget governance.
Service Level Indicators (SLIs) are quantifiable operational metrics that reflect the real-time quality of service provided to end users, such as request success rate and latency. Service Level Objectives (SLOs) define precise target reliability goals (e.g., 99.9% successful requests over a 30-day rolling window) agreed upon by engineering and business stakeholders. The difference between 100% availability and the SLO target is the error budget, which represents the tolerable threshold of unreliability. An error budget policy formally dictates governance actions—such as freezing new feature rollouts and prioritizing reliability engineering—whenever the budget is depleted or burning at an unsustainable rate.
This approach aligns directly with Google Cloud Well-Architected reliability principles and SRE best practices by shifting observability to the customer perspective and programmatically coupling error budget burn to delivery automation.
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