A citizen-feedback portal stores evolving JSON documents whose fields change as new survey types appear. Which database pattern fits better than a rigid relational schema?
Select an answer to reveal the explanation.
Short Explanation
Think of citizen feedback like sticky notes that keep gaining new corners — rigid spreadsheet columns fight you every week. Document stores shrug and keep the JSON as it grows. You are picking flexibility for semi-structured data, not forcing a migration circus for every survey tweak.
Full Explanation
Non-relational document databases store semi-structured documents (often JSON) without requiring a fixed relational schema for every attribute. That flexibility suits evolving feedback or content payloads where fields change frequently. Rigid schemas, offline tape, and raw block LUNs do not address the document flexibility requirement.