- A
Use AWS Schema Conversion Tool (SCT) to convert the schema and then load data with DMS.
Why wrong: SCT is not needed for MongoDB to DocumentDB migration; DocumentDB uses the same API.
- B
Use AWS DMS with 'create indexes before data load' option enabled.
Why wrong: Creating indexes before load slows down migration because indexes are updated during data load.
- C
Use AWS Database Migration Service (DMS) with the 'lob' mode set to 'Don't include LOB columns' and create indexes after the full load.
Deferring index creation speeds up data migration; DMS can handle data transfer.
- D
Use mongodump and mongorestore with the --writeConcern option set to 0.
Why wrong: mongodump/mongorestore does not allow deferred index creation; indexes are created during restore.
Question 1,107 of 1,730
DBS-C01 Deployment and Migration Practice Question
This DBS-C01 practice question tests your understanding of deployment and migration. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is migrating a self-hosted MongoDB database to Amazon DocumentDB. They need to ensure that indexes are created after the data load to improve migration performance. Which migration strategy should they use?
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
✓
Use AWS Database Migration Service (DMS) with the 'lob' mode set to 'Don't include LOB columns' and create indexes after the full load.
Option C is correct because AWS DMS can be configured to skip LOB columns during the full load, which significantly improves migration performance by reducing data transfer overhead. After the full load completes, indexes can be created on the target DocumentDB database, avoiding the performance penalty of maintaining indexes during the bulk data ingestion. This approach aligns with the requirement to defer index creation until after the data load.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use AWS Schema Conversion Tool (SCT) to convert the schema and then load data with DMS.
Why it's wrong here
SCT is not needed for MongoDB to DocumentDB migration; DocumentDB uses the same API.
- ✗
Use AWS DMS with 'create indexes before data load' option enabled.
Why it's wrong here
Creating indexes before load slows down migration because indexes are updated during data load.
- ✓
Use AWS Database Migration Service (DMS) with the 'lob' mode set to 'Don't include LOB columns' and create indexes after the full load.
Why this is correct
Deferring index creation speeds up data migration; DMS can handle data transfer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use mongodump and mongorestore with the --writeConcern option set to 0.
Why it's wrong here
mongodump/mongorestore does not allow deferred index creation; indexes are created during restore.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume DMS has a built-in option to defer index creation (like some relational database migration tools), but DMS for DocumentDB requires manually configuring LOB handling and creating indexes post-load, and they might confuse the 'create indexes before data load' misconception with a real DMS feature.
Detailed technical explanation
How to think about this question
When migrating to DocumentDB, DMS uses a full-load phase followed by ongoing replication. By setting 'lob' mode to 'Don't include LOB columns', DMS avoids transferring large objects during the initial load, which reduces network I/O and speeds up the process. Indexes should be created after the full load because DocumentDB (like MongoDB) must update indexes on every insert, causing significant write amplification; deferring index creation allows the bulk insert to proceed without this overhead, and indexes can be built efficiently in a single pass afterward.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Deployment and Migration — study guide chapter
Learn the concepts, then practise the questions
- →
Deployment and Migration practice questions
Targeted practice on this topic area only
- →
All DBS-C01 questions
1,730 questions across all exam domains
- →
AWS Certified Database Specialty DBS-C01 study guide
Full concept coverage aligned to exam objectives
- →
DBS-C01 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DBS-C01 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Workload-Specific Database Design practice questions
Practise DBS-C01 questions linked to Workload-Specific Database Design.
Deployment and Migration practice questions
Practise DBS-C01 questions linked to Deployment and Migration.
Management and Operations practice questions
Practise DBS-C01 questions linked to Management and Operations.
Monitoring and Troubleshooting practice questions
Practise DBS-C01 questions linked to Monitoring and Troubleshooting.
Database Security practice questions
Practise DBS-C01 questions linked to Database Security.
DBS-C01 fundamentals practice questions
Practise DBS-C01 questions linked to DBS-C01 fundamentals.
DBS-C01 scenario practice questions
Practise DBS-C01 questions linked to DBS-C01 scenario.
DBS-C01 troubleshooting practice questions
Practise DBS-C01 questions linked to DBS-C01 troubleshooting.
Practice this exam
Start a free DBS-C01 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DBS-C01 question test?
Deployment and Migration — This question tests Deployment and Migration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use AWS Database Migration Service (DMS) with the 'lob' mode set to 'Don't include LOB columns' and create indexes after the full load. — Option C is correct because AWS DMS can be configured to skip LOB columns during the full load, which significantly improves migration performance by reducing data transfer overhead. After the full load completes, indexes can be created on the target DocumentDB database, avoiding the performance penalty of maintaining indexes during the bulk data ingestion. This approach aligns with the requirement to defer index creation until after the data load.
What should I do if I get this DBS-C01 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More DBS-C01 practice questions
- A company is deploying a new application on Amazon RDS for PostgreSQL. The security policy requires that all data be enc…
- Match each AWS service to its primary purpose.
- A financial services company runs a production Amazon Aurora MySQL database cluster (1 writer, 2 readers) in us-east-1.…
- A company is designing a database for a global e-commerce platform that requires low-latency reads and writes from multi…
- A security auditor reviews the output of a DynamoDB table description command as shown in the exhibit. Which statement a…
- A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. The database contains sensitive data tha…
Last reviewed: Jul 4, 2026
This DBS-C01 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 DBS-C01 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.