Raw portal events arrive faster than daily aggregates can be finalized. Where should those raw events typically land first in a web-analyzer architecture?
Select an answer to reveal the explanation.
Short Explanation
Catch the rain in a cistern before you bottle drinking water. Raw events land in HDFS, object storage, or messaging first; aggregates come later. Slide decks and browser caches are not the lake.
Full Explanation
Web-analyzer architectures usually land raw events in durable Big Data stores such as HDFS or object storage, or buffer them through messaging, before building aggregate analytical stores. That order preserves Volume for reprocessing and auditing. Browser local storage and slide decks are not durable system-of-record choices. BDPC Domain 10 storage choices follow that landing-then-aggregate pattern.