A developer is building various microservices for an application that will run on Amazon EC2 instances. The developer needs to monitor the end-to-end view of the requests between the microservices and

Question

Options

• AUse Amazon CloudWatch to aggregate the microservices' logs and metrics, and build the
• BUse AWS CloudTrail to aggregate the microservices' logs and metrics, and build the monitoring
• CUse the AWS X-Ray SDK to add instrumentation in all the microservices, and monitor using the
• DUse AWS Health to monitor the health of all the microservices.

• A
  5% (2)
• B
  8% (3)
• C
  85% (33)
• D
  3% (1)

Explanation

AWS X-Ray is purpose-built for distributed tracing across microservices - by instrumenting each service with the X-Ray SDK, developers get an end-to-end service map showing request flow, latency, errors, and bottlenecks across all components, which is exactly what "end-to-end view" and "debug issues" require.

Why the distractors are wrong:

• A (CloudWatch): CloudWatch aggregates logs and metrics well, but it lacks distributed tracing - it cannot stitch together a request's journey across multiple microservices into a single trace.
• B (CloudTrail): CloudTrail records API calls made to AWS services for auditing and governance purposes - it is not designed for application-level monitoring or inter-service request tracing.
• D (AWS Health): AWS Health reports on the status and health of AWS infrastructure and service events (e.g., outages, maintenance) - it has no visibility into your application's microservice behavior.

Memory tip: Think of X-Ray as an "X-ray machine" for your requests - it sees through all your microservices to show the full skeleton of a transaction from start to finish. Whenever an exam question mentions distributed tracing, end-to-end request visibility, or debugging across microservices, X-Ray is the answer.

No community discussion yet for this question.