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. Mistaking multi-partner JSON schema drift for volume misdirects architecture and governance choices. Variety is not limited to video, and calling every API "volume" erases a core 4 V distinction taught in BDPC fundamentals.