A weekly capacity report must aggregate a few fields across millions of historical interface samples. Point lookups of whole device documents are rare. Which database layout best fits the report?
Select an answer to reveal the explanation.
Short Explanation
Think of reading only the “temperature” column from a million weather cards stacked by field—not flipping every full card. Columnar layouts make that analytic scan cheap. Hauling whole device documents for a few aggregates is the wrong shape.
Full Explanation
Columnar databases excel when analytics touch a small subset of fields across large historical sets. Document-oriented whole-object reads and graph topology walks optimize different patterns. Queues are transport, not durable analytic storage for weekly reports.