Answer – C
The AWS Documentation mentions the following.
Lambda@Edge is an extension of AWS Lambda, a compute service that lets you execute functions that customize the content that CloudFront delivers. You can author functions in one region and execute them in AWS locations globally closer to the viewer, without provisioning or managing servers. Lambda@Edge scales automatically, from a few requests per day to thousands per second. Processing requests at AWS locations closer to the viewer than on origin servers significantly reduces latency and improves the user experience.
Option A is incorrect because although adding an event to the S3 bucket and then invoking the event by the Lambda function to customize the content may do the needful, a lot of manual intervention is required. With Lambda @ Edge, it can be done more easily.
Option B is incorrect because Step Function is normally used to sequence AWS Lambda functions and multiple AWS services. This scenario is not suitable.
Option D is incorrect because adding EC2 is not cost-efficient.
For more information on Lambda@Edge, please refer to the below Link-
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-at-the-edge.html