Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team manages an internet-facing e-commerce API on Google Cloud backed by a Firestore database. Following a recent outage that went unnoticed until customers complained, you need to implement a proactive Cloud Monitoring strategy with the following requirements:
Which Cloud Monitoring configuration should you implement?
This option attempts to edit Google Cloud-managed service dashboards directly, replace time-series latency aggregation with log-based alerting policies, and infer external endpoint availability from VM CPU utilization metrics.
p99 over time-series data. Triggering immediately on any single slow request creates excessive noise and violates the 5-minute rolling window requirement.You wanted to be notified whenever a specific critical error string appeared in application logs, while viewing default single-service metrics without needing a consolidated multi-service dashboard or external endpoint probing.
This strategy combines synthetic monitoring, metric-based threshold alerting, and custom dashboards within Cloud Monitoring to provide proactive failure detection and centralized operational visibility. Together, these tools ensure that external outages and sustained performance degradations trigger timely notifications while giving engineers a unified troubleshooting workspace.
p99) of request latency over a 5-minute rolling window. Triggering only when the threshold of 250 ms is breached for the full duration prevents alert fatigue from brief, self-healing traffic spikes.4xx and 5xx responses against total api/request_count alongside alert and incident widgets.Unlike predefined service dashboards or manual checks, this integrated configuration automates failure detection across both external availability and internal latency while consolidating every key operational signal into one actionable dashboard.
This option creates an HTTPS uptime check without an alerting policy, places Indicator widgets on a custom dashboard, and relies on Metrics Explorer for ad-hoc error rate calculations.
Your team only needed an interactive workspace for occasional manual investigation and a passive wallboard display without automated Slack notifications or sustained rolling-window latency alerts.
This option relies on BigQuery for metric storage, recommended alerting policies with notification channels disabled, and Cloud Monitoring's broken-link checker synthetic monitor.
404 HTML links). It does not compute p99 API request latency over a rolling time window or act as a substitute for metric-based latency alerts.Your goal was to archive historical Cloud Monitoring metrics in BigQuery for long-term capacity forecasting, crawl a public website for broken HTML links, and track non-urgent policy violations silently inside the console.
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