The correct answer is to use the MySQL 8.0 native JSON data type with JSON path expressions. This is because the native JSON type stores documents in an optimized binary format, allowing direct SQL access to fields via functions like JSON_EXTRACT, the -> operator, or the ->> operator, which eliminates the need for application-level parsing and dramatically improves query performance. On the AWS Certified Database Specialty DBS-C01 exam, this scenario tests your understanding of how to optimize semi-structured data in RDS MySQL without moving to a NoSQL service—a common trap is assuming you must use a separate document database or parse JSON in the application layer. Remember that MySQL 8.0’s generated columns can create virtual indexes on JSON fields, making frequent field queries as fast as querying regular columns. A quick memory tip: think “JSON path, not app parse” to recall that native JSON with path expressions is the optimized, exam-approved approach.
DBS-C01 Workload-Specific Database Design Practice Question
This DBS-C01 practice question tests your understanding of workload-specific database design. 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 running a MySQL database on Amazon RDS and needs to store JSON documents that are frequently queried by fields within the JSON. The company wants to reduce development complexity and improve query performance. Which RDS MySQL feature should the database specialist recommend?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the JSON data type in MySQL 8.0 and utilize JSON path expressions in queries
Option B is correct because MySQL 8.0's native JSON data type stores JSON documents in an optimized binary format, enabling efficient indexing and querying via JSON path expressions (e.g., `JSON_EXTRACT`, `->`, `->>`). This reduces development complexity by allowing direct SQL access to JSON fields without application-level parsing, and improves query performance through generated columns and virtual indexes.
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.
✗
Migrate the JSON data to Amazon DynamoDB and use DynamoDB's document model
Why it's wrong here
Migrating to DynamoDB would require application changes and may not be necessary if the data can be handled within RDS.
✓
Use the JSON data type in MySQL 8.0 and utilize JSON path expressions in queries
Why this is correct
MySQL's JSON data type allows efficient storage and querying using JSON path expressions and indexes.
Related concept
Read the scenario before looking for a memorised answer.
✗
Store JSON documents in a VARCHAR(MAX) column and use LIKE operations for queries
Why it's wrong here
LIKE operations on VARCHAR columns are inefficient and do not support JSON path queries.
✗
Store JSON documents as BLOBs and parse them in application code
Why it's wrong here
This approach puts parsing burden on the application and prevents database-level optimization.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume DynamoDB (Option A) is the only way to handle JSON efficiently, overlooking MySQL 8.0's native JSON support which avoids cross-service complexity while providing comparable query capabilities.
Detailed technical explanation
How to think about this question
MySQL 8.0's JSON data type internally stores documents in a binary format (BSON-like) that allows fast key-value lookups without reparsing the entire document. You can create generated columns on JSON fields and index them with secondary indexes, enabling queries like `SELECT * FROM t WHERE JSON_EXTRACT(doc, '$.field') = 'value'` to use index range scans. This approach is particularly beneficial for read-heavy workloads with frequent partial document updates, as MySQL supports partial JSON updates via `JSON_SET` without rewriting the entire column.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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.
Workload-Specific Database Design — This question tests Workload-Specific Database Design — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the JSON data type in MySQL 8.0 and utilize JSON path expressions in queries — Option B is correct because MySQL 8.0's native JSON data type stores JSON documents in an optimized binary format, enabling efficient indexing and querying via JSON path expressions (e.g., `JSON_EXTRACT`, `->`, `->>`). This reduces development complexity by allowing direct SQL access to JSON fields without application-level parsing, and improves query performance through generated columns and virtual indexes.
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 →
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.
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.