County inspectors must filter field jobs by status and district without table scans. Status alone has only a few values. Which DynamoDB design best supports that query?
Select an answer to reveal the explanation.
Short Explanation
Status by itself is like labeling every open job “Open”—you pile the whole county into one hot shelf. Combine district (or district+status) into the GSI partition key so queries stay targeted and partitions stay balanced.
Full Explanation
Global secondary indexes support alternate query patterns without scanning the base table. A status-only partition key has very low cardinality and creates hot partitions. Combining district with status (or using district as PK and status as SK) spreads load and lets inspectors Query for a district’s jobs in a given status. Scans waste RCU; Streams are for change capture, not ad-hoc filtering.