The correct answer is to remove unused or redundant indexes and implement batch inserts. Removing unnecessary indexes directly reduces write amplification because each index must be updated on every INSERT, UPDATE, or DELETE, so fewer indexes mean fewer disk writes per row change. Batch inserts reduce per-row overhead by combining multiple rows into a single write operation, which minimizes transaction log flushes and index page splits. On the AWS Certified Database Specialty DBS-C01 exam, this question tests your understanding of InnoDB’s write path and common performance pitfalls—many candidates mistakenly choose to increase instance size or switch storage engines, but those don’t address the root cause of amplification. A key trap is assuming normalization always helps; in fact, it can increase write amplification by adding more tables and indexes. Memory tip: “Drop the dead weight, batch the payload”—remove unused indexes and group your inserts to slash write amplification.
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 runs a MySQL-compatible database on Amazon RDS for a mission-critical application. The database experiences high write latency due to frequent index updates. The team wants to redesign the database to reduce write amplification and improve insert performance. Which TWO design changes could help?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use batch INSERT statements instead of single-row inserts
Option A (removing unused indexes) directly reduces write amplification. Option C (batch inserts) reduces per-row overhead. Option B (increasing instance size) may not address root cause. Option D (changing to InnoDB) is already MySQL's default engine; switching to MyISAM is not recommended. Option E (normalizing) might increase joins but not necessarily reduce write amplification.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Switch the storage engine from InnoDB to MyISAM
Why it's wrong here
MyISAM lacks transaction support and is not recommended for production.
✓
Use batch INSERT statements instead of single-row inserts
Why this is correct
Batch inserts reduce transaction overhead and log I/O.
Related concept
Static NAT maps one inside address to one outside address.
✗
Upgrade to a larger RDS instance class
Why it's wrong here
More CPU/memory may not reduce write amplification caused by index maintenance.
✓
Remove unused or redundant indexes
Why this is correct
Fewer indexes mean less work during writes.
Related concept
Static NAT maps one inside address to one outside address.
✗
Normalize the database schema to reduce data redundancy
Why it's wrong here
Normalization can reduce redundancy but may increase joins; it does not directly reduce write amplification from index updates.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DBS-C01 NAT questions on configuration and troubleshooting.
Workload-Specific Database Design — This question tests Workload-Specific Database Design — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use batch INSERT statements instead of single-row inserts — Option A (removing unused indexes) directly reduces write amplification. Option C (batch inserts) reduces per-row overhead. Option B (increasing instance size) may not address root cause. Option D (changing to InnoDB) is already MySQL's default engine; switching to MyISAM is not recommended. Option E (normalizing) might increase joins but not necessarily reduce write amplification.
What should I do if I get this DBS-C01 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DBS-C01 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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.