Exam AWS Certified Solutions Architect - Professional topic 1 question 693 discussion

B is correct, the workload on cloud relies on the Windows based storage

I believe it's A. DataSync is for initial migration but it's not meant for ongoing. The better answer would be to use DataSync first then file gateway.

"Migration" is the keyword here. For "Migration" use DataSync and for "Integration" use Storage Gateway. https://tutorialsdojo.com/aws-datasync-vs-storage-gateway/

A FSx Storage gateway: https://bluexp.netapp.com/blog/aws-fsxo-blg-fsx-gateway-amazon-fsx-for-windows-at-on-premises-speed#:~:text=FSx%20File%20Gateway%20is%20a,FSx%20for%20Windows%20File%20Server.

For those who have selected Option B : The company can use AWS Storage Gateway to migrate the data from the Windows file server to AWS. AWS Storage Gateway can be deployed on-premises as a virtual machine (VM) and configured as a file gateway to provide a file interface to Amazon S3. The company can use the AWS Direct Connect connection to transfer data from the on-premises Windows file server to the AWS Storage Gateway, and then from the gateway to Amazon S3. The right option is A

Are most Windows based file system always FSx?

data migration strategy

B: "and needs the data to be available on a file system in the cloud. " No, access like a file system....on a file system

It is clear that we need Amazon Fx on the AWS side. For the on-prem, we can achieve this with DataSync or with Amazon FSx File Gateway (https://aws.amazon.com/storagegateway/file/fsx/). Option A is incomplete, cannot decide between A and B

if the company already relocated its workload to the cloud then storage gateway is the way...A make sense tho

Have to choose B - Windows based share file system + Question clearly states "requires data to be accessible through a cloud file system". A - cannot be right since it will use NFS/SMB protocol to cache & transfer files to an S3 bucket which is not a FS.

the statement says "Relocated" which means the migration has already happened and now what they want is just access to the data on-prem. So has to be storage gateway.

It's say that "relocated a portion of its Windows-based workload to AWS". So in this case we have to use Storage Gateway, because we need to access data both from on-premis and on AWS. So we can't use DataSync which is used for transfer 100% data to AWS and keep no data remain on-premis. That's my opinion, so the answer should be ANH

aggreed with hansmong

A - access file on s3 from on-prem C - datapipeline is an ETL tool, should be datasync in this case D - efs does not support Windows https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/AmazonEFS.html

You can use AWS DataSync to migrate on-premises data to Amazon S3, Amazon EFS, and Amazon FSx for Windows File Server. Configure DataSync to make an initial copy of your entire dataset, and schedule subsequent incremental transfers of changing data until the final cut-over from on-premises to AWS.

B is right