An enterprise is migrating its legacy data center workloads to AWS. The migration involves… — AWS Certified Solutions Architect - Professional

An enterprise is migrating its legacy data center workloads to AWS. The migration involves two primary NFS-based datasets that must be migrated within a strict $30\text{-day}$ window:

* Dataset 1: A $1.2\text{ PB}$ historical archive dataset containing static files. This data will be migrated to Amazon S3 and must be accessible by an external, third-party auditing application located in a separate AWS account.
* Dataset 2: An $80\text{ TB}$ active operational dataset that is continuously updated. This data must be migrated to an Amazon EFS file system, and all POSIX metadata (ownership, permissions, and directory structures) must be preserved.

The company has a $1\text{ Gbps}$ AWS Direct Connect connection, but bandwidth throttling limits the maximum dedicated network throughput for migration traffic to $400\text{ Mbps}$ . All data at rest must be encrypted using an AWS KMS key that supports cross-account sharing.

Which two actions should the Solutions Architect recommend to achieve this migration within the required timeline? (Select TWO.)

Order multiple AWS Snowball Edge Storage Optimized devices to import the $1.2\text{ PB}$ archive dataset to Amazon S3. Configure the Snowball jobs to encrypt the imported data using a Customer Managed Key (CMK) in AWS KMS.Cevap
Deploy AWS DataSync agents on-premises and configure a task to replicate the $80\text{ TB}$ operational dataset to Amazon EFS over the Direct Connect connection, enabling the options to preserve group ID, owner ID, permissions, and timestamps.Cevap
C
Deploy AWS DataSync agents on-premises and configure a task to replicate both the $1.2\text{ PB}$ archive dataset and the $80\text{ TB}$ operational dataset to AWS over the dedicated Direct Connect connection to centralize and simplify migration management.
D
Order multiple AWS Snowball Edge Storage Optimized devices to import the $1.2\text{ PB}$ archive dataset to Amazon S3. Configure the Snowball jobs to encrypt the data at rest using the default AWS-managed key (aws/s3) to minimize key management complexity.
E
Deploy AWS DataSync agents on-premises to replicate the $80\text{ TB}$ operational dataset to Amazon EFS. Establish network path connectivity by routing the DataSync traffic over the Direct Connect connection into a transit VPC, and then transitively route it to the destination EFS VPC using an established VPC Peering connection between the transit VPC and the EFS VPC.

Cevap

The correct architecture requires ordering multiple AWS Snowball Edge Storage Optimized devices to migrate the

1.2\text{ PB}

archive dataset to Amazon S3 using a Customer Managed Key (CMK), and deploying AWS DataSync agents on-premises to replicate the active

80\text{ TB}

operational dataset directly to Amazon EFS over the Direct Connect connection while preserving POSIX metadata.

The correct solutions combine an offline and online migration strategy based on bandwidth constraints. The

1.2\text{ PB}

archive dataset is too large to fit over the

400\text{ Mbps}

dedicated network allocation within 30 days. Multiple AWS Snowball Edge Storage Optimized devices must be used. To allow the third-party auditing application in a separate AWS account to read this data, the Snowball job must use a Customer Managed Key (CMK) with a key policy configured for cross-account access. The

80\text{ TB}

active operational dataset can be transferred within the timeline (taking ~18.5 days) and should be migrated online using AWS DataSync to ensure active updates and POSIX metadata are natively preserved when writing to Amazon EFS.

Adım Adım Çözüm

Calculate the maximum data that can be transferred over the network within the timeline.

The dedicated network allocation is

400\text{ Mbps}

. In

30\text{ days}

, the maximum theoretical data transfer is:

400\text{ Mbps} \times 86400\text{ seconds/day} \times 30\text{ days} = 1.0368 \times 10^{15}\text{ bits} \approx 129.6\text{ TB}

Determining network capacity defines which datasets must be shipped physically versus which can be copied online.

Select the transfer method for the

1.2\text{ PB}

historical archive dataset.

Since

1.2\text{ PB}

(

1,200\text{ TB}

) exceeds the

129.6\text{ TB}

maximum online transfer limit, this dataset must be transferred offline using AWS Snowball Edge devices.

Using the network for this dataset would take roughly 278 days, failing the 30-day timeline requirement.

Evaluate the encryption requirements for the archive dataset.

The archive data must be encrypted using a Customer Managed Key (CMK) in AWS KMS because AWS-managed keys (such as `aws/s3`) cannot be shared across accounts to allow the third-party auditing application access.

Custom key policies can only be attached to Customer Managed Keys.

Select the transfer method and network routing path for the

80\text{ TB}

operational dataset.

The

80\text{ TB}

dataset fits within the remaining transfer window (taking approximately 18.5 days over

400\text{ Mbps}

). Use AWS DataSync to preserve ownership, permissions, and directory structures natively on Amazon EFS.

AWS DataSync simplifies migration over network links while automatically maintaining full POSIX compliance for EFS.

Anahtar Kavram

Selecting data transfer tools based on network constraints and security requirements

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru