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 payment platform on Google Cloud using Cloud SQL and Cloud Spanner. Your organization has a contractual SLA guaranteeing 99.9% monthly availability aligned with each customer billing cycle. Recently, teams struggled to trace why brief performance degradations depleted error budgets and could not produce clean end-of-month compliance reports.
You need to configure Cloud Monitoring to:
Which approach should you implement?
This solution combines Service Level Objectives (SLOs) configured with calendar-based compliance periods, Cloud Monitoring custom dashboards featuring SLO widgets, and Cloud Logging (Logs Explorer) for deep-dive troubleshooting. Together, these capabilities establish an end-to-end observability workflow across heterogeneous database services such as Cloud SQL and Cloud Spanner.
Unlike rolling windows or alert-only setups, this architecture addresses both operational troubleshooting and formal SLA validation. It pairs proactive internal guardrails with deterministic monthly scoring and rich diagnostic context across multiple database technologies.
This approach uses rolling 30-day compliance periods configured at the exact 99.9% contractual SLA threshold, while relying on the Alerts timeline within individual per-service dashboards to verify monthly compliance.
The goal were strictly continuous operational health monitoring over a sliding 30-day horizon for an individual service without external monthly billing-cycle SLA reporting or multi-service consolidation.
This setup defines a 7-day rolling windows-based SLO at the 99.9% SLA threshold and relies exclusively on burn-rate alerting policies to monitor performance over time.
You only needed short-term, real-time notifications when weekly latency percentiles degraded rapidly, rather than monthly contractual SLA validation and cross-database historical analysis.
This configuration attempts to enforce perfection by setting a 100% availability SLO on a calendar-month basis while exporting raw Prometheus metrics instead of building Cloud Monitoring SLO dashboards.
100% - SLO%) exist specifically to balance feature velocity and maintenance against reliability risk.You only needed to collect raw custom database telemetry via Prometheus for external archival, rather than managing error budgets, performing dashboard-driven root cause analysis, and validating realistic monthly SLAs.
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