Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An e-commerce company runs a distributed application on Google Cloud composed of several independent microservices:
During a promotional event, customers report slow checkout times. The operations team needs to follow the end-to-end journey of a single checkout transaction across all of these microservices to determine which specific component is causing the latency bottleneck.
Which core observability component should the team analyze to investigate this issue?
Logs (managed in Google Cloud through Cloud Logging) are chronological, time-stamped records of discrete events that occur within an application, operating system, or infrastructure component. Each log entry captures detailed context about a specific event, such as an application error, a configuration change, a security audit trail, or a state transition.
The scenario asked how to inspect the detailed error message of a failed payment transaction, review Cloud Storage access logs, or analyze audit trails to determine which administrator modified a system configuration.
In a complete observability strategy, logs and traces complement each other. Engineers typically use traces first to isolate which microservice is experiencing a bottleneck or failure, and then examine the logs generated by that specific component to read the detailed error payload.
Metrics (collected and analyzed in Cloud Monitoring) are numerical measurements of system health, resource utilization, or application activity gathered at regular time intervals. Common examples include CPU utilization, memory consumption, network I/O, request rate, error rate, and business indicators such as orders placed.
The scenario asked how to track CPU consumption over time to right-size virtual machines, monitor quantitative service-level indicators (SLIs) on a dashboard, or analyze long-term traffic trends for capacity planning.
Metrics act as the first line of visibility in observability. An unexpected change in metric data—such as a sudden jump in average checkout latency—signals that a problem exists, prompting engineers to use traces to find where the slowdown is occurring.
Alerting policies are automated monitoring rules within Google Cloud Observability that evaluate metric thresholds, log events, or statistical anomalies against predefined conditions. When a specified condition is breached, the policy automatically triggers notifications through configured notification channels such as email, SMS, or incident management systems.
The scenario asked how the operations team could automatically send an SMS notification or open an incident ticket whenever the application's checkout error rate exceeds 5% for more than five minutes.
In the cloud operations workflow, alerting policies initiate the incident response process by waking up or notifying the team, whereas traces and logs are the diagnostic tools used afterward to investigate and resolve the underlying issue.
Traces (managed in Google Cloud through Cloud Trace) are a core pillar of observability that represent the complete end-to-end journey of a single user request or transaction as it travels through the components of a distributed application. Each trace is composed of individual spans, where each span records the execution details and duration of a single function, microservice call, or operation.
While metrics indicate that overall checkout latency has increased and logs record isolated events within a single service, neither automatically reconstructs the cross-service path of a multi-step request. Traces are specifically designed for distributed systems, making them the optimal telemetry component for diagnosing inter-service latency bottlenecks.
Change the inputs and watch how the outcome changes.

Pick the team's goal and the component they analyze to see what each pillar actually reveals about the checkout application.
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