A multi-account public-health program is replacing a sticky-session SQL table that stores field-kit device IDs and inspection-app session tokens that are keyed lookups with bursty write rates. Which target datastore should architects select?
Select an answer to reveal the explanation.
Short Explanation
Session tokens and device IDs are lockers with labels, not a novel you page through. DynamoDB is built for that key-value slam without running a SQL night shift. Glacier and laptop files are not a live registry.
Full Explanation
Key-value access patterns such as device registries and session state map to Amazon DynamoDB as a Task 4.3 target. DynamoDB provides managed scale, consistent keyed lookups, and no server administration across public-health accounts. A single-AZ Oracle RDS instance recreates operational burden and a SPOF, Glacier is cold object storage, and laptop files lack a durable shared registry.