SAA-C03 · Question #278
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…
The correct answer is C. Use AWS Fargate to deploy the Windows batch job as a container. Use AWS Batch to manage. AWS Batch supports Windows-based jobs and automates provisioning and scaling of compute environments. Paired with AWS Fargate, it removes the need to manage infrastructure. This solution requires the least operational overhead and is cloud-native, providing flexibility and
Question
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?
Options
- ACreate a fleet of Amazon EC2 instances in an Auto Scaling group to handle the Windows batch
- BImplement an AWS Lambda function to process the Windows batch job. Use an Amazon
- CUse AWS Fargate to deploy the Windows batch job as a container. Use AWS Batch to manage
- DUse Amazon Elastic Kubernetes Service (Amazon EKS) on Amazon EC2 instances to
How the community answered
(40 responses)- A8% (3)
- B5% (2)
- C85% (34)
- D3% (1)
Explanation
AWS Batch supports Windows-based jobs and automates provisioning and scaling of compute environments. Paired with AWS Fargate, it removes the need to manage infrastructure. This solution requires the least operational overhead and is cloud-native, providing flexibility and
Community Discussion
No community discussion yet for this question.