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.
A retail company exposes its microservices-based e-commerce APIs to external partners through Apigee. Recently, partners reported intermittent high latency and elevated HTTP 5xx error rates during peak shopping hours.
To establish comprehensive observability across the API management layer and backend services, the engineering team must meet the following requirements:
Which observability strategy should the team implement?
Apigee API Monitoring provides minute-by-minute aggregated operational metrics for API proxies, including error counts, fault codes, and latency distributions. Cloud Monitoring collects numeric time-series data—such as CPU utilization, memory saturation, and request rates—to power operational dashboards and alert policies.
The team only needed real-time operational alerting and high-level triage between the API proxy and the backend boundary, without requiring exact per-app latency quantiles or internal microservice span tracing.
Effective API observability separates real-time monitoring (alerts and fault codes) from analytics (exact quantiles and business dimensions) and distributed tracing (internal call-chain spans).
A complete observability architecture combines API gateway telemetry with application-level telemetry across metrics, logs, and distributed traces. In Google Cloud, Apigee API Monitoring and Cloud Monitoring deliver real-time operational visibility, Apigee API Analytics provides deep historical business and performance reporting, and OpenTelemetry feeds Cloud Trace and Cloud Logging to expose internal microservice execution paths.
No single tool covers every layer of an API-driven distributed system. Pairing Apigee's specialized operational and analytical tools with Google Cloud Observability ensures real-time incident response, accurate historical reporting, and granular microservice debugging.
Cloud Logging collects, stores, and queries time-stamped records of discrete events across Google Cloud services and applications, including Cloud Audit Logs for administrative and data access tracking. Error Reporting scans log entries for formatted exceptions, annotates them, and groups recurring failures into error groups for developer triage.
The primary goal were security auditing, compliance forensics, or aggregating unhandled application exceptions across backend workloads rather than holistic API performance analytics and distributed latency profiling.
Logs are one of the three pillars of observability alongside metrics and traces. Cloud Logging works best when correlated with Cloud Trace IDs and paired with Cloud Monitoring alerts rather than replacing them.
Apigee API Analytics is a historical reporting and business intelligence engine that captures detailed API call metadata from Apigee proxies and stores it in BigQuery. It offers roughly 50 selectable dimensions—including Developer App, Proxy, Request Path, and geography—and supports custom reports and asynchronous report jobs to evaluate long-term API traffic patterns.
The team only needed historical business and performance reporting—such as identifying top consuming partners, analyzing regional traffic growth, or generating monthly latency quantile reports—without requiring real-time alerting or internal microservice debugging.
A common misconception is treating Apigee API Analytics as an all-in-one monitoring platform. In practice, teams rely on Apigee API Monitoring with Cloud Monitoring for real-time alerts and Cloud Trace for internal microservice span visibility.
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