A municipality is choosing databases for two workloads: (1) millions of meter-ID lookups with simple key access, and (2) a permitting app that needs multi-table joins and transactional integrity. Which pairing best matches access patterns?
Select an answer to reveal the explanation.
Short Explanation
Match the filing cabinet to the job: a giant keyed drawer for “look up this meter ID,” and a relational ledger when permits need joins and transactions. DynamoDB shines at scale for keys; Aurora/RDS owns the join-heavy desk work.
Full Explanation
Amazon DynamoDB is purpose-built for key-value and document access patterns at any scale, which fits high-volume meter ID lookups. Complex multi-table joins and strong relational transactions belong on Amazon Aurora or Amazon RDS. Redshift is analytical, Neptune is graph-oriented, and swapping DynamoDB with RDS for those roles mismatches access patterns.