SAP-C03 · Domain 4: Resilience, Migration, and Business Continuity · 15% of the exam
Task 4.1: Design migration strategies by using AWS frameworks.
Moving an estate: discovery and wave planning, rehosting with AWS Transform MGN and AWS Transform, database and data migration, replatforming onto managed services, refactoring with patterns such as the strangler fig, and modernizing mainframes, legacy applications and databases.
Study it
Portfolio assessment, the seven migration strategies and wave planning
Try each one before opening the answer. Every option is explained, with the AWS documentation page that proves it.
Question 1 · choose 1
A company is starting its first large migration: about 1,500 VMware virtual machines in two data centers. It needs an inventory of the servers, a map of the dependencies between them, and migration waves that keep dependent servers together. The company has not used any AWS migration service before. Which AWS service should it use for discovery and wave planning?
AAWS Transform, using its discovery, dependency analysis and wave planning capabilities
BAWS Config with an aggregator for all accounts, recording the virtual machines as configuration items
CAWS Compute Optimizer, opting in the data center hosts to receive sizing recommendations
DAWS Trusted Advisor, with its checks extended to the on-premises environment
Show the answer and why
AAWS Transform, using its discovery, dependency analysis and wave planning capabilities
Correct
AWS Transform collects and analyzes on-premises server inventory, groups applications, identifies dependencies and builds prioritized migration waves.
BAWS Config with an aggregator for all accounts, recording the virtual machines as configuration items
Incorrect
AWS Config records the configuration of AWS resources. It does not discover virtual machines in a data center or plan migration waves.
CAWS Compute Optimizer, opting in the data center hosts to receive sizing recommendations
Incorrect
Compute Optimizer analyzes AWS resources that already run in AWS accounts. It cannot inventory on-premises servers.
DAWS Trusted Advisor, with its checks extended to the on-premises environment
Incorrect
Trusted Advisor inspects an AWS environment against best practices. It has no discovery or wave planning for on-premises servers.
Discovery, dependency mapping and wave planning for a new migration are capabilities of AWS Transform, which AWS now recommends in place of AWS Migration Hub and AWS Application Discovery Service, both of which no longer accept new customers.
Before approving a migration budget, the CFO wants a data-driven business case that compares the current on-premises cost of 900 servers with the projected cost on AWS, based on the servers' real utilization, and that compares bringing existing Windows and SQL Server licenses with using license-included instances. Which approach meets this requirement?
AEnter each server's current size into the AWS Pricing Calculator and total the monthly estimates
BRequest an assessment with Migration Evaluator and collect utilization data with its agentless collector
CUse AWS Cost Explorer forecasting on a pilot account to project the cost of the whole server estate
DCreate AWS Budgets for the target accounts and compare those budgets with the current data center costs
Show the answer and why
AEnter each server's current size into the AWS Pricing Calculator and total the monthly estimates
Incorrect
The Pricing Calculator estimates the cost of AWS services that you describe. Typing in today's sizes ignores actual utilization and does not collect data from the servers.
BRequest an assessment with Migration Evaluator and collect utilization data with its agentless collector
Correct
Migration Evaluator builds a data-driven business case from discovered on-premises usage, recommends cost-effective AWS alternatives and compares bring-your-own-license with license-included options.
CUse AWS Cost Explorer forecasting on a pilot account to project the cost of the whole server estate
Incorrect
Cost Explorer forecasts from spend that already happens on AWS. A pilot account says little about 900 servers that have not moved.
DCreate AWS Budgets for the target accounts and compare those budgets with the current data center costs
Incorrect
Budgets track spend against a limit that you set. They do not estimate what the servers would cost on AWS.
A TCO business case built on real utilization and licensing options is what Migration Evaluator produces.
A company is planning migration waves for 600 servers. Its order system runs on 12 servers that share one database cluster with the billing system, which runs on 8 other servers. The two systems must keep low latency to the shared database during and after the migration. How should the wave plan treat these servers?
AMove the order system in the first wave and the billing system in a later wave so that each wave stays small
BOrder the waves by server operating system so that each wave uses one migration runbook
CPut the order servers, the billing servers and the database cluster in the same move group and wave
DMove the database cluster first and leave both systems on premises until the last wave
Show the answer and why
AMove the order system in the first wave and the billing system in a later wave so that each wave stays small
Incorrect
Splitting systems that share a database leaves one of them talking to the database across the hybrid link between waves, which breaks the latency requirement.
BOrder the waves by server operating system so that each wave uses one migration runbook
Incorrect
Grouping by operating system ignores the shared database dependency that AWS guidance asks wave planning to account for.
CPut the order servers, the billing servers and the database cluster in the same move group and wave
Correct
Wave planning groups applications by their infrastructure and application dependencies, such as a shared database, so that servers that must stay together move together.
DMove the database cluster first and leave both systems on premises until the last wave
Incorrect
Both systems would then reach the database across the hybrid link for most of the migration, which again breaks the latency requirement.
Dependencies decide move groups: servers that share a database and need low latency to it migrate in the same wave.
A company will move a 20 TB Oracle database to Amazon Aurora PostgreSQL. The database takes orders around the clock, and the business allows at most 30 minutes of downtime for the cutover. The schema includes PL/SQL procedures that must be converted. Which migration approach meets these requirements?
ACreate an Aurora PostgreSQL read replica of the Oracle database and promote it to a standalone cluster at cutover
BCopy the Oracle data files to Amazon S3 with AWS DataSync and attach the copied files to the new Aurora cluster
CRun an AWS DMS full-load task only, during the cutover window, after converting the schema
DConvert the schema with DMS Schema Conversion or AWS SCT, then run a DMS full load with change data capture
Show the answer and why
ACreate an Aurora PostgreSQL read replica of the Oracle database and promote it to a standalone cluster at cutover
Incorrect
Aurora PostgreSQL read replicas can be created from RDS for PostgreSQL DB instances. For a database that is not PostgreSQL-compatible, AWS points to AWS DMS.
BCopy the Oracle data files to Amazon S3 with AWS DataSync and attach the copied files to the new Aurora cluster
Incorrect
DataSync moves files and objects. Aurora PostgreSQL cannot use Oracle data files, and the engines differ.
CRun an AWS DMS full-load task only, during the cutover window, after converting the schema
Incorrect
A full load of 20 TB takes far longer than 30 minutes, and without ongoing replication every change made during the load is lost.
DConvert the schema with DMS Schema Conversion or AWS SCT, then run a DMS full load with change data capture
Correct
Schema conversion translates the Oracle schema and code objects to PostgreSQL, and a DMS task with full load plus ongoing replication keeps the target in sync, so cutover needs only a short pause.
Heterogeneous and near-zero downtime: convert the schema first, then full load plus change data capture with AWS DMS.
A company must move 500 TB from an on-premises NFS file server to Amazon S3 within four weeks. Its 10 Gbps AWS Direct Connect connection is mostly idle. Users keep changing files until cutover, so the copy must be refreshed incrementally, with the transfers verified and the bandwidth used capped during business hours. Which solution meets these requirements?
ARun an AWS DataSync task from the NFS share to the bucket over Direct Connect on a schedule, with a bandwidth limit
BSet up an AWS Transfer Family SFTP server and have a script upload the changed files to it over SFTP every night
CUpload the files with S3 Transfer Acceleration from a server in the data center, repeating the upload for changed files
DMount the NFS share on an EC2 instance through a VPN and copy it with a scheduled cp command
Show the answer and why
ARun an AWS DataSync task from the NFS share to the bucket over Direct Connect on a schedule, with a bandwidth limit
Correct
DataSync copies from NFS to S3, can transfer only the data that changed on later runs, includes data integrity validation, and lets you limit the bandwidth that a task uses.
BSet up an AWS Transfer Family SFTP server and have a script upload the changed files to it over SFTP every night
Incorrect
Transfer Family serves SFTP users. A custom upload script would have to handle change detection, verification and throttling itself.
CUpload the files with S3 Transfer Acceleration from a server in the data center, repeating the upload for changed files
Incorrect
Transfer Acceleration speeds up uploads over the internet through edge locations. It does not use the idle Direct Connect link or detect changed files.
DMount the NFS share on an EC2 instance through a VPN and copy it with a scheduled cp command
Incorrect
A copy command has no built-in incremental transfer, verification or bandwidth limit, and a VPN adds a slower path when Direct Connect is available.
Large online file transfers with incremental runs, verification and throttling are what DataSync does over an existing private link.
A company will rehost 120 Linux and Windows servers from VMware to Amazon EC2. The applications must not change, each cutover window is at most one hour, and the team wants to test launched instances before each cutover. Which service meets these requirements?
AAWS DMS, migrating the databases on each server and then recreating the rest of each server on EC2 by hand
BVM Import/Export, exporting each virtual machine and importing it as an AMI during its window
CAWS Transform MGN, replicating the servers continuously and launching test instances before cutover
DAWS DataSync, copying each server's disks to Amazon S3 and launching instances from them
Show the answer and why
AAWS DMS, migrating the databases on each server and then recreating the rest of each server on EC2 by hand
Incorrect
AWS DMS migrates databases, not whole servers, so the rest of each server would have to be rebuilt manually.
BVM Import/Export, exporting each virtual machine and importing it as an AMI during its window
Incorrect
Importing images is a one-time copy, so every change made after the export is lost or the server must be stopped for the whole import, which is hard to fit into one hour.
CAWS Transform MGN, replicating the servers continuously and launching test instances before cutover
Correct
MGN replicates source servers continuously at block level, converts them to run on AWS, supports test launches and gives cutover windows typically measured in minutes.
DAWS DataSync, copying each server's disks to Amazon S3 and launching instances from them
Incorrect
DataSync transfers files and objects. It does not turn server disks into bootable EC2 instances.
Rehosting many servers with short cutovers and test launches is the job of AWS Transform MGN, formerly AWS Application Migration Service.
After a rehost, a monolith on EC2 still runs a nightly cron job that builds reports, resizes every uploaded image inside the web request, and handles a five-step order fulfillment process in one long-running thread that loses progress on restarts. The company wants to modernize these three parts without managing servers. Which changes should it make? (Choose THREE.)
ARun the report job as a Lambda function or ECS task started by an Amazon EventBridge Scheduler schedule
BMove the monolith to a larger EC2 instance so that the cron job and image work finish faster
CResize images in a Lambda function invoked by Amazon S3 event notifications when an upload lands in the bucket
DKeep the fulfillment thread but restart the instance every night so that progress is never lost
ERun the cron job on an EC2 instance in an Auto Scaling group with a minimum and maximum of one
FModel the fulfillment process as an AWS Step Functions state machine with retries for each step
Show the answer and why
ARun the report job as a Lambda function or ECS task started by an Amazon EventBridge Scheduler schedule
Correct
EventBridge Scheduler starts targets such as Lambda functions and ECS tasks on a cron-style schedule, so no server has to run cron.
BMove the monolith to a larger EC2 instance so that the cron job and image work finish faster
Incorrect
A larger instance still keeps all three jobs inside the server that the company wants to stop managing.
CResize images in a Lambda function invoked by Amazon S3 event notifications when an upload lands in the bucket
Correct
S3 event notifications can invoke a Lambda function for each new object, which moves image processing out of the web request.
DKeep the fulfillment thread but restart the instance every night so that progress is never lost
Incorrect
Restarting does not save progress; it causes exactly the loss the company wants to avoid.
ERun the cron job on an EC2 instance in an Auto Scaling group with a minimum and maximum of one
Incorrect
An Auto Scaling group of one replaces a failed instance, but the company would still manage a server for a scheduled job.
FModel the fulfillment process as an AWS Step Functions state machine with retries for each step
Correct
Step Functions coordinates multi-step workflows, keeps the state of each execution and retries failed steps, so progress survives failures.
Schedules, events and workflows each have a serverless home: EventBridge Scheduler, S3 events to Lambda, and Step Functions.
A bank's portfolio assessment includes COBOL applications on an IBM z/OS mainframe. Leaders want to modernize them on AWS rather than keep the mainframe, and want AWS tooling to help analyze and transform the code. Which option should the plan evaluate?
ARepurchase a SaaS product for every COBOL application
BRetain the mainframe indefinitely
CRehost the mainframe image to EC2 with AWS Transform MGN
DAWS Transform for mainframe modernization
Show the answer and why
ARepurchase a SaaS product for every COBOL application
Incorrect
Custom banking applications rarely have SaaS equivalents for each one.
BRetain the mainframe indefinitely
Incorrect
Leaders want to move away from the mainframe.
CRehost the mainframe image to EC2 with AWS Transform MGN
Incorrect
Server replication rehosts virtual and bare metal servers; it does not run a z/OS mainframe image on EC2.
DAWS Transform for mainframe modernization
Correct
AWS Transform can modernize and migrate IBM z/OS workloads to AWS.
Mainframe modernization on AWS is evaluated with AWS Transform.
A public website with users worldwide is moving from the company's data center to an Application Load Balancer in AWS. The team wants to send 10% of all users to AWS first, raise the share step by step to 100% over two weeks, and keep the on-premises site, which has public IP addresses and no AWS components, as the fallback. If the AWS endpoint fails its health checks during the rollout, traffic must return to the data center automatically, and no client may need new settings. The domain is hosted in Route 53. Which approach meets these requirements?
ARoute 53 weighted records for the AWS and on-premises endpoints, each with a health check, starting at weights of 10 and 90
BAn AWS Global Accelerator standard accelerator whose endpoint group holds both sites, with endpoint weights moving traffic to AWS
CRoute 53 geolocation records that send one country at a time to AWS until every country has moved
DRoute 53 latency-based records for both sites so that each user reaches whichever site answers faster
Show the answer and why
ARoute 53 weighted records for the AWS and on-premises endpoints, each with a health check, starting at weights of 10 and 90
Correct
Weighted routing sends each resource a share of traffic that matches its relative weight, which suits testing a new version and moving traffic in steps. With health checks on the records, Route 53 stops returning an unhealthy endpoint, so traffic falls back to the other one.
BAn AWS Global Accelerator standard accelerator whose endpoint group holds both sites, with endpoint weights moving traffic to AWS
Incorrect
Endpoint weights can manage how much traffic each endpoint gets, but a standard accelerator's endpoints must be load balancers, EC2 instances or Elastic IP addresses in AWS. The on-premises site cannot be an endpoint, so there is nothing to fall back to.
CRoute 53 geolocation records that send one country at a time to AWS until every country has moved
Incorrect
Geolocation routing chooses resources by the users' location, so it moves whole countries, not a controlled 10% share of all users worldwide.
DRoute 53 latency-based records for both sites so that each user reaches whichever site answers faster
Incorrect
Latency-based routing serves users from the AWS Region with the lowest latency, based on traffic between users and AWS data centers. It gives no control over the share of users, and latency to a non-AWS site is not measured.
The constraints are a controlled percentage of all users, an on-premises fallback with no AWS components, automatic return on failure and no client changes. Global Accelerator cannot use the data center as an endpoint, and geolocation and latency routing do not control percentages. Weighted records with health checks meet all of them through DNS.