What should a solutions architect do to meet these requirements?

By:
In: SAA-C02
Tagged:
With: 1 Comment
A company has more than 5 TB of file data on Windows file servers that run on premises.Users and applications interact with the data each day.The company is moving its Windows workloads to AWS.As the company continues this process, the company requires access to AWS and on-premises file storage with minimum latency.The company needs a solution that minimizes operational overhead and requires no significant changes to the existing file access patterns.The company uses an AWS Site-to-Site VPN connection for connectivity to AWS.

What should a solutions architect do to meet these requirements?

Deploy and configure Amazon FSx for Windows File Server on AWS. Move the on-premises file data to FSx for Windows File Server. Reconfigure the workloads to use FSx for Windows File Server on AWS.

Deploy and configure an Amazon S3 File Gateway on premises. Move the on-premises file data to the S3 File Gateway. Reconfigure the on-premises workloads and the cloud workloads to use the S3 File Gateway.

Deploy and configure an Amazon S3 File Gateway on premises. Move the on-premises file data to Amazon S3. Reconfigure the workloads to use either Amazon S3 directly or the S3 File Gateway, depending on each workload’s location.

Deploy and configure Amazon FSx for Windows File Server on AWS. Deploy and configure an Amazon FSx File Gateway on premises. Move the on-premises file data to the FSx File Gateway. Configure the cloud workloads to use FSx for Windows File Server on AWS. Configure the on-premises workloads to use the FSx File Gateway.

Explanations:

While Amazon FSx for Windows File Server is suitable for Windows workloads, moving the on-premises data to it and reconfiguring workloads may require significant changes to existing access patterns, which the company wants to avoid.

Deploying an Amazon S3 File Gateway does allow on-premises access to S3, but it requires significant reconfiguration of workloads to use the S3 File Gateway, which does not align with the requirement to minimize operational overhead and changes to access patterns.

Similar to option B, using an S3 File Gateway requires reconfiguration of workloads, either to access Amazon S3 directly or through the gateway. This does not meet the requirement of maintaining existing access patterns and minimizing changes.

Deploying Amazon FSx for Windows File Server on AWS and configuring an FSx File Gateway on-premises allows for seamless integration between AWS and on-premises storage. This solution minimizes latency and operational overhead while requiring minimal changes to existing file access patterns.

2025-09-29

1 Comment

  1. Carol
    Author

    I systematize that the answer is:
    Deploy and configure Amazon FSx for Windows File Server on AWS. Deploy and configure an Amazon FSx File Gateway on premises. Move the on-premises file data to the FSx File Gateway. Configure the cloud workloads to use FSx for Windows File Server on AWS. Configure the on-premises workloads to use the FSx File Gateway.

Leave a Reply

Your email address will not be published. Required fields are marked *

one × five =