An enterprise wants to migrate a 1.2\text{ PB} dataset from an on-premises NetApp ONTAP NF… — AWS Certified Solutions Architect - Professional

An enterprise wants to migrate a $1.2\text{ PB}$ dataset from an on-premises NetApp ONTAP NFSv4 file system to Amazon FSx for NetApp ONTAP located in a target VPC. The enterprise also has multiple spoke VPCs that require access to this file system during the migration. The target VPC is connected to the on-premises network via a Transit Gateway and an AWS Direct Connect connection with a $1\text{ Gbps}$ transit capacity. The migration must be completed within $30\text{ days}$ . The company's security policy requires that all data must be encrypted in transit and at rest using an AWS KMS Customer Managed Key (CMK) owned by the target AWS account, and no traffic can traverse the public internet. Which of the following is the most efficient and compliant architecture to migrate this data within the required timeframe?

Order multiple AWS Snowball Edge Storage Optimized devices from the target AWS account, specifying the target account's Customer Managed Key (CMK) for encryption. Copy the data from the on-premises NFS file system to the Snowball Edge devices using the built-in NFS interface. Ship the devices back to AWS to import the data into an Amazon S3 bucket encrypted with the CMK. Use AWS DataSync to copy the data from the S3 bucket to the Amazon FSx for NetApp ONTAP file system within the AWS region.Answer
B
Deploy AWS DataSync agents on-premises on VMware ESXi. Configure an AWS DataSync task to copy the data directly from the on-premises NFSv4 file system to the Amazon FSx for NetApp ONTAP file system over the $1\text{ Gbps}$ Direct Connect connection via the Transit Gateway. Configure the task to encrypt the data at rest using the target account's Customer Managed Key (CMK).
C
Associate the Direct Connect Gateway directly with the target VPC and the spoke VPCs to allow transitive routing between the on-premises file system and all VPCs. Deploy AWS DataSync agents on-premises and configure a task to transfer the data directly to the FSx for NetApp ONTAP file system over the network connection, using the AWS-managed KMS key aws/fsx for at-rest encryption.
D
Order multiple AWS Snowball Edge Storage Optimized devices from the source AWS account. Copy the data from the on-premises NFS file system to the devices. Once the devices are shipped back to AWS and the data is loaded into a source S3 bucket, configure S3 Cross-Region Replication (CRR) to transfer the data to a target S3 bucket in the target account, using the AWS-managed KMS key aws/s3 for encryption. Then, mount the target S3 bucket directly to FSx for NetApp ONTAP.

Answer

Ordering multiple AWS Snowball Edge Storage Optimized devices from the target AWS account to copy the NFS data, shipping them back to AWS to import the data into Amazon S3, and then using AWS DataSync within the AWS region to transfer the data from S3 to Amazon FSx for NetApp ONTAP is the most efficient and compliant architecture.

The correct answer identifies that a

1.2\text{ PB}

dataset cannot be transferred over a

1\text{ Gbps}

connection within

30\text{ days}

(which would take over

111\text{ days}

even under ideal conditions), necessitating an offline migration using AWS Snowball Edge Storage Optimized devices. Ordering the devices from the target AWS account using the target account's Customer Managed Key (CMK) satisfies the KMS compliance requirements. Using the built-in NFS interface on the Snowball Edge allows direct copying of the NFSv4 filesystem. Once imported into Amazon S3, using AWS DataSync within the AWS region avoids using the on-premises Direct Connect link and allows fast ingestion into FSx for NetApp ONTAP.

Step-by-Step Solution

Calculate the network transfer time for

1.2\text{ PB}

of data over a

1\text{ Gbps}

link.

The theoretical transfer time is

\approx 111.1\text{ days}

(assuming

100\%

network efficiency), which exceeds the

30\text{ days}

project constraint, indicating that an offline physical migration via AWS Snowball Edge is required.

To determine whether an online network migration or an offline physical transfer is necessary to meet the scheduling requirements.

Select the appropriate account context and key type for the AWS Snowball Edge devices.

Ordering the devices from the target AWS account using the target account's Customer Managed Key (CMK) ensures compliance with the encryption requirements and avoids the cross-account limitations of AWS-managed keys.

AWS-managed keys (such as aws/s3) cannot be shared across different accounts, making it critical to use a Customer Managed Key (CMK) when cross-account sharing or replication is involved.

Determine the data ingestion path from the imported S3 bucket to Amazon FSx for NetApp ONTAP.

AWS DataSync is selected to transfer the data from the Amazon S3 bucket to the Amazon FSx for NetApp ONTAP file system within the AWS region, which completes rapidly and does not affect on-premises bandwidth.

Unlike FSx for Lustre, FSx for NetApp ONTAP does not natively mount S3 buckets as backing stores, requiring an active synchronization mechanism like AWS DataSync to copy data.

Key Concept

Selecting between online and offline data migration methods based on dataset size and network bandwidth limitations, combined with KMS key sharing policies and destination storage integration capabilities.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic