SAP-C02 Continuous Improvement for Existing Solutions Practice Question

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 to DynamoDB On-Demand capacity mode.

  Why it's wrong here

  On-demand mode removes provisioned capacity entirely, so it cannot be configured to increase write capacity during spikes; it simply scales with traffic and costs more per request. The requirement is met by DynamoDB auto scaling, which adjusts provisioned write capacity units in response to consumed capacity.

• ✗

  Implement DynamoDB Accelerator (DAX) for caching.

  Why it's wrong here

  DAX caches read results in front of DynamoDB, so it reduces read latency and read capacity consumption, leaving write throttling untouched. It is tempting because it is the standard DynamoDB performance accelerator, but it would be correct for read-heavy latency problems, not for scaling write capacity.

• ✗

  Use DynamoDB Global Tables to distribute writes.

  Why it's wrong here

  Global Tables replicate writes across Regions for multi-Region active-active access; they do not raise a single table's write capacity ceiling or scale it automatically. It is tempting because replication spreads load geographically, but the throttling is against one table's provisioned write capacity, which needs auto scaling.

• ✓

  Enable DynamoDB Auto Scaling for write capacity.

  Why this is correct

  DynamoDB Auto Scaling adjusts provisioned write capacity in response to CloudWatch-consumed capacity metrics, scaling up during spikes and down afterwards. This automatically raises write throughput when traffic surges, directly addressing the occasional write throttling described in the stem.