A parks department must store photo metadata, free-form tags, and view counters for each trail report in one flexible record instead of rigid columns. Which approach best fits this variety?
Select an answer to reveal the explanation.
Short Explanation
Think of each trail report like a digital scrapbook page: photos, tags, and counters all travel together. A document NoSQL store lets those mixed fields sit in one flexible record without forcing every report into identical columns. Rigid relational tables and MapReduce word-count jobs miss that variety-driven pattern.
Full Explanation
Variety in Big Data often pushes teams toward document-oriented NoSQL models when attributes differ widely across items. A parks trail report mixing media metadata, tags, and counters is a classic flexible-document case. Forcing a single rigid relational schema or substituting batch MapReduce for a live store does not address schema flexibility. Graph-only designs aimed at foreign-key cascades also miss the document use case.