Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team manages a multi-database application platform on Google Cloud with a contractual Service Level Agreement (SLA) guaranteeing 99.9% availability over a calendar month. You need to implement proactive reliability monitoring in Cloud Monitoring that meets the following requirements:
Which SLO and alerting strategy should you implement?
Cloud Monitoring custom dashboards and service Error Budget Remaining charts provide visual observability into current SLO compliance, historical Service Level Indicator (SLI) trends, and the remaining percentage of an error budget.
The requirement was strictly to consolidate visual health, compliance, and error-budget reporting across multiple database services into a single operational overview without automated paging.
To proactively manage error budgets, teams should pair Cloud Monitoring dashboards with burn-rate alerting policies attached to notification channels, using the dashboard charts to diagnose issues after an alert fires.
This approach attempts to enforce zero tolerance for errors (100% SLO) while evaluating the error-budget burn rate over a 30-day lookback period at a 1x threshold.
100% - SLO goal. A 100% SLO results in an error budget of zero, meaning even a single failed database query or transient network blip immediately violates the objective and renders burn-rate calculations meaningless.This option would not be valid in Cloud Monitoring because a 100% SLO leaves no error budget and burn-rate alerting policies do not support lookback periods exceeding 24 hours.
Rather than aiming for an unattainable 100% target, teams should calibrate the SLO based on user expectations and error-budget tolerance, then pair shorter lookback periods (1–2 hours and 24 hours) with higher burn-rate multipliers (10x and 2x).
Service Level Objective (SLO) burn-rate alerting in Cloud Monitoring measures how rapidly a service consumes its error budget—calculated as 100% - SLO goal—relative to the compliance period. By pairing a stricter internal SLO with two complementary burn-rate alerting policies (fast-burn and slow-burn) connected to notification channels, engineering teams receive timely, actionable alerts before a contractual Service Level Agreement (SLA) is violated.
Relying on a single burn-rate policy leaves blind spots for either rapid outages or slow leaks, and matching the SLO to the SLA eliminates any operational buffer. Combining a stricter 99.95% SLO with dual fast-burn and slow-burn alerting policies delivers comprehensive, low-noise protection against SLA breaches.
This option sets the internal Service Level Objective (SLO) to match the exact 99.9% target of the customer-facing Service Level Agreement (SLA) and relies exclusively on a single fast-burn alerting policy.
This configuration would only be partially suitable if the organization solely wanted emergency paging for sudden major outages and had already accounted for SLA safety margins elsewhere—though even then, it would fail to catch slow-burn budget depletion.
Best practices dictate defining an internal SLO tighter than external commitments (such as 99.95% for a 99.9% SLA) and pairing a fast-burn policy with a 24-hour slow-burn policy for full protection.
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