AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial-services firm is migrating its on-premises batch document-conversion system to AWS. The application is written in .NET 7 and must run on Windows Server 2022. Each conversion task writes temporary files to a shared SMB directory that must be concurrently accessible by every running task. The engineering team will containerize the workload and wants to minimize the operational effort required to patch and scale the compute layer while still running Windows containers and providing a highly available shared file system that every task can mount at run time.
Which solution meets these requirements MOST effectively?
Build a Windows container image, deploy it to an Amazon ECS service that uses the AWS Fargate launch type, and configure the task definition to mount an Amazon FSx for Windows File Server volume.
Build a Windows container image, deploy it to an Amazon ECS service that uses an EC2 capacity provider with Windows Server 2022 instances, and configure the task definition to mount an Amazon FSx for Windows File Server volume.
Build a Linux container image, deploy it to an Amazon ECS service on AWS Fargate, and mount an Amazon EFS file system inside the task.
Deploy the application by using AWS Elastic Beanstalk in a Windows environment and configure the environment to mount an Amazon EFS file system.
Running Windows containers that need a shared SMB volume is natively supported by Amazon ECS when the service is backed by Windows EC2 instances and the task definition mounts an Amazon FSx for Windows File Server volume. FSx delivers a fully managed Windows file system that can be attached to each task, and Service Auto Scaling with an EC2 capacity provider handles cluster scaling while the ECS control plane removes much of the day-to-day instance management overhead.
AWS Fargate for Windows containers cannot mount FSx for Windows File Server, so that option cannot satisfy the shared-storage requirement. Using Fargate with Linux containers would avoid instance management but the workload is Windows-only. Elastic Beanstalk Windows environments cannot mount Amazon EFS, and EFS is not supported by Windows instances, so that option also fails the storage requirement.
Therefore, deploying the Windows container image to an ECS service that uses an EC2 capacity provider with Windows Server 2022 instances-and mounting an FSx for Windows File Server volume in the task definition-is the only choice that fulfills all technical and operational goals.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why can't AWS Fargate for Windows containers use Amazon FSx for Windows File Server?
Open an interactive chat with Bash
What are the advantages of using Amazon FSx for Windows File Server in this scenario?
Open an interactive chat with Bash
What is the main purpose of an EC2 capacity provider in ECS, and why is it used here?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Accelerate Workload Migration and Modernization
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access