A company is moving its blog platform to AWS. On‑premises servers connect to AWS over a Site-to-Site VPN. Multiple authors update blog content several times per day; the content is served from a NAS file share. The company must migrate the blog without blocking ongoing content updates. The blog runs on EC2 instances across multiple Availability Zones behind an Application Load Balancer. The company also needs to transfer 200 TB of archival data from on‑premises to Amazon S3 as quickly as possible. Which combination of steps will satisfy these requirements? (Choose two.)

Mounting an Amazon EFS file system from on-premises servers allows the EFS to act as the central NAS. This enables a seamless migration by copying blog content to EFS while authors continue updates. The EC2 instances then mount the same EFS, ensuring they serve the most current content without interruption. This approach supports ongoing updates and multi-AZ access. Ordering an AWS Snowball Edge Storage Optimized device is the most efficient way to transfer 200 TB of archival data quickly. Snowball Edge is designed for large-scale data transfers, significantly faster than transferring over the Site-to-Site VPN. Incorrect options: Weekly cron rules and Lambda functions for updates would lead to significant content staleness, as updates occur "several times per day." Amazon EBS Multi-Attach volumes are block storage, not suitable for shared file system access across multiple EC2 instances in different AZs for a blog platform without complex cluster software. Also, weekly synchronization would cause data inconsistency. AWS Snowcone SSD devices are suitable for smaller data transfers (up to 8 TB), not the 200 TB specified, making Snowball Edge Storage Optimized the correct choice for scale.