mediummulti selectObjective-mapped

A multi-tenant event system writes and reads data in DynamoDB. One tenant generates most of the traffic, causing throttling on a single partition key value, and the dashboards repeatedly read the most recent items for that tenant. Which two changes should the team make to improve performance? Select two.

Question 1mediummulti select
Full question →

A multi-tenant event system writes and reads data in DynamoDB. One tenant generates most of the traffic, causing throttling on a single partition key value, and the dashboards repeatedly read the most recent items for that tenant. Which two changes should the team make to improve performance? Select two.

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Shard the hot tenant’s writes across multiple partition key values so traffic is spread across partitions.

Write sharding reduces pressure on a single partition and is the standard fix for a hot key caused by one tenant.

B

Best answer

Use Amazon DAX to cache repetitive read requests for the same items with sub-millisecond latency.

DAX accelerates repeated reads and reduces pressure on DynamoDB when dashboards request the same recent data repeatedly.

C

Distractor review

Switch the table to on-demand capacity mode so DynamoDB automatically removes partition limits.

On-demand mode simplifies capacity management, but it does not remove the physical partition throughput limits of a hot key.

D

Distractor review

Use a larger sort key attribute to increase the maximum write throughput for the tenant.

Sort key size does not change partition-level throughput, so it does not solve the hot partition bottleneck.

E

Distractor review

Move the table to a single larger provisioned throughput setting and keep the same key design.

Raising table capacity without changing the access pattern still leaves one partition overloaded by the same tenant key.

Common exam trap

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.

Technical deep dive

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.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Shard the hot tenant’s writes across multiple partition key values so traffic is spread across partitions. — The core problem is a hot partition created by one tenant, so the write pattern must be spread across multiple partition key values. That is why write sharding is the first fix. Because the dashboards repeatedly read the same recent data, DAX is also helpful: it serves frequent read traffic from cache and reduces repeated load on DynamoDB. Together, these changes address both the write hotspot and the repetitive read workload. On-demand capacity and larger provisioned settings can help with overall capacity planning, but they do not eliminate the partition-level hotspot created by a single key. Changing the sort key does not redistribute traffic. The scenario specifically shows both a hot write path and repeated reads, so sharding and read caching are the most effective combination.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.