Q47 — AWS SAA-C03 Ch.13

Question 47 of 100 | ← Chapter 13

Q947. A company is migrating a daily Microsoft Windows batch job from the company's on-premises environment to AWS.The current batch job runs for up to 1 hour.The company wants to modernize the batch job process for the cloud environment.Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: C. Use AWS Fargate to deploy the Windows batch job as a container. Use AWS Batch to manage the batch job processing.

Explanation

The best solution with the least operational overhead is C. Use AWS Fargate to deploy the Windows batch job as a container. Use AWS Batch to manage the batch job processing.Here's why:Serverless Batch Processing: AWS Fargate provides a serverless compute engine for containers, eliminating the need for managing EC2 instances. This reduces operational overhead significantly. Managed Batch Service: AWS Batch is a fully managed batch processing service that handles scheduling, queuing, and execution of batch jobs. It automates many tasks, reducing operational burden. Containerization: Containerizing the Windows batch job allows for easier deployment, portability, and scalability.Minimal Management: Using Fargate and Batch minimizes the need for infrastructure management, patching, and scaling, leading to a simpler and more efficient solution.Why other options are less ideal:A. Create a fleet of Amazon EC2 instances in an Auto Scaling group to handle the Windows batch job processing: While Auto Scaling helps manage EC2 instances, it still requires managing the underlying infrastructure, scaling, and patching.B. Implement an AWS Lambda function to process the Windows batch job. Use an Amazon EventBridge rule to invoke the Lambda function: Lambda is great for event-driven workloads, but it might not be ideal for a 1-hour batch job. Lambda has time limits, and managing a large batch job within those limits could be challenging.D. Use Amazon Elastic Kubernetes Service (Amazon EKS) on Amazon EC2 instances to orchestrate Windows containers for the batch job processing: EKS provides container orchestration, but it requires managing the underlying EC2 infrastructure, adding complexity and operational overhead.In summary:Option C offers the most streamlined and operationally efficient solution for migrating the Windows batch job to AWS. Fargate and Batch provide a serverless and fully managed approach, minimizing infrastructure management and simplifying the migration process.