A Node.js inspection service must persist a nested checklist object to DynamoDB without turning numbers into unexpected strings or dropping nested maps. What should the team use?
Select an answer to reveal the explanation.
Short Explanation
Hand DynamoDB a real nested object the way your app thinks about it. The document client (or proper marshalling) keeps numbers as numbers and maps as maps—no surprise string conversions.
Full Explanation
Application objects must be serialized to DynamoDB AttributeValue types and deserialized on read. The Document Client (or marshall/unmarshall helpers) maps JavaScript objects, arrays, and numbers to Map, List, and Number types correctly. Stuffing CSV or opaque base64 loses queryability and type fidelity; routing nested JSON through unrelated RDS columns is outside this DynamoDB persistence pattern.