Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An e-commerce company operates a multi-tier microservices application hosted on Google Cloud. When customers submit checkout orders, the request travels across an API gateway, an inventory verification service, an external payment processor, and a backend database. Customers report severe, intermittent delays during checkout, but CPU and memory utilization across all compute instances remain below 20%.
Which diagnostic tool and feature should you use to evaluate individual request spans and pinpoint the exact source of latency across these distributed services?
Cloud Logging is a fully managed service that allows organizations to store, search, analyze, and monitor log data and events generated by Google Cloud infrastructure, system services, and custom applications. The Logs Explorer provides a rich query interface to filter logs by timestamp, severity level, resource type, and payload fields.
This option would be the ideal choice if developers were investigating specific runtime exceptions, application crash dumps, error stack traces, or auditing security events and HTTP response codes.
Although Cloud Logging is not the primary tool for distributed latency visualization, it tightly integrates with Cloud Trace. Traces and logs can share trace identifiers, allowing operators who spot an anomalous span in Cloud Trace to jump directly into correlated logs for deeper root-cause debugging.
Cloud Monitoring provides visibility into the performance, uptime, and overall health of cloud applications and cloud infrastructure. It aggregates numerical metrics, creates custom charts and dashboards, and triggers alerting policies when metrics (such as request count, error rate, or 99th percentile latency) cross defined thresholds.
This option would be the right choice if the objective were to establish real-time alerting notifications when overall checkout latency exceeds an SLA threshold, or to plot macro-level latency trends on an operational dashboard over days or weeks.
Cloud Monitoring and Cloud Trace work in tandem. Typically, Cloud Monitoring acts as the first line of defense by alerting engineers to elevated 95th or 99th percentile latency, after which engineers navigate to Cloud Trace to diagnose the specific distributed bottleneck causing that latency.
Cloud Trace is a distributed tracing system designed specifically for Google Cloud and hybrid environments. Its primary purpose is to collect latency information from instrumented applications and Google Cloud services, allowing developers and administrators to track how user requests propagate through complex, multi-service architectures. A single end-to-end transaction is represented as a trace, which is subdivided into individual units of execution known as spans.

traceparent) to stitch together parent and child spans across microservice boundaries.Cloud Trace is the only Google Cloud observability tool built from the ground up for distributed tracing and span-level timing analysis. While monitoring tools can signal that an overall service is slow and logging tools can display discrete event records, only Cloud Trace maps out the exact sequence and timing of interdependent calls across distributed microservices.
Cloud Profiler is a continuous statistical profiling tool designed to analyze CPU utilization and memory allocations inside running application code. It operates by periodically sampling call stacks across production workloads, aggregating this execution data into interactive flame graphs to show which specific functions or lines of code consume the most system resources.
This option would be the right choice if the application instances were suffering from sustained 100% CPU utilization or excessive garbage collection overhead, and developers needed to identify computationally expensive methods or memory leaks within a specific codebase.
While Cloud Profiler and Cloud Trace are both diagnostic tools in Google Cloud, they serve complementary purposes. Cloud Trace answers where time is spent across services (distributed latency), whereas Cloud Profiler answers which functions consume compute resources inside an instance (code efficiency).
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