CLF-C02 Cloud Technology and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create a replication instance, then create source and target endpoints, then test endpoint connectivity, then create a database migration task, then start the migration task.

  Why this is correct

  This is the correct order because the replication instance must exist before endpoints can be associated, endpoints must be created before testing, testing must succeed before creating a task, and the task must be created before it can be started.

• ✗

  Create source and target endpoints, then create a replication instance, then test endpoint connectivity, then create a database migration task, then start the migration task.

  Why it's wrong here

  In AWS DMS, the replication instance is the compute engine that performs the actual data movement and is also used to validate connectivity to any endpoint. Creating source and target endpoints first is problematic because endpoint tests cannot run without a replication instance, and associating endpoints with an instance later adds an unnecessary step. Best practice is to provision the replication instance first, then create endpoints so they can be tested and used by the migration task immediately.

• ✗

  Create a replication instance, then create source and target endpoints, then create a database migration task, then test endpoint connectivity, then start the migration task.

  Why it's wrong here

  Testing endpoint connectivity must happen before you create the database migration task, not after, because the test validates the network path, firewall rules, and database credentials that the task will rely on. A task created before connectivity is verified may start and immediately fail with connection timeouts or authentication errors, and AWS DMS logs those errors at the task level. By testing first, you isolate configuration issues before the task is defined, avoiding repeated failed runs.

• ✗

  Create a replication instance, then test endpoint connectivity, then create source and target endpoints, then create a database migration task, then start the migration task.

  Why it's wrong here

  Endpoint connectivity tests are run by the AWS DMS replication instance against a specific endpoint's connection attributes, so the endpoints must exist before any test can be attempted. In this reversed order, the test has no source or target endpoint to reference and cannot resolve connection details, making the entire step impossible to execute. The correct sequence creates endpoints first, then tests them, then creates the task.

Go deeper

Related to this question