Examkin

Soru

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

A company needs to migrate 500 TB500\text{ TB} of historical data from an on-premises NFS file system to Amazon S3. The initial migration must be completed within 30 days. After the initial migration, the company needs to replicate daily incremental updates of approximately 50 GB50\text{ GB} from the same NFS file system to Amazon S3. The company has a dedicated 100 Mbps100\text{ Mbps} internet connection available for this migration. Security policies require that all data at rest in Amazon S3 be encrypted using a Customer Managed Key (CMK) in AWS KMS, and the migration process must minimize administrative overhead. Which two actions should a Solutions Architect recommend to meet these requirements?

  1. Order multiple AWS Snowball Edge Storage Optimized devices, copy the initial 500 TB500\text{ TB} dataset locally to the devices, and ship them to AWS to import the data into the Amazon S3 bucket.Cevap
  2. Deploy an AWS DataSync agent on-premises, configure the source location as the NFS file system and the destination location as the Amazon S3 bucket, and schedule a daily task to replicate the 50 GB50\text{ GB} incremental updates.Cevap
  3. C
    Deploy AWS DataSync agents on-premises, and configure a migration task to transfer the initial 500 TB500\text{ TB} dataset over the dedicated 100 Mbps100\text{ Mbps} internet connection to the Amazon S3 bucket.
  4. D
    Configure AWS Transfer Family with an SFTP endpoint in a VPC, configure a Transit Gateway with a Direct Connect gateway to route the SFTP traffic, and run an on-premises script to migrate the initial 500 TB500\text{ TB} dataset over the network.
  5. E
    Configure the AWS Snowball Edge devices to encrypt the migrated data using the AWS-managed KMS key for Amazon S3 (`aws/s3`) to simplify key management during the import process.

Cevap

Order multiple AWS Snowball Edge Storage Optimized devices to import the initial 500 TB dataset into the Amazon S3 bucket, and deploy an AWS DataSync agent on-premises to sync the daily 50 GB incremental updates to Amazon S3.
Using multiple AWS Snowball Edge Storage Optimized devices for the initial transfer is correct because copying the data locally and shipping it physically bypasses the 100 Mbps network constraint, which would otherwise take over a year. Deploying AWS DataSync on-premises is correct because it provides an automated, managed mechanism to sync the daily 50 GB updates over the network link in about 1 hour with minimal administration.

Adım Adım Çözüm

1
Calculate the transfer duration for the initial 500 TB dataset over the 100 Mbps network connection.
Transferring 500 TB at 100 Mbps takes approximately 463 days (500×1012 bytes×8 bits/byte/108 bps=4×107 seconds500 \times 10^{12} \text{ bytes} \times 8 \text{ bits/byte} / 10^8 \text{ bps} = 4 \times 10^7 \text{ seconds}), which is far greater than the 30-day requirement. Therefore, an offline physical transfer (Snowball Edge) is required.
To determine whether the network bandwidth can support the initial migration within the specified timeline.
2
Calculate the transfer duration for the daily 50 GB incremental updates over the 100 Mbps network connection.
Transferring 50 GB at 100 Mbps takes approximately 1.1 hours (50×109 bytes×8 bits/byte/108 bps=4000 seconds50 \times 10^9 \text{ bytes} \times 8 \text{ bits/byte} / 10^8 \text{ bps} = 4000 \text{ seconds}), which easily fits into a daily maintenance window.
To determine whether the daily updates can be replicated over the network.
3
Select the correct AWS services that automate network replication and satisfy key-management compliance.
AWS DataSync is selected for the daily replication because it natively handles incremental synchronization with minimal administrative overhead. A Customer Managed Key (CMK) is required because AWS Snowball Edge import jobs cannot use AWS-managed keys.
To align the migration strategy with compliance and overhead minimization requirements.

Anahtar Kavram

Selecting data transfer strategies requires balancing network bandwidth constraints against data volume and timelines (the online vs. offline decision matrix). For initial bulk migrations where network transfer time exceeds the timeline, offline shipping with AWS Snowball Edge is required. For ongoing incremental updates that fit within the available network capacity, automated replication via AWS DataSync minimizes operational overhead. Additionally, AWS Snowball Edge require Customer Managed KMS keys (CMKs) rather than AWS-managed keys to allow custom policy delegation.
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru