You have a distributed microservices application running on EC2, and message volumes make it hard to correlate logs across services for a given transaction. You need to trace requests through the services to analyze message flow. Which combination of steps should you take? (Choose two.)

To trace requests across microservices with AWS X-Ray, you need two main components. First, the AWS X-Ray SDK must be integrated into each microservice. This SDK instruments your code, captures metadata about requests, and sends trace data to the X-Ray daemon. Second, the AWS X-Ray daemon needs to be running on an EC2 instance to collect this raw segment data from the SDKs and relay it to the X-Ray service. The daemon listens for UDP traffic on port 2000. Incorrect options: Configuring an interface VPC endpoint for X-Ray is not for a "global AWS X-Ray daemon" and X-Ray communication typically uses HTTPS, not TCP port 2000 for the service endpoint. The daemon uses UDP port 2000. AWS X-Ray and CloudWatch are distinct services; CloudWatch logs are not pushed into X-Ray for tracing purposes. X-Ray generates its own trace data. Amazon CloudWatch metric streams are for collecting metrics, not for distributed tracing of requests.