A development team wants to collect large volumes of sensor readings that contain varying fields based on new device types. They need a method that accepts additional fields without major schema changes and supports horizontal growth. Which style best meets these requirements?
A manual-file approach managed through conversions
A specialized warehouse with fixed table definitions
A column-based style that assigns attributes before deployment
A document-centric style allows new data fields to be added easily, which fits environments where sensor readings may include evolving attributes. A column-based style that locks attributes complicates schema changes for new fields. Rigid warehouse designs constrain updates when new data formats appear. A manual-file approach requires more transformations whenever a sensor introduces a new attribute.
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 document-centric database style?
Open an interactive chat with Bash
Why is a document-centric style better for horizontal scaling?
Open an interactive chat with Bash
How does a document-centric design differ from a column-based design?
Open an interactive chat with Bash
CompTIA Cloud+ CV0-004
Cloud Architecture
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access