Which combination of steps should the developer take to meet this requirement?
(Choose two.)
Download the AWS X-Ray daemon. Install the daemon on an EC2 instance. Ensure that the EC2 instance allows UDP traffic on port 2000.
Configure an interface VPC endpoint to allow traffic to reach the global AWS X-Ray daemon on TCP port 2000.
Enable AWS X-Ray. Configure Amazon CloudWatch to push logs to X-Ray.
Add the AWS X-Ray software development kit (SDK) to the microservices. Use X-Ray to trace requests that each microservice makes.
Set up Amazon CloudWatch metric streams to collect streaming data from the microservices.
Explanations:
Installing the AWS X-Ray daemon on EC2 allows it to capture trace data from the microservices and send it to the X-Ray service, which is essential for analyzing message flow. The UDP port 2000 is required for communication between the daemon and X-Ray.
There is no global AWS X-Ray daemon to access via VPC endpoint. X-Ray requires the X-Ray daemon to be installed on each instance or as part of the ECS service, so this configuration would not help.
CloudWatch and X-Ray are separate services, and pushing CloudWatch logs to X-Ray is not possible. X-Ray is specifically used for tracing requests, while CloudWatch is for logging.
Adding the AWS X-Ray SDK to the microservices enables the generation of trace data for requests, allowing the developer to track transactions across microservices. This integration is essential for distributed tracing in X-Ray.
CloudWatch metric streams are used for monitoring metrics, not for capturing or analyzing individual transaction traces. They do not assist in matching log output to specific transactions.
I conclude that the answer is:
Download the AWS X-Ray daemon. Install the daemon on an EC2 instance. Ensure that the EC2 instance allows UDP traffic on port 2000.
As far as I’m aware, the answer is:
Download the AWS X-Ray daemon. Install the daemon on an EC2 instance. Ensure that the EC2 instance allows UDP traffic on port 2000.