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 recently migrated its applications to Google Cloud. During a high-traffic event, customers experience slow checkout times, and the IT operations team takes hours to diagnose the issue because their telemetry data is siloed. The company wants to modernize its operations to meet the following goals:
Which solution should the company implement to meet these requirements?
Google Cloud Observability (formerly Google Cloud's operations suite) is an integrated suite of managed services designed to collect, correlate, and analyze telemetry data across cloud and hybrid environments. It combines core tools such as Cloud Monitoring, Cloud Logging, Cloud Trace, and Cloud Profiler into a unified operational interface.
Cloud Logging, and inspect request latency bottlenecks using Cloud Trace in one place.Cloud Trace and Cloud Profiler to track how requests propagate through distributed microservices and identify resource-intensive code.Unlike post-incident administrative processes or pre-deployment testing tools, Google Cloud Observability directly resolves the problem of siloed telemetry during live production incidents. By correlating metrics, logs, and traces in real time, it eliminates diagnostic blind spots and dramatically shortens investigation and recovery times.
Performance and load testing involves simulating realistic or extreme user traffic patterns against applications and infrastructure using services like Cloud Load Balancing and load generation tools. Stress testing intentionally pushes systems to their operational limits to uncover capacity constraints and architectural weaknesses before they impact real users.
Simulating traffic is a proactive validation technique rather than a centralized observability solution. Running load tests does not unify siloed logs, metrics, and traces into a single management plane, nor does it give operations teams the diagnostic visibility required to troubleshoot unexpected production incidents and reduce mean time to resolution (MTTR) when a live failure occurs.
This option would be correct if the company wanted to proactively validate system resilience, perform capacity planning ahead of a scheduled sales event, or verify that new code deployments can withstand peak traffic loads without degrading.
Even when organizations perform regular load and stress testing, unexpected production incidents still occur due to third-party dependencies, network anomalies, or unforeseen user behavior. Therefore, testing must always be paired with Google Cloud Observability to monitor live health and diagnose active issues quickly.
A post-incident review (PIR), commonly referred to as a postmortem, is a structured, retrospective process conducted after an incident has been resolved. A multidisciplinary team gathers data to reconstruct a timeline of events, determine the underlying root cause, and define corrective actions within a blameless culture.
While a post-incident review is a vital Site Reliability Engineering (SRE) practice for long-term reliability, it is an administrative and analytical process that takes place after an outage is over. It does not provide the live technical tooling needed to ingest metrics, aggregate logs, or trace application requests during an active incident, nor does it directly solve the problem of siloed telemetry data when engineers are trying to diagnose an ongoing slowdown.
This option would be the right choice if the scenario asked how the organization should foster a culture of continuous improvement, analyze systemic weaknesses after an outage has been resolved, and prevent similar incidents from recurring in the future.
In modern cloud operations, Google Cloud Observability and post-incident reviews complement one another. Integrated observability tools provide the raw metrics, logs, and traces needed to lower MTTR during the incident, and that same centralized data is later reviewed during the PIR to document an accurate timeline.
A knowledge base is a shared repository of documentation, runbooks, playbooks, known issues, and standard operating procedures. Using collaboration platforms like Google Workspace, operations teams can create, version-control, and share troubleshooting guides and escalation protocols across the organization.
A document repository in Google Workspace only stores static human-written knowledge and procedural guides. It cannot ingest real-time infrastructure metrics, aggregate application logs, or trace distributed requests. Because the company's delay in diagnosing issues stems from siloed telemetry data across their technology stack, a documentation portal will not provide full-stack observability.
This option would be the ideal solution if the company's primary challenge was a lack of standardized incident response procedures, confusion over team responsibilities during outages, or engineers repeatedly solving the same common problems from scratch without shared documentation.
While a knowledge base and well-maintained runbooks help streamline team coordination during an incident, responders still need Google Cloud Observability to see what is actually happening inside the environment. In practice, alerts generated by Cloud Monitoring often include links to relevant runbooks so engineers have both live telemetry and procedural guidance.
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