SAP-C02 Question #525: Real Exam Question with Answer & Explanation

Question

A company runs an application in an on-premises data center. The application gives users the ability to upload media files. The files persist in a file server. The web application has many users. The application server is overutilized, which causes data uploads to fail occasionally. The company frequently adds new storage to the file server. The company wants to resolve these challenges by migrating the application to AWS. Users from across the United States and Canada access the application. Only authenticated users should have the ability to access the application to upload files. The company will consider a solution that refactors the application, and the company needs to accelerate application development. Which solution will meet these requirements with the LEAST operational overhead?

Options

• AUse AWS Application Migration Service to migrate the application server to Amazon EC2
• BUse AWS Application Migration Service to migrate the application server to Amazon EC2
• CCreate a static website for uploads of media files. Store the static assets in Amazon S3. Use
• DUse AWS Amplify to create a static website for uploads of media files. Use Amplify Hosting to

Explanation

Option D is correct because AWS Amplify is purpose-built to accelerate web application development with minimal operational overhead - it handles hosting, CI/CD, authentication (via Amazon Cognito integration), and global CDN distribution out of the box, directly satisfying the requirements for authenticated access, fast development, and coverage across the US and Canada.

Options A and B (both describe lifting the app to EC2 via Application Migration Service) are wrong because they are a lift-and-shift approach - they do nothing to refactor the app, don't reduce operational overhead, still require you to manage EC2 instances and scaling, and don't natively solve the overutilization or storage growth problems.

Option C is likely wrong because a plain S3 static website lacks built-in authentication and CDN acceleration without significant additional configuration (you'd need to manually wire up CloudFront, Cognito, etc.), which increases operational overhead compared to Amplify's integrated stack.

Memory tip: When you see the keywords "accelerate development + least operational overhead + authenticated users + static/refactored web app," think Amplify - it bundles hosting, auth, CDN, and CI/CD into one managed service so you manage none of that infrastructure yourself.

No community discussion yet for this question.