A company needs to migrate 850\text{ TB} of data from an on-premises SMB file share to Ama… — AWS Certified Solutions Architect - Professional

A company needs to migrate $850\text{ TB}$ of data from an on-premises SMB file share to Amazon EFS. The migration must be completed within $35\text{ days}$ . The company has an active $1\text{ Gbps}$ AWS Direct Connect connection, but due to production workloads, only $150\text{ Mbps}$ of bandwidth can be allocated for this migration. All data must be encrypted at rest using an AWS Key Management Service (AWS KMS) customer managed key that can be shared with a secondary auditing AWS account. Which migration strategy will meet these requirements within the specified timeline?

Order multiple AWS Snowball Edge Storage Optimized devices, specifying the customer managed KMS key during job creation. Copy the data from the on-premises SMB share to the devices. Once the data is imported into an intermediate Amazon S3 bucket, configure an AWS DataSync task to copy the data from the S3 bucket to the Amazon EFS file system. Finally, configure another DataSync task to sync any incremental changes from the on-premises SMB share directly to Amazon EFS over the Direct Connect connection.Answer
B
Deploy multiple AWS DataSync agents on-premises. Configure a DataSync task to transfer the data directly from the on-premises SMB share to the Amazon EFS file system over the $150\text{ Mbps}$ allocated Direct Connect bandwidth, using a customer managed KMS key to encrypt the files during transit and at rest.
C
Order multiple AWS Snowball Edge Storage Optimized devices. Establish an AWS Transit Gateway and configure transit routing to allow the physical Snowball Edge devices to establish an IPSec VPN tunnel directly to the on-premises network over the Direct Connect link. Copy the data from the SMB share to the devices over this secure tunnel, then return the devices to AWS to be loaded directly into Amazon EFS.
D
Order multiple AWS Snowball Edge Storage Optimized devices, specifying the AWS managed KMS key (`aws/s3`) for encryption. Copy the data from the on-premises SMB share to the devices. Once the data is loaded into an intermediate Amazon S3 bucket, use AWS DataSync to copy the data to Amazon EFS. Share the AWS managed key with the secondary auditing account to allow decryption of the S3 objects for verification.

Answer

Order multiple AWS Snowball Edge Storage Optimized devices, specifying the customer managed KMS key during job creation. Copy the data from the on-premises SMB share to the devices. Once the data is imported into an intermediate Amazon S3 bucket, configure an AWS DataSync task to copy the data from the S3 bucket to the Amazon EFS file system. Finally, configure another DataSync task to sync any incremental changes from the on-premises SMB share directly to Amazon EFS over the Direct Connect connection.

The correct option correctly addresses both the bandwidth bottleneck and the security constraints. With only

150\text{ Mbps}

of available bandwidth, an online transfer of

850\text{ TB}

would take over

500\text{ days}

, making AWS Snowball Edge necessary. Since Snowball Edge does not load directly into Amazon EFS, loading the data into Amazon S3 first and then using AWS DataSync to copy it to EFS is the standard pattern. Using a customer managed KMS key enables the cross-account key policy modification required to share the key with the auditing account. Finally, running a small incremental sync via DataSync catches any write operations performed during the shipping time.

Step-by-Step Solution

Calculate the time required for a network-based transfer over the allocated bandwidth.

Transferring

850\text{ TB}

(

6.8 \times 10^{15}\text{ bits}

) over a

150\text{ Mbps}

(

1.5 \times 10^8\text{ bps}

) link would take approximately

4.53 \times 10^7\text{ seconds}

(about

524\text{ days}

), which exceeds the

35\text{-day}

limit.

Determines whether an online or offline migration strategy is required to meet the timeline.

Select the appropriate physical transfer mechanism and security configuration.

Identify AWS Snowball Edge Storage Optimized as the solution. Select a KMS customer managed key (CMK) during job creation to support the cross-account sharing requirement.

AWS managed KMS keys cannot be shared cross-account, necessitating a customer managed key.

Determine the path to the target storage system.

Import the data from Snowball Edge into an intermediate Amazon S3 bucket, and then use AWS DataSync to transfer the data from Amazon S3 to the target Amazon EFS file system.

Snowball Edge does not support direct ingestion into Amazon EFS.

Plan the final sync for delta changes.

Configure AWS DataSync to sync remaining delta changes from the on-premises SMB share to Amazon EFS over the Direct Connect connection once the bulk data import is complete.

Ensures that any files created or modified during the transit time of the Snowball devices are captured.

Key Concept

Selecting the optimal hybrid storage migration pattern using AWS Snowball Edge and AWS DataSync based on network capability, and configuring KMS Customer Managed Keys for cross-account security requirements.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic