The correct answer is A because the application is a lightweight data processing tool that always completes within 3 minutes , which fits well within the execution model of AWS Lambda . Lambda is a fully managed compute service that eliminates the need to provision or manage servers, clusters, operating systems, or container hosts. Since the company is willing to make any required changes to the image, packaging the workload as a Lambda container image is the option with the least operational overhead.
Lambda is well suited for short-lived, event-driven, or on-demand processing jobs. It automatically scales, charges only for execution time, and removes nearly all infrastructure administration. Compared with container orchestration services, Lambda requires less setup, less monitoring of infrastructure, and no task or cluster capacity planning.
Option B is incorrect because Amazon EKS with Fargate still requires Kubernetes management constructs and introduces more operational complexity than Lambda. Option C is simpler than EKS, but Amazon ECS with Fargate still involves managing task definitions, services, and networking, which is more overhead than Lambda for a brief processing job. Option D is incorrect because using a custom AMI with AWS Batch introduces more compute management and is unnecessary for a very short, lightweight workload.
AWS guidance favors serverless services when the workload is short-lived and infrastructure management should be minimized. Because this job always completes quickly and the company wants the least operational overhead, AWS Lambda with a container image is the best solution.
