Right after a release, DynamoDB consumed write capacity roughly doubles at the same citizen traffic level. What should the team do with metrics?
Select an answer to reveal the explanation.
Short Explanation
Same citizen traffic, twice the write burn right after ship? Diff the CloudWatch write metrics across the deploy—odds are an N+1 write bug rode in with the release.
Full Explanation
Comparing CloudWatch consumed write capacity before and after a deploy at similar traffic isolates release-driven regressions such as N+1 writes. Attribution to the change set guides rollback or a hotfix. Marketing notes, assuming AWS silently doubled capacity, or disabling tracing do not explain or fix the metric jump.