A large ecommerce company uses Amazon DynamoDB to handle the transactions on its web portal. Traffic patterns throughout the year are usually stable; however, a large event is planned. The company…

Question

Options

• AEnsure the table is always provisioned to meet peak needs
• BAllow burst capacity to handle the additional load
• CSet an AWS Application Auto Scaling policy for the table to handle the increase in traffic
• DPreprovision additional capacity for the known peaks and then reduce the capacity after the event

• A
  7% (2)
• B
  23% (7)
• C
  13% (4)
• D
  57% (17)

Explanation

Explanation

Option D is correct because the company has advance knowledge of both the timing (3-day event) and magnitude (10x normal load) of the traffic increase, making manual pre-provisioning the most reliable and cost-effective strategy - capacity is scaled up before the event and scaled back down afterward, ensuring predictable performance without wasting money long-term.

Option A is wrong because permanently provisioning for peak load is extremely wasteful and costly during the other 362 days when traffic is at normal levels. Option B is wrong because DynamoDB burst capacity only handles short, unexpected spikes using unused reserved capacity credits - it is not designed to sustain a 10x load for 3 full days. Option C is wrong because while Auto Scaling is a valid general strategy, it reacts to traffic changes rather than proactively preparing for them; during a rapid spike (like when sale prices are published), Auto Scaling may not respond fast enough to prevent throttling.

Memory Tip: Think of it as "planned surgery vs. emergency surgery" - when you know the spike is coming, manually pre-provision (scheduled prep), rather than relying on reactive tools like Auto Scaling or burst capacity, which are better suited for unexpected traffic changes.

No community discussion yet for this question.