Cloud Native Observability GCSA Practice Questions (Page 9)

Questions 41–45

1. 41application · medium

   A team is designing a new microservice and wants to ensure that its logs are useful for debugging and correlation. They plan to use a log aggregation platform. Which logging practice is most aligned with cloud native observability best practices?

   • AWrite logs in a custom text format that is optimized for human reading.
   • BLog only error messages and ignore informational logs to reduce noise.
   • CEmit structured logs in JSON format with fields for request ID, service name, and severity level.
   • DUse a single global log level for all services to simplify configuration.
   Reveal Solution Discussion Select an answer first
2. 42expert · hard

   An SRE team is troubleshooting a performance degradation in a microservices application. Metrics show increased latency in the order service, but logs from the order service do not show any errors. The team suspects the database is the bottleneck. They have traces available, but they are not sure how to use them to confirm the database is the cause. Which approach is most effective?

   • AIncrease the log level of the order service to debug and wait for new logs to appear.
   • BCheck the database's slow query log and compare timestamps with the latency spike.
   • CLook at the order service's CPU usage metrics and correlate them with the latency spike.
   • DFilter traces for the order service and examine the spans for database calls to identify which queries have high duration.
   Reveal Solution Discussion Select an answer first
4. 43foundation · easy

   How does correlating metrics, logs, and traces help in diagnosing a performance issue?

   • AIt eliminates the need for manual investigation.
   • BIt provides a complete picture by linking the symptom (metric), the event details (log), and the request path (trace).
   • CIt automatically rolls back the last deployment.
   • DIt reduces the amount of telemetry data collected.
   Reveal Solution Discussion Select an answer first
5. 44foundation · easy

   What is the primary distinction between cloud native observability and traditional monitoring in cloud environments?

   • AObservability emphasizes the ability to ask arbitrary questions about system behavior using telemetry, while monitoring focuses on predefined metrics and alerts.
   • BMonitoring uses traces and logs, while observability uses only metrics.
   • CObservability is only applicable to containerized workloads, while monitoring applies to all cloud resources.
   • DObservability is based on predefined metrics and alerts, while monitoring explores unknown system behaviors.
   Reveal Solution Discussion Select an answer first
6. 45application · medium

   A site reliability engineer (SRE) is investigating a sudden increase in checkout failures. The metrics show a spike in 5xx responses from the checkout service, and the logs show 'connection refused' errors when connecting to the inventory service. The SRE wants to confirm whether the inventory service is the root cause and whether a specific deployment caused the issue. Which sequence of actions best achieves this?

   • AIncrease the log level of the checkout service to debug and wait for new errors to appear.
   • BCheck the inventory service's metrics for error rate and latency, then examine its logs for the same time window, and finally review the deployment history for both services.
   • CRestart the checkout service and monitor whether the error rate returns to normal.
   • DOpen the inventory service's dashboard and look at its CPU usage over the last hour.
   Reveal Solution Discussion Select an answer first