A developer created an AWS Lambda function that calls multiple AWS services and observed that the function's execution time is higher than expected. The developer must investigate interactions between the services without modifying the function's code. Which approach meets this requirement?

Enabling AWS X-Ray active tracing for the Lambda function allows you to visualize the function's execution, including calls to other AWS services. X-Ray provides a service map and detailed trace timelines, making it easy to identify bottlenecks and understand the latency contributed by each service interaction. This meets the requirement of investigating interactions without modifying code. AWS CloudTrail records API calls made to AWS services, but it doesn't provide detailed timing or performance metrics for individual service interactions within a Lambda function's execution. AWS Config records configuration changes to resources, not performance or interaction details. Inspecting CloudWatch logs for the Lambda function would show function logs and basic metrics, but not the detailed breakdown of inter-service calls and their latencies that X-Ray offers.