Logical Data Warehouse — Learn free

Self-check

Questions 1–10 of 10

1. What is a Logical Data Warehouse (LDW)?
Question 1A. A new storage technology that replaces physical warehousesB. An architectural approach delivering a unified warehouse view without physically consolidating all data into one repositoryC. A data warehouse modelled strictly in 3NFD. A cube of pre-aggregated dataE. A department-level data mart
2. What is the backbone of a Logical Data Warehouse?
Question 2A. ETL pipelinesB. Tape archivesC. Data virtualizationD. OLAP cubesE. Data scraping
3. How does a Logical Data Warehouse relate to modelling techniques such as Inmon's 3NF or Kimball's star and snowflake schemas?
Question 3A. It requires 3NF onlyB. It requires star schemas onlyC. It is modelling-agnostic; the distinction lies in the physical location of the data, not the modelling techniqueD. It forbids dimensional modellingE. It replaces modelling with schema-on-read
4. What does pushdown processing mean in a Logical Data Warehouse?
Question 4A. Copying data down into a central repository before queryingB. Processing is pushed to the underlying engines so analytical workloads use their compute powerC. Moving old data to cheaper storage tiersD. Compressing results before returning themE. Delegating governance to source system owners
5. In practical terms, how does a Logical Data Warehouse present itself to users?
Question 5A. As a collection of separate source system loginsB. As a semantic and integration layer exposing curated views, so users experience a single warehouseC. As a raw data lakeD. As a spreadsheet exportE. As a set of ETL job schedules
6. Which of the following is a governance advantage of a well-implemented Logical Data Warehouse?
Question 6A. Metadata, lineage, access control and quality enforcement can be centralised through the logical layerB. Governance becomes unnecessary because data is not movedC. Each source system governs itself independentlyD. Access control is delegated to the BI toolE. History is preserved automatically
7. Why is a Logical Data Warehouse less suitable for regulatory reporting, auditing and long-term trend analysis?
Question 7A. Because it cannot run SQLB. Because it does not inherently provide historical storage; if sources do not retain history, the LDW cannot reconstruct itC. Because regulators forbid virtualizationD. Because it only supports unstructured dataE. Because it cannot integrate APIs
8. What risk arises when a Logical Data Warehouse pushes analytical queries down into operational (OLTP) systems?
Question 8A. Data becomes encryptedB. Performance degradation, as operational workloads compete with analytical queries and service levels may be violatedC. Historical data is duplicatedD. The semantic layer stops workingE. Metadata is lost
9. Why does federated access in a Logical Data Warehouse raise security concerns?
Question 9A. Because all data must be decrypted in transitB. Because it increases the surface area for misconfiguration and may expose sensitive datasets or create unintended access pathsC. Because passwords must be shared across systemsD. Because it disables access control listsE. Because it stores copies of data in every source
10. How should a Logical Data Warehouse be positioned relative to a physical data warehouse?
Question 10A. As a full replacement for the physical warehouseB. As an architectural complement, often in a hybrid where the physical warehouse holds curated history, a lake holds raw data, and the logical layer unifies accessC. As a temporary staging area before loading the physical warehouseD. As a data mart for one departmentE. As a backup of the physical warehouse