The two repositories serve different analytical needs and differ chiefly in the state of the data they hold. A data lake ingests data as it arrives from source systems, without cleansing or remodeling, and retains it in raw form. Because the structure is imposed only when the data are queried, a lake is highly flexible and supports exploratory work and machine learning on diverse formats. A data warehouse holds data that have already been extracted, cleansed, conformed, and organized into a defined schema, commonly through an ETL process, so that business users can run consistent reporting and business intelligence queries with confidence. Option C expresses this contrast: raw versus scrubbed. Option A is wrong because both repositories can contain internal and external data; origin does not separate them. Option B inverts the actual relationship. Warehouses are structured and schema-on-write, while lakes accept structured, semi-structured, and unstructured content. The distinction carries consequences for users and cost. Lakes favor data scientists and engineers who need access to original detail, whereas warehouses favor analysts who need reliable curated figures. Many organizations now combine the two in a lakehouse design that layers warehouse-style management over lake storage. Reference: Data Science Fundamentals Study Guide – Data Management: Data Storage Architectures (Data Lakes and Data Warehouses).
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit