Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5
SOA-C02 Monitoring, Logging, and Remediation Practice Question
Drag and drop the steps to migrate an on-premises application to AWS using AWS Application Migration Service (MGN) into the correct order.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Install the agent, then configure replication, then sync, then test, then cut over.
The correct sequence for migrating an on-premises application to AWS using AWS Application Migration Service is: first install the AWS Replication Agent on the source server, then configure the replication settings including launch settings and target VPC, then start the initial sync to replicate the entire server volume, then perform a test launch to validate the replicated environment, and finally initiate the cutover to redirect production traffic to the new AWS instance. Each step builds on the previous one to ensure a successful migration with minimal downtime.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Install the agent, then configure replication, then sync, then test, then cut over.
Why this is correct
This is the correct order because the agent must be installed first to enable data replication, then replication settings must be configured before the initial sync, which is followed by testing to verify the replicated environment, and finally cut over to redirect traffic to the new AWS infrastructure.
- ✗
Install the agent, then sync, then configure replication, then test, then cut over.
Why it's wrong here
Installing the agent first is correct, but attempting to sync before configuring replication is invalid because replication settings define the staging area, target AWS account, and launch parameters for the migration. Without these settings configured, there is no replication job or destination to perform the initial sync against, so the sync cannot execute. The initial sync is a consequence of the replication configuration, not an independent step that can precede it.
- ✗
Configure replication, then install the agent, then sync, then test, then cut over.
Why it's wrong here
Configuring replication before installing the agent is impossible in AWS Application Migration Service because the agent on the source server is what discovers local volumes and streams data to the staging area. Replication settings are meaningless without an active agent providing the source data, and the service cannot establish a replication channel to a server that has no agent installed. Therefore, agent installation must always precede replication configuration, making this sequence invalid.
- ✗
Install the agent, then configure replication, then test, then sync, then cut over.
Why it's wrong here
This is incorrect because testing should occur after synchronization to ensure that the fully synced data is consistent and the application behaves correctly in the AWS environment. Testing before sync would verify an incomplete or outdated copy.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SOA-C02 question from scratch — 247 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SOA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SOA-C02 exam.