Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Nuanced question. B vs C. B. S3 File GW = yes. Mount to EC2 via NFS = yes. When changes occur in S3, RefreshCache API to update S3 File GW = No - if I am the server and I upload the file to S3 I don't need to refresh the S3 File GW to see the file, its already visible on the S3 File GW, this would only make sense if say something like a container stored the file on S3 bucket that is also linked to the S3 File GW > then yes. B also wants an API action per upload. C. Mount text is the misdirect. If I follow the C and cannot mount the NFS volume because its not possible = solution still works. Also note, this is one time setup with no regular mandated action - set and forget vs B which run an API command each time. Answer is C.
If you prioritize "least amount of effort", the S3 File Gateway (Option B) is the most straightforward. It's a simple mount that works with a legacy application without code changes, and it's a very common migration pattern.
This is a “can’t update the app, need S3” scenario. S3 File Gateway is designed for exactly this — mount as NFS, writes go local then sync to S3. FSx for Lustre is more for HPC use cases, and DataSync won’t give you continuous sync with <30min latency without extra work.