Which solution meets these requirements?
Create an AWS Database Migration Service (AWS DMS) replication instance, a source endpoint for MongoDB, and a target endpoint of Amazon DocumentDB (with MongoDB compatibility).
Create an AWS Database Migration Service (AWS DMS) replication instance, a source endpoint for MongoDB, and a target endpoint of a MongoDB image that is hosted on Amazon EC2
Use the mongodump and mongorestore tools to migrate the data from the source MongoDB deployment to Amazon DocumentDB (with MongoDB compatibility).
Use the mongodump and mongorestore tools to migrate the data from the source MongoDB deployment to a MongoDB image that is hosted on Amazon EC2.
Explanations:
AWS DMS supports continuous data replication, which allows for minimal downtime during migration. Amazon DocumentDB is fully managed, scalable, and compatible with MongoDB, making it a suitable target for the migration.
Migrating MongoDB to a MongoDB instance on EC2 does not provide a fully managed solution. Also, setting up EC2 requires more management and configuration, which doesn’t meet the requirement for a fully managed service.
While mongodump and mongorestore can be used for migration, this method requires more manual intervention and does not support continuous replication. It may result in more downtime compared to AWS DMS, and Amazon DocumentDB is a better solution for a fully managed service.
Similar to option C, using mongodump and mongorestore for migration to a MongoDB instance on EC2 is not fully managed and involves more manual management. It doesn’t meet the requirement for a scalable, fully managed solution.
I infer that the answer is:
Create an AWS Database Migration Service (AWS DMS) replication instance, a source endpoint for MongoDB, and a target endpoint of Amazon DocumentDB (with MongoDB compatibility).