DVA-C02: How to Enable AWS X-Ray Tracing on On-Premises Linux Servers

The correct answer is B. Install and run the X-Ray daemon on the on-premises servers to capture and relay the data to the X-Ray service.

To enable X-Ray tracing on the on-premises servers, the developer needs to install and run the X-Ray daemon on each server that runs the custom application. The X-Ray daemon is a software agent that listens for traffic on UDP port 2000, gathers raw segment data, and relays it to the X-Ray service. The X-Ray daemon also adds information about the EC2 instance to each segment, such as the instance ID and availability zone.

The other options are incorrect for the following reasons:

• Option A is incorrect because the X-Ray SDK is not enough to enable X-Ray tracing on the on-premises servers. The X-Ray SDK is a set of libraries for different languages that enable instrumentation of the application code to generate and send segment documents to the X-Ray daemon. The X-Ray SDK does not relay the data to the X-Ray service by itself; it needs the X-Ray daemon to do so.
• Option C is incorrect because it involves unnecessary complexity and latency. Capturing incoming requests on-premises and configuring an AWS Lambda function to pull, process, and relay relevant data to X-Ray using the PutTraceSegments API call would require additional steps and resources, such as setting up an API endpoint, triggering a Lambda function, parsing and filtering the request data, and making an API call to X-Ray. This would also introduce additional overhead and delay in sending the data to X-Ray.
• Option D is incorrect because it uses the wrong API call. The PutTelemetryRecords API call is used to send aggregated statistics about segments that were processed by the X-Ray daemon, such as error rates and response times. It is not used to send segment documents that contain information about individual requests.