Which combination of stops will meet these requirements?
(Choose two.)
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.
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.
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.
Order an AWS Snowball Edge Storage Optimized device. Copy the static data artifacts to the device. Ship the device to AWS.
Order an AWS Snowcons SSD device. Copy the static data artifacts to the device. Ship the device to AWS.
Explanations:
Amazon EventBridge and Lambda are not suitable for regular updates of the blog content, as this method would not ensure real-time data synchronization for frequently updated content by multiple authors.
Amazon EBS Multi-Attach volumes are not designed for content sharing across multiple EC2 instances in a multi-AZ setup. This option would not facilitate real-time access to updated blog content across Availability Zones.
Amazon EFS is a scalable, shared file system that allows EC2 instances across multiple Availability Zones to access shared content, making it suitable for synchronizing and serving frequently updated blog content from on-premises.
AWS Snowball Edge Storage Optimized is designed for transferring large data volumes quickly to Amazon S3. It is ideal for migrating the 200 TB of archival data to AWS in an efficient, secure manner.
AWS Snowcone is a smaller device with limited storage capacity, making it unsuitable for transferring 200 TB of archival data to AWS, which exceeds Snowcone’s capacity.
I weigh that the answer is:
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.