A city's citizen-profile service keeps adding optional attributes for new programs, and rigid relational migrations delay each release. Which approach best fits this evolving, high-scale profile data?
Select an answer to reveal the explanation.
Short Explanation
Think of citizen profiles like a filing cabinet that keeps growing new folders—locking the drawer shape every week just slows the city down. NoSQL shines when attributes keep changing and you still need to scale. Let the model bend so programs can ship without a schema fire drill.
Full Explanation
Citizen profiles often accumulate optional, program-specific attributes that do not fit a fixed relational schema without frequent migrations. NoSQL document-oriented and similar flexible models store semi-structured records so new fields can appear without blocking releases. Relational systems remain excellent when schemas are stable and multi-row transactions dominate, but they slow delivery when attributes churn. Choosing NoSQL for this pattern trades rigid upfront schema control for faster evolution at high scale.