nerdexam
Google

PROFESSIONAL-CLOUD-DEVELOPER · Question #279

Your ecommerce application receives external requests and forwards them to third-party API services for credit card processing, shipping, and inventory management as shown in the diagram. Your custome

The correct answer is A. Install the OpenTelemetry library for your respective language, and instrument your application.. The problem is intermittent slowness caused by calls to multiple third-party APIs, with no existing metrics or traces to diagnose where the latency originates. OpenTelemetry (Option A) is the industry-standard, vendor-neutral observability framework that provides distributed trac

Monitoring, Logging, and Troubleshooting Solutions

Question

Your ecommerce application receives external requests and forwards them to third-party API services for credit card processing, shipping, and inventory management as shown in the diagram. Your customers are reporting that your application is running slowly at unpredictable times. The application doesn't report any metrics. You need to determine the cause of the inconsistent performance. What should you do?

Exhibit

PROFESSIONAL-CLOUD-DEVELOPER question #279 exhibit

Options

  • AInstall the OpenTelemetry library for your respective language, and instrument your application.
  • BInstall the Ops Agent inside your container and configure it to gather application metrics.
  • CModify your application to read and forward the X-Cloud-Trace-Context header when it calls the
  • DEnable Managed Service for Prometheus on the Google Kubernetes Engine cluster to gather

How the community answered

(38 responses)
  • A
    76% (29)
  • B
    8% (3)
  • C
    13% (5)
  • D
    3% (1)

Explanation

The problem is intermittent slowness caused by calls to multiple third-party APIs, with no existing metrics or traces to diagnose where the latency originates. OpenTelemetry (Option A) is the industry-standard, vendor-neutral observability framework that provides distributed tracing, metrics, and logging. By instrumenting the application with OpenTelemetry, every outbound call to the credit card, shipping, and inventory APIs is traced with timing data, immediately revealing which downstream dependency is the bottleneck. Option B (Ops Agent) collects infrastructure-level metrics (CPU, memory) from the container host, not application-level call latency. Option C (forwarding X-Cloud-Trace-Context) enables trace context propagation but only if the third-party APIs support it - it also doesn't add instrumentation to the application itself. Option D (Managed Service for Prometheus) collects Kubernetes cluster metrics, not application-level request tracing.

Topics

#Application Monitoring#Observability#OpenTelemetry#Performance Troubleshooting

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVELOPER Practice