An enterprise needs to migrate 800\text{ TB} of data from an on-premises NFS file system t… — AWS Certified Solutions Architect - Professional

An enterprise needs to migrate $800\text{ TB}$ of data from an on-premises NFS file system to an Amazon FSx for NetApp ONTAP file system in a target AWS account. The enterprise has a $300\text{ Mbps}$ dedicated network connection to AWS. The migration must be completed within $21\text{ days}$ . During this period, the on-premises file system will remain active, generating approximately $15\text{ TB}$ of incremental changes. The target file system must encrypt all data at rest using a customer managed key (CMK) in AWS KMS. Which of the following migration strategies is the most efficient and meets these requirements?

Order multiple AWS Snowball Edge Storage Optimized devices. Configure the Snowball jobs to use a destination Amazon S3 bucket and a KMS Customer Managed Key (CMK) for encryption. Copy the data from the on-premises NFS file system to the devices via their NFS interface. Once the data is imported to Amazon S3, use AWS DataSync to copy the data from the S3 bucket to the Amazon FSx for NetApp ONTAP file system. Deploy an on-premises AWS DataSync agent to perform a final incremental sync of the $15\text{ TB}$ delta from the on-premises NFS file system directly to the FSx for NetApp ONTAP file system.Answer
B
Order multiple AWS Snowball Edge Storage Optimized devices, specifying the Amazon FSx for NetApp ONTAP file system directly as the job's destination storage. Configure the Snowball jobs to encrypt the transferred data using the default AWS-managed KMS key (aws/s3). After the devices are processed, deploy an on-premises AWS DataSync agent to sync the remaining $15\text{ TB}$ delta directly from the on-premises NFS file system to the FSx for NetApp ONTAP file system.
C
Deploy AWS DataSync agents on-premises. Set up an AWS Direct Connect connection with a Direct Connect gateway. Associate the Direct Connect gateway directly with both the VPC containing the DataSync agent and the VPC containing the Amazon FSx for NetApp ONTAP file system to establish transitive routing between them. Run an online DataSync task over this connection to copy the entire $800\text{ TB}$ dataset and all subsequent changes directly to the FSx for NetApp ONTAP file system.
D
Order multiple AWS Snowball Edge Storage Optimized devices, specifying an Amazon S3 bucket as the destination and using a KMS Customer Managed Key (CMK). Copy the data to the devices. Once the data is imported to S3, set up an AWS Transfer Family SFTP server to pull the data from S3 and write it to the FSx for NetApp ONTAP file system. Use an on-premises SFTP client to transfer the $15\text{ TB}$ delta over the $300\text{ Mbps}$ link.

Answer

The most efficient strategy is to order multiple AWS Snowball Edge Storage Optimized devices to physically ship the

800\text{ TB}

of data encrypted with a Customer Managed Key (CMK) to Amazon S3, use AWS DataSync to copy that data from S3 to the target Amazon FSx for NetApp ONTAP file system, and use an on-premises AWS DataSync agent to sync the remaining

15\text{ TB}

delta over the dedicated network connection.

The correct strategy uses AWS Snowball Edge Storage Optimized devices to overcome the physical throughput limitations of the

300\text{ Mbps}

network link. Because Snowball Edge cannot directly target Amazon FSx, data must land in Amazon S3 first, encrypted using a KMS Customer Managed Key (CMK), which is required for Snowball Edge. AWS DataSync is then used to transfer the files from S3 to the FSx for NetApp ONTAP target. The final

15\text{ TB}

delta is copied online using an on-premises AWS DataSync agent, which can easily complete the incremental sync within the remaining time window.

Step-by-Step Solution

Calculate the network transfer time for the initial

800\text{ TB}

dataset over the

300\text{ Mbps}

connection.

300\text{ Mbps}

(assuming

80\%

network utilization), transferring

800\text{ TB}

takes approximately 308 days. This violates the 21-day migration timeline constraint, proving that offline transfer via the Snow Family is required.

To identify the necessity of offline data transfer based on physical time constraints.

Configure the AWS Snowball Edge job requirements, specifically the target service and encryption key types.

The target must be set to Amazon S3 (as Snowball does not support direct import to Amazon FSx). A KMS Customer Managed Key (CMK) must be selected because AWS Snowball Edge cannot modify policies on AWS-managed keys (like aws/s3) to grant permissions to the Snowball service.

To satisfy encryption compliance and Snowball service requirements.

Establish the internal AWS transfer path from the S3 staging bucket to the target FSx for NetApp ONTAP file system.

Configure AWS DataSync with the imported S3 bucket as the source and the FSx for NetApp ONTAP file system as the destination, running the sync task internally within AWS.

To move the bulk data to the final destination file system after the physical devices are ingested by AWS.

Plan the delta migration phase for the

15\text{ TB}

of changes.

Deploy an on-premises AWS DataSync agent to transfer the

15\text{ TB}

delta directly to the FSx for NetApp ONTAP file system over the network, which takes approximately 6 days and fits within the 21-day migration window.

To capture files modified during the Snowball shipping transit period without performing another full copy.

Key Concept

Selecting the optimal hybrid migration path using AWS Snowball Edge and AWS DataSync under tight time and bandwidth constraints.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic