SAP-C02 domain - 20% of the exam

Accelerate Workload Migration and Modernization

Accelerate Workload Migration and Modernization is 20% of the SAP-C02 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

52
Practice questions
6
Objectives
18
Medium
34
Hard

Where people go wrong

  • Expecting online transfer services to beat a bandwidth cap

    The wrong answers push the bulk data over the constrained link anyway. S3 Transfer Acceleration, Transfer Family, DataSync for the full 600 TB archive over a 50 Mbps link, and a DMS full load of a forty-terabyte warehouse all send every byte across that connection, so none finishes in the window. Snowball Edge copies the bulk data locally and ships it. The link then carries only the small ongoing changes, through DataSync for changed files or DMS change data capture for a database.

    See it in a sample question
  • Confusing DataSync, Transfer Family and Transfer Acceleration

    The wrong answers swap these three services by name. DataSync is offered to external partners who cannot run its agent and to players uploading over the internet, Transfer Family is offered for incremental sync, and Transfer Acceleration is offered where SFTP clients must be kept. Transfer Family gives partners an SFTP or FTPS endpoint into S3. DataSync syncs storage the owner controls through an agent. Transfer Acceleration speeds long-distance S3 uploads through edge locations.

    See it in a sample question
  • Treating Schema Conversion Tool and DMS as interchangeable

    The wrong answers give one half of a heterogeneous migration to the wrong tool. Database Migration Service is credited with converting PL/SQL packages, triggers and proprietary types, the Schema Conversion Tool is credited with keeping a target current, and DataSync or a native backup is offered in place of either. The Schema Conversion Tool converts the schema and code objects. DMS runs a full load plus change data capture until a brief cutover.

    See it in a sample question
  • Rehosting whole servers with file or database tools

    The wrong answers pick a tool that moves data rather than machines. DMS replicates database tables, DataSync copies files, and VM Import/Export takes a point-in-time image, so none of them gives continuous block-level replication of a running server. Application Migration Service installs an agent, replicates the volumes into a staging area, launches test instances while the source keeps running, then cuts over in a short window.

    See it in a sample question
  • Using migration or config services for discovery

    The wrong answers name services that act on servers or databases instead of discovering them. Application Migration Service replicates for cutover, DMS knows only its own endpoints, the Schema Conversion Tool assesses schemas, and AWS Config records AWS resources rather than on-premises servers. Application Discovery Service collects inventory, utilisation and network connections, and Migration Hub groups servers into applications and tracks migration status.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleAccelerate Workload Migration and Modernizationhard

A media company is closing a remote production studio and must move 600 TB of archived video from an on-premises NAS into Amazon S3. The studio site has a single 50 Mbps internet link that the facilities team needs for daily operations, and the migration must finish within four weeks without saturating that link. The data is then deleted from the NAS. Which transfer mechanism MOST appropriately meets the deadline and the link constraint?

  • ADeploy an AWS DataSync agent on the studio network and schedule transfer tasks during off-hours to push the archive over the existing 50 Mbps internet link into the destination S3 bucket.
  • BEnable Amazon S3 Transfer Acceleration on the destination bucket and use the multipart upload API from the studio so the archive routes over the optimised CloudFront edge path into S3.
  • COrder multiple AWS Snowball Edge devices, copy the archive locally over the studio LAN, and ship them to AWS for ingestion into S3 so the migration never touches the internet link. Correct
  • DSet up AWS Transfer Family with an SFTP endpoint backed by the bucket and have the studio scripts upload the archive to that managed endpoint over the public internet connection.
Choose AWS Snow Family for large one-time bulk migrations when available bandwidth cannot meet the deadline within the constraint. When the data volume divided by the usable link bandwidth exceeds the migration window, an online transfer cannot finish in time regardless of optimisation. 600 TB over a shared 50 Mbps link would take many months, so a physical Snow Family transfer that copies at local network speed and ships the devices is the only option that meets a four-week deadline without consuming the operational link. DataSync, Transfer Acceleration and Transfer Family all remain bounded by the same 50 Mbps origin.

Why A is wrong: DataSync optimises and parallelises transfers, but 600 TB over a 50 Mbps link would take far longer than four weeks and would still compete for the bandwidth facilities relies on.

Why B is wrong: Transfer Acceleration improves long-distance throughput per connection but is still capped by the 50 Mbps origin link, so it cannot deliver 600 TB in four weeks and competes for bandwidth.

Why C is correct: Snowball Edge moves bulk data offline at LAN speed and ships physically, completing a 600 TB transfer within the deadline while leaving the 50 Mbps link untouched for operations.

Why D is wrong: Transfer Family exposes a managed SFTP front door for ongoing exchange, but it still sends bytes over the same constrained 50 Mbps link and adds nothing to bulk migration speed.

Free sampleAccelerate Workload Migration and Modernizationhard

A genomics firm runs an on-premises Lustre cluster and must replicate roughly 8 TB of new research output to Amazon S3 every night across a 10 Gbps AWS Direct Connect link. The pipeline already produces clean files, but the team wants incremental transfers that copy only changed data, verify integrity end to end, and run on a schedule with minimal scripting and operational overhead. Which mechanism BEST satisfies these nightly replication requirements?

  • AStand up an AWS Transfer Family SFTP server fronting the bucket and run a nightly cron job on the cluster that pushes the full 8 TB output set through the managed endpoint to S3.
  • BEnable S3 Transfer Acceleration and script multipart uploads of the nightly output, relying on the accelerated edge path to push the changed files quickly into the destination bucket each night.
  • CSchedule recurring AWS Snowball Edge shipments to capture each night's output locally and send the devices to AWS, ingesting the changed research files into S3 on arrival.
  • DDeploy an AWS DataSync agent next to the cluster and create a scheduled task over the Direct Connect link that transfers only changed files, verifies data integrity and reports task metrics to CloudWatch. Correct
Select AWS DataSync for scheduled incremental transfers with built-in integrity verification when bandwidth supports online replication. DataSync is purpose-built for moving and synchronising file data between on-premises storage and AWS. It detects and transfers only changed files, verifies data integrity end to end with checksums, runs on a schedule and surfaces metrics in CloudWatch, all with a managed agent rather than custom code. With 8 TB nightly fitting easily inside a 10 Gbps Direct Connect link, an online incremental sync is correct, whereas Transfer Family, Transfer Acceleration and Snow Family each miss the incremental, verified, scheduled requirement.

Why A is wrong: Transfer Family is built for partner file exchange over SFTP, not incremental sync, so it would resend full data sets and force the team to build the change detection and verification themselves.

Why B is wrong: Transfer Acceleration only speeds individual uploads and provides no change detection, scheduling or built-in verification, leaving the team to script the incremental logic and integrity checks.

Why C is wrong: Snowball shipments suit one-time bulk moves, but nightly physical shipping cannot meet a daily schedule and is needless when a 10 Gbps Direct Connect link comfortably carries 8 TB online.

Why D is correct: DataSync handles incremental scheduled transfers, performs end-to-end integrity verification and emits task metrics natively, meeting the nightly replication need with minimal custom scripting over Direct Connect.

Free sampleAccelerate Workload Migration and Modernizationhard

A bank is migrating a core application from a self-managed Oracle database on-premises to Amazon Aurora PostgreSQL in a new AWS account. The Oracle schema contains PL/SQL packages, triggers and proprietary data types that must be translated to PostgreSQL, the business will tolerate only a brief cutover, and the team needs ongoing change replication from Oracle so the target stays current until the application is repointed. Which combination of AWS services MOST effectively delivers this heterogeneous migration?

  • AUse the Schema Conversion Tool to convert the schema and PL/SQL to PostgreSQL on Aurora, then use AWS Database Migration Service with full load plus change data capture to move existing rows and replicate ongoing changes until cutover. Correct
  • BUse AWS Application Migration Service to replicate the Oracle database server into EC2, then run the Schema Conversion Tool against that instance and switch the application across after a short verification window once replication has caught up.
  • CUse the Schema Conversion Tool to translate the schema and code to PostgreSQL, then use AWS DataSync to copy the underlying Oracle data files into Amazon S3 and load them into Aurora PostgreSQL during a single short maintenance window.
  • DUse AWS Database Migration Service alone to convert the PL/SQL, triggers and proprietary types automatically and to move the data, relying on its built-in engine translation to land everything directly into Aurora PostgreSQL with continuous replication.
Pair the Schema Conversion Tool with DMS full load plus change data capture for heterogeneous database migration with minimal cutover downtime. Heterogeneous engine changes need two tools: the Schema Conversion Tool converts schema objects and procedural code such as PL/SQL that DMS cannot translate, and DMS then performs a full load followed by change data capture so the Aurora PostgreSQL target stays synchronised with Oracle until the application is repointed in a short cutover.

Why A is correct: The Schema Conversion Tool translates the proprietary schema and PL/SQL to PostgreSQL while Database Migration Service performs a full load and change data capture, keeping Aurora current until a brief cutover, which is the canonical heterogeneous migration pairing.

Why B is wrong: Application Migration Service rehosts a whole server onto EC2 as Oracle rather than converting to Aurora PostgreSQL, so it neither translates the proprietary schema nor lands the data in the managed PostgreSQL engine the bank targets.

Why C is wrong: The Schema Conversion Tool step is right, but DataSync copies files and cannot transform Oracle data into PostgreSQL rows or provide ongoing change capture, so the target would be loaded once and immediately go stale.

Why D is wrong: Database Migration Service maps basic data types during transfer but does not convert PL/SQL packages, triggers or proprietary objects, so without the Schema Conversion Tool the converted schema would be incomplete and the migration would fail.

Free sampleAccelerate Workload Migration and Modernizationhard

A logistics company runs about two hundred Linux and Windows virtual machines in an on-premises VMware estate that it must move into a dedicated migration account in its AWS Organizations. The applications cannot be re-architected before the move, the business mandates a cutover window of only a few minutes per application with near-continuous block-level synchronisation beforehand, and the team wants to keep source servers running until each cutover is verified. Which AWS migration service MOST effectively meets these requirements?

  • AUse AWS Database Migration Service with the Schema Conversion Tool to replicate each server, performing a full load followed by change data capture so that every virtual machine cuts over with only a few minutes of synchronised downtime.
  • BUse AWS DataSync to copy each server's file systems on a recurring schedule into Amazon S3, then build fresh EC2 instances from those files and reinstall the applications before performing a short cutover for every workload.
  • CUse VM Import/Export to convert each virtual machine into an Amazon Machine Image, importing the images one at a time and launching new instances so each application moves across with a short cutover and verified state.
  • DUse AWS Application Migration Service to install replication agents on each source server, continuously replicate the block volumes into a staging area, then launch test and cutover instances during a short window once each application is validated. Correct
Select AWS Application Migration Service for lift-and-shift server rehosting with continuous block replication and a short, verified cutover. Application Migration Service installs agents that continuously replicate source block volumes into a staging subnet, lets you launch non-disruptive test instances, and during cutover converts the latest replicated state into a running EC2 instance within minutes, which is the rehost pattern for whole servers that cannot be re-architected first.

Why A is wrong: Database Migration Service moves database records between engines rather than whole servers, and the Schema Conversion Tool converts schemas, so neither relocates an entire VMware machine image as the rehost requirement demands.

Why B is wrong: DataSync transfers files rather than bootable block volumes, so it cannot deliver continuous block-level synchronisation and a minutes-long cutover, and rebuilding instances and reinstalling applications is rearchitecting the workloads.

Why C is wrong: VM Import/Export creates point-in-time images with no ongoing replication, so the source keeps changing during a slow import and the cutover data is stale, missing the near-continuous synchronisation and short window stated.

Why D is correct: Application Migration Service performs agent-based continuous block-level replication into a low-cost staging area and converts a tested machine into a running EC2 instance during a brief cutover, matching lift-and-shift with minutes of downtime and verifiable test launches.

Free sampleAccelerate Workload Migration and Modernizationhard

A retailer is planning a large data centre exit but lacks an accurate inventory of its on-premises servers and, more importantly, of how the hundreds of applications depend on one another across the network. Before committing to migration waves, the team needs to collect server configuration, performance and inbound and outbound network connection data over time so they can group interdependent systems into move groups. Which AWS capability MOST effectively produces this dependency-aware inventory?

  • AUse AWS Application Migration Service in test mode to launch every source server in AWS and observe which converted instances communicate, building the dependency map from the network traffic seen between the launched test instances.
  • BUse AWS Application Discovery Service with the agent-based collector to gather server configuration, performance and network connection data over time, then analyse the dependencies in Migration Hub to form move groups. Correct
  • CUse the AWS Schema Conversion Tool assessment reports across the database fleet to enumerate the servers and their relationships, exporting the assessment output as the authoritative dependency inventory for planning the migration waves.
  • DUse AWS Database Migration Service to connect to each database endpoint and record the source and target connections it establishes, treating that connection log as the application dependency map used to plan the move groups.
Use AWS Application Discovery Service with Migration Hub to collect performance and network dependency data for planning migration move groups. Application Discovery Service deploys agents or an agentless connector to gather server configuration, time-series utilisation and inbound and outbound network connections, and Migration Hub surfaces those connections as a dependency graph, which is the data needed to cluster interdependent applications into migration waves before rehosting begins.

Why A is wrong: Application Migration Service replicates and launches servers for cutover and is not a discovery tool, and launching everything just to observe traffic is costly and premature before move groups are even defined.

Why B is correct: Application Discovery Service collects configuration, time-series performance and inbound and outbound connection data through agents or the agentless connector, and Migration Hub visualises those dependencies so interdependent systems can be grouped into waves before any migration.

Why C is wrong: The Schema Conversion Tool assesses database schema convertibility, not server inventory or cross-application network dependencies, so its reports cannot map how applications talk to one another across the estate.

Why D is wrong: Database Migration Service replicates database content and only knows its own source and target endpoints, so it cannot discover server inventory or the inbound and outbound network dependencies the retailer needs to plan waves.

Other domains in this exam

See also the SAP-C02 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Amazon Web Services. Original, blueprint-aligned practice material only.