An e-commerce analytics team ingests supplemental transaction details from multiple payment services. Each incoming JSON record may include additional, unexpected fields beyond a shared core set. Which storage solution best handles these unpredictable attributes?
A star schema data mart optimized for fixed dimensions
A fully normalized relational database with predefined columns
A segmented relational design that stores optional fields in child tables
A non-relational document database with a flexible schema
Document-oriented NoSQL databases store each record as a self-contained JSON document, so different records in the same collection can have different fields without any DDL changes. In contrast, a star schema or a fully normalized relational design requires predefined columns; adding a new attribute means altering tables or building extra join tables. Splitting optional fields into child tables also complicates queries and slows iteration.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a general-purpose data repository?
Open an interactive chat with Bash
Why are star schemas and relational database designs less suitable for evolving data fields?
Open an interactive chat with Bash
What challenges arise in using a segmented design with multiple tables for evolving data?