SAP-C02 · Question #765
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…
The correct answer is C. Mount an Amazon Elastic File System (Amazon EFS) file system to the on-premises servers to D. Order an AWS Snowball Edge Storage Optimized device. Copy the static data artifacts to the. To migrate the frequently updated blog content from a NAS without interruption, Amazon EFS should be mounted on both on-premises and EC2 instances, allowing authors to continue updating content. For the 200 TB of archival data, an AWS Snowball Edge Storage Optimized device…
Question
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.)
Options
- ACreate a weekly cron job in Amazon EventBridge. Use the cron job to invoke an AWS Lambda
- BConfigure an Amazon Elastic Block Store (Amazon EBS) Multi-Attach volume for the EC2
- CMount an Amazon Elastic File System (Amazon EFS) file system to the on-premises servers to
- DOrder an AWS Snowball Edge Storage Optimized device. Copy the static data artifacts to the
- EOrder an AWS Snowcons SSD device. Copy the static data artifacts to the device. Ship the
How the community answered
(51 responses)- A4% (2)
- B10% (5)
- C67% (34)
- E20% (10)
Why each option
To migrate the frequently updated blog content from a NAS without interruption, Amazon EFS should be mounted on both on-premises and EC2 instances, allowing authors to continue updating content. For the 200 TB of archival data, an AWS Snowball Edge Storage Optimized device should be used for rapid, large-scale data transfer to Amazon S3.
A weekly cron job invoking an AWS Lambda function is not suitable for real-time synchronization of frequently updated file share content or for large-scale archival data transfer.
Amazon EBS Multi-Attach is for attaching a single EBS volume to multiple EC2 instances within the same Availability Zone for block storage, not for cross-premises file share synchronization or migrating 200 TB to Amazon S3.
Mounting an Amazon Elastic File System (Amazon EFS) to both on-premises servers and EC2 instances enables a seamless migration of the NAS file share, allowing multiple authors to continue updating blog content without interruption while simultaneously migrating the data to a highly available and scalable AWS file system.
Ordering an AWS Snowball Edge Storage Optimized device is the most efficient and fastest way to transfer 200 TB of archival data from on-premises to Amazon S3, significantly reducing the migration time compared to transferring over a VPN connection.
An AWS Snowcone SSD device has a much smaller capacity (up to 14 TB) compared to 200 TB of archival data, making it unsuitable for this scale of migration; AWS Snowball Edge is designed for much larger data transfers.
Concept tested: File System Migration (EFS), Large-scale Data Transfer (Snowball Edge)
Source: https://docs.aws.amazon.com/efs/latest/ug/on-premises-access.html
Community Discussion
No community discussion yet for this question.