Question #565
A company hosts a custom application on on-premises Linux servers that interact with AWS services via Amazon API Gateway. The API's development stage has AWS X-Ray tracing enabled. What should a developer do to enable X-Ray tracing on the on-premises servers with the LEAST configuration?
Integrate the X-Ray SDK into the application code on the on-premises servers to capture and send trace data directly to the X-Ray service.
Install and run the X-Ray daemon on the on-premises servers to collect and forward trace data to the X-Ray service.
Configure an Amazon Kinesis Data Firehose stream to ingest application logs from the on-premises servers and deliver them to X-Ray for processing.
Set up an Amazon CloudWatch agent on the on-premises servers to forward metrics and logs to CloudWatch, then use CloudWatch Insights to relay the data to X-Ray.
Explanation
Answer B is correct because the X-Ray daemon acts as a proxy to collect trace data from on-premises applications and forwards it to the AWS X-Ray service. This requires only installing and running the daemon, minimizing configuration effort.
Option A requires modifying application code to integrate the X-Ray SDK, which adds complexity. Option C is incorrect because X-Ray does not ingest data via Kinesis Data Firehose. Option D is invalid since CloudWatch cannot relay data to X-Ray directly. The key takeaway is that the X-Ray daemon simplifies tracing for non-AWS environments by handling data transmission without code changes.
Answer
The correct answer is: B