Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 35 discussion

B. Use AWS DataSync to schedule a daily task to replicate data between the on-premises Windows file server and Amazon FSx. D. Use AWS DataSync to schedule a daily task to replicate data between the on-premises Windows file server and Amazon Elastic File System (Amazon EFS) are also valid options. They both use DataSync to schedule a daily task to replicate the data between on-premises and cloud, the main difference is the type of file system in the cloud, Amazon FSx or Amazon Elastic File System (Amazon EFS).

For an and b we need FSx. Data Sync is useful for a batch and is able to process large data volumes. in (a) the data is also accessible from on prem. The data volume is quite small (5 GB) per day therefore (a) is feasible. In my opinion, the key requirement is "data to be available on a file system in the cloud" and ",, migrating workloads" and I think this includes that it can be accessed from servers on prem. In addition (a) replaces only a Windows File server and not the overall windows landscape in AWS. There I vote for (a), AWS Data Sync. See https://tutorialsdojo.com/aws-datasync-vs-storage-gateway/ for a comparison

I had to pick B over A because it didn't specify "Fsx File Gateway" it just said "File Gateway" which is a separate product used to send data to S3 rather than a file system like Fsx File Gateway would do. Tricky one.

Amazon FSx for Windows File Server is the best match for Windows-based workloads. AWS DataSync can efficiently handle scheduled transfers, perfect for 5 GB/day. Ideal if the goal is daily replication/migration to make data available in AWS without requiring real-time syncing. Argument: File Gateway offers real-time access to data from both on-premises and cloud via caching. If immediate cloud access to on-premises files is needed, Amazon FSx File Gateway can serve as a bridge. Valid if the requirement is active hybrid access. But not a "data migration" strategy, it doesn't move data to the cloud, it fronts S3 of Fsx with a cache.

Has to be A, it's the only option if you want data to be available on the cloud instantly. B does a daily sync, which means the data is outdated throughout the day

Nothing suggests that we want to do a daily sync in the question. A makes more sense because the files will be always available to use from the cloud. In 99% of the cases that's better, and if it's the remaining 1%, they would have surely mentioned it in the question.

DayaSync allows migration and continue access to both on-prem file server and FSx in a synchronised manner.

A seem to be a more efficient solution as it eliminates duplicate storage. Storage gateway has to be FSx, which is implicit in this option.

Comparing A and B, finally I choosed B due to the "scheduling". In A, despite file gateway could provide or combine a scheduling function, B explicitly says that operation.

Workloads are only partially migrated which means data need to be accessed simultaneously by on-prem VMs and the already migrated VMs in cloud And we should assume that the data should be up to date all the time not just updated periodically Finally, File Gateway could be Amazon FSX File GW Hence clearly A.

D is wrong cos EFS support only Linux File System

Using Amazon FSx File Gateway, you can access data with low latency from on-premise and also in-cloud always. Why do you neet to batch datasync as like B?

B. Use AWS DataSync to schedule a daily task to replicate data between the on-premises Windows file server and Amazon FSx.

Because part of the workloads have already been migrated we need a solution that keeps the data consistent between on prem and the cloud. With DataSync files stored by systems on-prem would be visible in the cloud only the following day. This could cause data inconsistencies and business disruption. The best solution is to use a file gateway to maintain files synchronised at all times. 5GBs/day is easily transferable over DX

B, for sure. Needs the data to be available on a file system in the cloud.

Windows file server -> FSx (cristal clear)

A is not the data migration