Examkin

Soru

Zorluk: OrtaLarge-Scale Data Transfer using Snow Family, DataSync, and Transfer Family

A healthcare enterprise is planning to migrate a 680 TB680\text{ TB} dataset from an on-premises S3-compatible object storage system to an Amazon S3 bucket. The enterprise has a 100 Mbps100\text{ Mbps} internet connection and a dedicated 1 Gbps1\text{ Gbps} AWS Direct Connect connection. To minimize impact on other corporate workloads, only 150 Mbps150\text{ Mbps} of the Direct Connect bandwidth can be allocated for this migration. The migration must be completed within 30 days. The source dataset is actively modified, with approximately 2 TB2\text{ TB} of new files added weekly. Security policies require all data to be encrypted at rest in the target bucket using an AWS KMS Customer Managed Key (CMK). Which migration strategy meets these requirements within the specified timeframe and with the lowest operational overhead?

  1. A
    Deploy multiple AWS DataSync agents on-premises. Configure a DataSync task with the on-premises S3-compatible storage as the source and the target S3 bucket as the destination, using the KMS Customer Managed Key for destination encryption. Execute the task over the Direct Connect connection using the allocated 150 Mbps150\text{ Mbps} bandwidth limit.
  2. B
    Order multiple AWS Snowball Edge Storage Optimized devices. Copy the initial data from the on-premises storage to the devices using the S3-compatible endpoint, encrypting it with the AWS-managed KMS key (`aws/s3`). Ship the devices to AWS. Once ingested, deploy an AWS DataSync agent on-premises, create a task from the S3-compatible source to the target S3 bucket, and execute it over the Direct Connect link to sync the remaining delta changes.
  3. Order multiple AWS Snowball Edge Storage Optimized devices. Copy the initial data from the on-premises storage to the devices using the S3-compatible endpoint, encrypting it with the KMS Customer Managed Key. Ship the devices to AWS. Once ingested, deploy an AWS DataSync agent on-premises, create a task from the S3-compatible source to the target S3 bucket, and execute it over the Direct Connect link to sync the remaining delta changes.Cevap
  4. D
    Order multiple AWS Snowball Edge Storage Optimized devices. Copy all data to the devices using the S3-compatible endpoint, encrypting it with the KMS Customer Managed Key, and ship them to AWS. Perform weekly shipments of additional devices containing the 2 TB2\text{ TB} updates to AWS for ingestion until the migration project is completed.

Cevap

Order multiple AWS Snowball Edge Storage Optimized devices to copy the initial data using a Customer Managed Key, ship them to AWS, and then use an AWS DataSync task to synchronize the remaining delta changes over the Direct Connect link.
The correct strategy uses multiple AWS Snowball Edge Storage Optimized devices to transport the bulk data (680 TB680\text{ TB}), which solves the network bandwidth limitation. Once the bulk data is ingested, AWS DataSync is used to replicate the remaining delta changes (2 TB2\text{ TB} per week) over the 150 Mbps150\text{ Mbps} connection. Using a Customer Managed Key meets both the encryption policy and Snowball compatibility requirements.

Adım Adım Çözüm

1
Calculate network migration viability for bulk data.
Transferring 680 TB680\text{ TB} over 150 Mbps150\text{ Mbps} requires approximately 420 days (680×1012×8/150,000,000≈36,266,667680 \times 10^{12} \times 8 / 150,000,000 \approx 36,266,667 seconds), which is far beyond the 30-day limit.
Determines whether an online-only migration using AWS DataSync is feasible.
2
Select the bulk transfer mechanism and configure encryption.
Order AWS Snowball Edge Storage Optimized devices and copy the 680 TB680\text{ TB} base dataset using a Customer Managed Key (CMK) for encryption.
Allows secure physical shipment of the bulk dataset within 1-2 weeks.
3
Synchronize active updates and delta changes.
Deploy an AWS DataSync agent on-premises to sync the weekly 2 TB2\text{ TB} changes to the target S3 bucket over the Direct Connect link.
Allows capturing updates made during the Snowball shipping and processing window within a few days, finishing the migration inside the 30-day target.

Anahtar Kavram

Combining offline physical migration (Snowball Edge) with online delta replication (DataSync) for large-scale datasets with limited bandwidth and strict migration windows.
Bu soruyu puanla

Konular

Large-Scale Data Transfer using Snow Family, DataSync, and Transfer Family

Bu konudan daha fazla soru