Data, Network, And Migration Mixed Drills

Concepts Covered

• Mixed migration and network scenario reading
• DataSync versus Storage Gateway
• Snow Family offline movement
• DMS and schema conversion boundaries
• Site-to-Site VPN versus Direct Connect
• Transit Gateway, peering, and PrivateLink
• File, object, block, and database migration
• Hybrid access patterns
• Cutover and rollback thinking
• Cost and transfer tradeoffs

1. Domain Mental Model

Migration questions become confusing because AWS has many movement services, and their names overlap in a learner's memory. The exam is usually not asking, "Which service sounds like migration?" It is asking what is moving, how it moves, and what constraints surround the move.

Use this frame:

source -> data type -> change rate -> network path -> target -> cutover

Files copied from an on-premises NFS share are not the same problem as a live relational database migration. A one-time petabyte transfer is not the same problem as recurring hybrid file access. Private application connectivity is not the same problem as bulk object movement.

2. Official Task Map

This drill set spans SAA-C03 Domain 2, Domain 3, and Domain 4.

Domain 2 includes loosely coupled, highly available, and fault-tolerant architectures. Domain 3 includes high-performing storage, network, and data ingestion designs. Domain 4 includes cost-optimized storage and network choices.

When these domains combine, the question usually sounds like:

move or connect the workload without breaking availability, performance, privacy, downtime, or cost constraints

That is why DataSync, Storage Gateway, DMS, Snow Family, Direct Connect, VPN, Transit Gateway, PrivateLink, and migration planning often appear together.

3. What AWS Is Testing

Classify the workload before you classify the AWS service.

For data type, decide whether the scenario describes object storage, file storage, block storage, database records, server images, streaming data, or application traffic.

For movement pattern, decide whether this is one-time transfer, recurring sync, online replication, offline bulk transfer, hybrid access, or final cutover.

For network path, decide whether the answer needs internet VPN, dedicated private connectivity, VPC-to-VPC routing, service-specific private access, or physical device transfer.

Then consider operational constraints: downtime, bandwidth, encryption, compliance, source compatibility, rollback, and who owns the target account.

4. Service And Concept Clusters

Use these clusters while drilling:

• File and object movement: AWS DataSync, AWS Transfer Family, AWS Snow Family
• Hybrid storage: AWS Storage Gateway, Amazon EFS, Amazon FSx
• Database migration: AWS Database Migration Service, Amazon RDS, Amazon Aurora
• Application migration: AWS Application Migration Service, AWS Migration Hub
• Hybrid networking: AWS Direct Connect, AWS Site-to-Site VPN, AWS Transit Gateway
• Private connectivity: Transit Gateway vs VPC Peering vs PrivateLink, VPC Endpoints And PrivateLink

5. Architecture Reasoning Patterns

Use the drills below to practice this migration trace:

source -> data type -> change rate -> connection -> target service -> cutover and rollback

Drill 1: Recurring File Copy To S3

Scenario: A company has an on-premises file share with daily generated files. It wants to move new and changed files to S3 on a schedule for analytics. The network link is sufficient, and users do not need low-latency file access from AWS back to on premises.

Best answer: use AWS DataSync to move files from the on-premises file system to S3 with scheduled or recurring transfers.

Why: DataSync is a managed data transfer service for moving file and object data between on-premises storage, AWS storage, and other supported locations. The key clues are recurring transfer, file data, and S3 target.

Distractors:

• Storage Gateway is better when workloads need hybrid access patterns such as cached file access or backup-style integration.
• DMS is for database migration, not file shares.
• Snow Family is stronger when bandwidth is insufficient for large offline transfer.
• Site-to-Site VPN provides connectivity but does not perform the file synchronization.

Drill 2: Hybrid File Access During Gradual Migration

Scenario: An office application still expects SMB file shares. The company wants cloud-backed storage while local users continue to access recently used files with low latency during a gradual migration.

Best answer: evaluate AWS Storage Gateway File Gateway or Amazon FSx options depending on protocol and application requirements.

Why: this is not just "copy files once." It is a hybrid access requirement. The local application still needs a file interface, while AWS-backed storage provides durability and integration.

Distractors:

• DataSync can move data but does not provide a persistent local file access interface.
• DMS does not apply to file shares.
• S3 alone is object storage and may not satisfy SMB/NFS application expectations without a gateway or file service layer.
• A database read replica has no relationship to file protocol compatibility.

Drill 3: Database Migration With Minimal Downtime

Scenario: A company wants to move an on-premises relational database to Amazon RDS. The database changes constantly, and the business wants minimal downtime during cutover.

Best answer: use AWS DMS for ongoing replication to the target database, and use schema conversion tooling when source and target engines differ.

Why: DMS fits database movement and ongoing replication. If the migration is heterogeneous, schema and code compatibility become a separate concern.

Distractors:

• DataSync moves files, not live database changes at the row/transaction level.
• Snow Family can move large exports but does not solve continuous database replication by itself.
• Read replicas are database-engine-specific and do not handle generic on-premises-to-RDS migration.
• Backup restore may be simpler but usually increases downtime.

Drill 4: Too Much Data For The Network

Scenario: A media archive is hundreds of terabytes, the migration window is short, and the existing internet connection cannot transfer the data in time.

Best answer: use AWS Snow Family for offline or edge-assisted bulk transfer, then use online sync for deltas if needed.

Why: physical transfer becomes relevant when bandwidth and time make network transfer impractical. The clue is not simply "large data." It is large data plus insufficient network capacity for the deadline.

Distractors:

• Direct Connect may help recurring private bandwidth, but provisioning and cost may not fit a one-time urgent transfer.
• DataSync over an inadequate link still faces the bandwidth limit.
• S3 Transfer Acceleration can help internet upload paths, but it does not remove the basic transfer-time constraint for very large datasets.
• Increasing EC2 size does not move on-premises data faster.

Drill 5: Hybrid Connectivity For Production Traffic

Scenario: A production application in AWS must call services in a data center. The company wants private, consistent network performance and plans to keep this hybrid pattern long term.

Best answer: consider AWS Direct Connect for dedicated private connectivity, often with Site-to-Site VPN as backup. Use Transit Gateway when many VPCs and on-premises networks need hub-style connectivity.

Why: the key clues are long-term hybrid traffic and predictable private connectivity. VPN can be faster to set up and can be enough for many cases, but Direct Connect is the stronger answer when consistent dedicated connectivity is explicit.

Distractors:

• VPC peering connects VPCs, not an on-premises data center by itself.
• PrivateLink exposes services privately but does not create general network routing.
• NAT Gateway is outbound internet egress, not private hybrid connectivity.
• CloudFront accelerates public content delivery, not private data center integration.

6. High-Yield Comparisons

DataSync versus Storage Gateway: DataSync moves data; Storage Gateway supports hybrid access and integration patterns.

DMS versus DataSync: DMS moves database changes; DataSync moves file and object data.

Snow Family versus network transfer: Snow Family fits when bandwidth and time make online transfer impractical.

VPN versus Direct Connect: VPN is internet-based encrypted connectivity; Direct Connect provides dedicated private connectivity for consistent long-term patterns.

Transit Gateway versus VPC peering: Transit Gateway fits hub-style many-network connectivity; peering is simpler point-to-point VPC routing.

PrivateLink versus Transit Gateway: PrivateLink exposes a service privately; Transit Gateway routes networks.

Migration Hub versus migration service: Migration Hub tracks migration progress; it is not the tool that copies files, replicates databases, or migrates servers.

7. Scenario Triggers

Use this checklist when data, network, and migration appear together:

• Recurring file transfer to S3: DataSync.
• Hybrid local file access backed by AWS: Storage Gateway or managed file service pattern.
• Database migration with low downtime: DMS, plus schema conversion when heterogeneous.
• Massive transfer with inadequate bandwidth: Snow Family.
• Lift-and-shift servers: Application Migration Service.
• Track migration waves: Migration Hub.
• Dedicated long-term hybrid connectivity: Direct Connect, often backed by VPN.
• Many VPCs and on-prem networks: Transit Gateway.
• Service-specific private producer/consumer access: PrivateLink.

8. Common Traps

Do not choose DMS for file shares.

Do not choose DataSync when the requirement is persistent local file access.

Do not choose Snow Family just because data is large; choose it when the network cannot meet the deadline.

Do not choose Direct Connect for an urgent setup if the scenario values speed of deployment more than dedicated connectivity.

Do not use VPC peering as a general replacement for hybrid connectivity.

Do not use PrivateLink when the requirement is full network routing.

Do not ignore schema conversion when the source and target database engines differ.

Do not forget cutover, rollback, and delta sync after the initial transfer.

9. Study Path

Study in this order:

1. On-Premises Migration To AWS
2. Hybrid Network Connectivity To AWS
3. AWS DataSync
4. AWS Storage Gateway
5. AWS Database Migration Service
6. AWS Snow Family
7. Transit Gateway vs VPC Peering vs PrivateLink

10. Related Topics

Review On-Premises Migration To AWS, Hybrid Network Connectivity To AWS, DataSync, Transfer Family, and Snow Family, and Transit Gateway vs VPC Peering vs PrivateLink.

Official AWS references:

• SAA-C03 exam guide
• Content Domain 2: Design Resilient Architectures
• Content Domain 3: Design High-Performing Architectures
• Content Domain 4: Design Cost-Optimized Architectures
• AWS Well-Architected Framework