A city permitting portal stores short-lived citizen session keys with simple key-value lookups and wants lower operations cost than an always-on relational database. Which design fits best?
Select an answer to reveal the explanation.
Short Explanation
Session keys are sticky notes, not tax ledgers. DynamoDB handles simple key-value lookups without babysitting an always-on RDS box. Redshift and Glacier are the wrong shelves for hot session data.
Full Explanation
Ephemeral session data with key-value access is a classic DynamoDB pattern that avoids the fixed cost and operational overhead of an always-on RDS instance. Multi-AZ RDS is justified for relational OLTP, not for simple session keys. Redshift is a columnar warehouse, and Glacier Deep Archive is for rarely retrieved cold objects—not low-latency sessions.