AWS Certified Solutions Architect – Professional (SAP-C02) — Question 491

A company is migrating its blog platform to AWS. The company's on-premises servers connect to AWS through an AWS Site-to-Site VPN connection. The blog content is updated several times a day by multiple authors and is served from a file share on a network-attached storage (NAS) server.

The company needs to migrate the blog platform without delaying the content updates. The company has deployed Amazon EC2 instances across multiple Availability Zones to run the blog platform behind an Application Load Balancer. The company also needs to move 200 TB of archival data from its on-premises servers to Amazon S3 as soon as possible.

Which combination of stops will meet these requirements? (Choose two.)

Answer options

• A. Create a weekly cron job in Amazon EventBridge. Use the cron job to invoke an AWS Lambda function to update the EC2 instances from the NAS server.
• B. Configure an Amazon Elastic Block Store (Amazon EBS) Multi-Attach volume for the EC2 instances to share for content access. Write code to synchronize the EBS volume with the NAS server weekly.
• C. Mount an Amazon Elastic File System (Amazon EFS) file system to the on-premises servers to act as the NAS server. Copy the blog data to the EFS file system. Mount the EFS file system to the C2 instances to serve the content.
• D. Order an AWS Snowball Edge Storage Optimized device. Copy the static data artifacts to the device. Ship the device to AWS.
• E. Order an AWS Snowcons SSD device. Copy the static data artifacts to the device. Ship the device to AWS.

Correct answer: C, D

Explanation

Amazon EFS is a shared file system that can be mounted concurrently on-premises (via VPN/Direct Connect) and on EC2 instances across multiple Availability Zones, ensuring immediate, real-time updates for the blog platform. To migrate 200 TB of archival data quickly, AWS Snowball Edge Storage Optimized is the correct hardware choice because of its high capacity, whereas an AWS Snowcone SSD device is limited to 14 TB of usable space and is insufficient for this volume of data. Weekly sync options like those in A and B would introduce unacceptable delays for content that is updated multiple times a day.