A clerk assumes any JSON API feed is "volume" when the real pain is dozens of drifting schemas across partners. Which correction is accurate?
Select an answer to reveal the explanation.
Short Explanation
Volume is "how much"; variety is "how many shapes." A skinny JSON fire hose with twenty quarreling schemas is a variety headache wearing a volume nametag. Fix the label so the fix matches the pain.
Full Explanation
Volume concerns the quantity of data that must be handled; variety concerns heterogeneous structures and schemas. When a clerk labels any JSON API feed as "volume" while the real pain is dozens of drifting partner schemas, the accurate correction is that schema chaos is a Variety problem. Civic partner integrations—permits, mobility, health—break when architecture plans for "more bytes" instead of "more shapes."
Claiming JSON always means velocity and never relates to schemas fails by concept: JSON can raise multiple Vs, and schema drift is Variety. Calling schema drift Volume because "volume means any API" fails by concept: APIs are not synonyms for scale. Limiting Variety to video only so JSON chaos must be Veracity fails by concept: Variety covers heterogeneous types and schemas beyond video, and schema drift is not primarily a truthfulness label.
Exam caveat: Keep Volume (scale) distinct from Variety (heterogeneous types/schemas); mislabeling partner JSON drift as Volume misdirects governance and tooling.
Operational check: Inventory partner JSON schemas and drift rate, tag the pain as Variety, and choose flexible ingest or schema-registry practices instead of only buying more disk.