An enterprise has a 600\text{ TB} historical dataset stored on an on-premises NFS file sys… — AWS Certified Solutions Architect - Professional

An enterprise has a $600\text{ TB}$ historical dataset stored on an on-premises NFS file system that must be migrated to Amazon S3. The enterprise has a dedicated $200\text{ Mbps}$ internet connection. In addition, the enterprise must establish an ingestion pipeline to receive daily reports totaling $100\text{ GB}$ from external vendors via the SFTP protocol, storing them directly in Amazon S3. The migration of the historical $600\text{ TB}$ dataset must be completed within $20$ days. Which two actions should the Solutions Architect take to meet these requirements? (Select TWO.)

Order multiple AWS Snowball Edge Storage Optimized devices, transfer the $600\text{ TB}$ dataset locally from the NFS server, and ship the devices back to AWS to import the data into the Amazon S3 bucket using an AWS KMS customer managed key.Answer
Provision an AWS Transfer Family server with an SFTP-enabled public endpoint, map the endpoint to the target Amazon S3 bucket, and configure external vendors to upload their daily reports using the SFTP protocol.Answer
C
Deploy AWS DataSync agents on-premises, establish a site-to-site VPN connection over the internet, and configure a DataSync task to copy the $600\text{ TB}$ NFS dataset directly to Amazon S3.
D
Order multiple AWS Snowball Edge Storage Optimized devices, transfer the $600\text{ TB}$ dataset locally from the NFS server, and configure the import job to encrypt the target Amazon S3 bucket using the default AWS managed key (`aws/s3`).
E
Establish an AWS Direct Connect connection with a Direct Connect Gateway to route the external vendors' SFTP traffic transitively through an on-premises environment before forwarding it to an AWS Transfer Family server using a private VPC endpoint.

Answer

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

600\text{ TB}

dataset using a customer managed KMS key, and provisioning an AWS Transfer Family SFTP-enabled public endpoint to ingest the daily

100\text{ GB}

vendor reports directly to Amazon S3.

Using AWS Snowball Edge Storage Optimized devices is the only way to meet the migration timeline for the

600\text{ TB}

dataset given the

200\text{ Mbps}

network limit. The import job requires an AWS KMS customer managed key because AWS managed keys do not support the delegation necessary for Snowball. Meanwhile, AWS Transfer Family with an SFTP public endpoint mapped to Amazon S3 offers a native, scalable solution for daily reports from external vendors.

Step-by-Step Solution

Calculate the network transfer time for the historical dataset to determine if online transfer is feasible.

200\text{ Mbps}

, transferring

600\text{ TB}

takes over

270

days, which is well beyond the

20

-day migration window.

This establishes that a physical offline transfer mechanism (Snowball Edge) is required rather than an online service like DataSync.

Evaluate the encryption requirements for the offline Snowball transfer.

Determine that an AWS KMS customer managed key must be configured because default AWS managed keys (`aws/s3`) do not support external access or cross-service delegation needed by the Snowball import process.

This guarantees compliance with security rules and ensures the Snowball import task succeeds.

Determine the optimal endpoint configuration for the SFTP ingestion pipeline.

Deploy an AWS Transfer Family SFTP-enabled public endpoint backed by Amazon S3 to support external vendors directly without complex transitive routing.

This provides a highly available, simple, and standard method for secure public ingestion.

Key Concept

Large-scale data migration decisions based on bandwidth limits, execution timelines, and service constraints (Snowball vs DataSync and Transfer Family).

Estimated Time:3m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic