An e-commerce company runs a microservices-based application across multiple services in Google Cloud. Following a recent feature release, operations engineers notice three distinct issues affecting production: Customers experience intermittent latency spikes during checkout transactions traversing multiple downstream services. Certain backend worker instances exhibit abnormally high CPU and memory consumption. Unhandled application crashes and runtime exceptions are being written to logs without being aggregated. Which combination of Google Cloud Application Performance Management (APM) and observability tools should you implement to address each issue?

Use Cloud Trace to analyze inter-service request latency, Cloud Profiler to inspect CPU and memory usage at the code level, and Error Reporting to aggregate and alert on application crashes.: ### What this solution is This solution combines **Cloud Trace**, **Cloud Profiler**, and **Error Reporting**, which together form the core Application Performance Management (APM) suite in Google Cloud. Each tool is purpose-built to target a specific dimension of distributed system performance and application reliability. ### How it meets the requirements - **Diagnosing Intermittent Latency Spikes**: **Cloud Trace** collects latency data and distributed span details from applications. By visualizing requests in a Gantt chart across microservices, engineers can pinpoint the exact downstream RPC or service introducing latency bottlenecks. - **Optimizing Resource Consumption**: **Cloud Profiler** provides continuous, low-overhead statistical profiling of CPU and memory allocations directly within application code, identifying inefficient functions and hot execution paths. - **Aggregating Application Failures**: **Error Reporting** automatically parses stack traces and runtime exceptions from application logs, grouping crashes into deduplicated, manageable issues with associated root-cause details. ### Key advantages and capabilities - **Distributed Context**: Trace spans correlate end-to-end request journeys across heterogeneous microservice architectures. - **Low Overhead Profiling**: Profiler operates continuously in production environments with typically less than 1% CPU and memory overhead. - **Automated Root-Cause Insights**: Error Reporting deduplicates repeated exceptions and links errors directly to source code revisions. ### Why this is optimal This approach directly aligns each operational symptom with its optimal diagnostic tool, enabling granular distributed latency tracing, code-level resource tuning, and centralized exception triage without requiring custom analytical infrastructure.

StudyCerts

Apm Tools Trace Profiler Error Reporting | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Apm Tools Trace Profiler Error Reporting

Section: Observability

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An e-commerce company runs a microservices-based application across multiple services in Google Cloud. Following a recent feature release, operations engineers notice three distinct issues affecting production:

Customers experience intermittent latency spikes during checkout transactions traversing multiple downstream services.
Certain backend worker instances exhibit abnormally high CPU and memory consumption.
Unhandled application crashes and runtime exceptions are being written to logs without being aggregated.

Which combination of Google Cloud Application Performance Management (APM) and observability tools should you implement to address each issue?

Use Cloud Service Mesh access logs to measure database query latency, Cloud Audit Logs to track memory leaks, and Eventarc to trigger notifications on application crashes.

Use Cloud Profiler to map end-to-end distributed service latency, Cloud Trace to pinpoint in-memory code allocations, and Log Analytics to group unhandled exceptions.

Use Cloud Trace to analyze inter-service request latency, Cloud Profiler to inspect CPU and memory usage at the code level, and Error Reporting to aggregate and alert on application crashes.

Use Cloud Logging queries to calculate distributed request duration, Cloud Monitoring dashboards to analyze process-level memory allocations, and Cloud Trace to aggregate application stack traces.

Professional Cloud Architect

Apm Tools Trace Profiler Error Reporting

Related questions