Question 1,319 of 1,730
Deployment and MigrationhardMultiple ChoiceObjective-mapped

Quick Answer

The answer is indexes on nested fields. Amazon DocumentDB allows you to create indexes on specific paths within sub-documents, such as "address.city" or "items.sku", which enables the query engine to perform targeted index scans rather than full collection scans when you run ad-hoc queries on nested fields. This is the correct feature because without such indexes, DocumentDB would have to examine every document in the collection to match nested field conditions, which is inefficient for ad-hoc workloads. On the AWS Certified Database Specialty DBS-C01 exam, this concept tests your understanding of how DocumentDB’s MongoDB-compatible indexing works, and a common trap is assuming that enabling a search index or a text index is required—when in fact, a standard B-tree index on the nested path is sufficient. Remember the memory tip: “Nest the index, not the scan”—if you need to query deep, index the path.

DBS-C01 Deployment and Migration Practice Question

This DBS-C01 practice question tests your understanding of deployment and migration. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 deploying a MongoDB-compatible database using Amazon DocumentDB. The application requires the ability to perform ad-hoc queries on nested fields within documents. Which DocumentDB feature should be enabled to meet this requirement?

Question 1hardmultiple choice
Read the full NAT/PAT explanation →

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

Indexes on nested fields

Amazon DocumentDB supports indexing on nested fields, which allows efficient querying of sub-documents and arrays within documents. By creating indexes on specific nested paths (e.g., "address.city"), the query engine can perform index scans instead of full collection scans, enabling fast ad-hoc queries on nested fields. This feature directly meets the requirement for ad-hoc queries on nested fields.

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.

  • TTL indexes

    Why it's wrong here

    TTL indexes automatically delete documents after a period.

  • Indexes on nested fields

    Why this is correct

    Indexes allow efficient ad-hoc queries on nested fields.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Transactions

    Why it's wrong here

    Transactions provide ACID guarantees, not query optimization.

  • Change streams

    Why it's wrong here

    Change streams capture changes, not query optimization.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may confuse indexing features with operational features like TTL or Change streams, assuming any advanced DocumentDB feature can support nested queries, when only explicit indexing on nested fields enables efficient ad-hoc querying on sub-documents.

Detailed technical explanation

How to think about this question

When creating an index on a nested field in DocumentDB, the index key uses dot notation (e.g., db.collection.createIndex({"address.zip": 1})), which stores B-tree entries for the specific sub-field. This allows the query planner to use index intersection or index-only scans for queries like db.collection.find({"address.zip": "12345"}), significantly reducing I/O compared to scanning entire documents. A real-world scenario is an e-commerce application that needs to filter orders by nested shipping address fields without retrieving all documents.

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.

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.

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: Indexes on nested fields — Amazon DocumentDB supports indexing on nested fields, which allows efficient querying of sub-documents and arrays within documents. By creating indexes on specific nested paths (e.g., "address.city"), the query engine can perform index scans instead of full collection scans, enabling fast ad-hoc queries on nested fields. This feature directly meets the requirement for ad-hoc queries on nested fields.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

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.