Two clerks may update the same case-notes item concurrently. How should the app prevent silent overwrites in DynamoDB?
Select an answer to reveal the explanation.
Short Explanation
Don’t let the second clerk’s save stomp the first. Stamp a version (or condition) and refuse the write when the item changed underneath—classic optimistic locking.
Full Explanation
DynamoDB conditional writes and optimistic locking (version attributes with ConditionExpression) prevent lost updates when concurrent writers race. Blind PutItem after Scan invites overwrites; removing IAM controls is unsafe; SNS is messaging, not the system of record for case notes.