Although Data Lakes and Data Warehouses have materially different architectures, both support the broader objective of making organizational data available for reporting, analysis, analytics, and decision support. Therefore, option B identifies their legitimate conceptual overlap.
A traditional Data Warehouse generally contains integrated, curated, structured data designed for repeatable Business Intelligence, reporting, and analytical workloads. A Data Lake typically retains larger volumes of raw or less-structured information and supports flexible processing, exploration, Data Science, and advanced analytics. Both can therefore participate in analytical data pipelines even though their approaches to schema, transformation, governance, and consumption differ.
They do not inherently duplicate every item of operational data. Nor must a Data Lake produce dimensional or star-schema models; that modeling approach is more closely associated with traditional warehouse implementations. Governance is required for both rather than being the defining difference between them.
From a Data Quality standpoint, warehouses typically apply substantial cleansing and conformity before consumption. Lakes may retain raw values and defer interpretation, which increases the importance of metadata, provenance, cataloging, profiling, and consumer awareness.
Reference Topics: DAMA-DMBOK2 — Data Warehousing and Business Intelligence; Big Data; Data Lakes; Analytical Data; Metadata; Chapter 13 — Data Preparation and Fitness for Purpose.
===============
