Immutable Data Warehouse — Learn free

Self-check

Questions 1–10 of 10

1. What does immutable mean?
Question 1A. Not changeableB. Not readableC. Not encryptedD. Not storedE. Not related
2. Why is data in a database described as mutable?
Question 2A. Because it can be read by many users at onceB. Because after inserting it, one also has the option to change it using update or delete commandsC. Because it is stored on rotating disksD. Because it is normalised to 3NFE. Because it must be encrypted
3. At the technology level, what must every database or data store allow?
Question 3A. Only inserts, never updatesB. Updates and deletes, because mutability is a must-have at technology levelC. Automatic deletion of records older than one yearD. Only read access for business usersE. Storage across national borders
4. By default, what kind of datastore is a data warehouse?
Question 4A. A mutable datastoreB. An immutable datastoreC. A virtual datastoreD. A federated datastoreE. An in-memory datastore
5. In the CUSTOMER data set example, which attributes are treated as immutable?
Question 5A. Address and contact detailsB. Jobs and carsC. Name, date of birth, parents and childrenD. Purchase history and preferencesE. Email and telephone number
6. In the CUSTOMER data set example, why are address, contact details, jobs and cars considered mutable?
Question 6A. Because they are never stored in a warehouseB. Because a customer can change them, such as moving house or changing contact detailsC. Because they are not part of the metadataD. Because they are stored in fact tablesE. Because they are always encrypted
7. Where should the immutable or mutable behaviour of each data element be captured, and who should manage it?
Question 7A. In the BI tool, managed by business usersB. In metadata, managed by the Data Governance teamC. In the application code, managed by developersD. In the backup policy, managed by the DBAE. In the ACL, managed by the security team
8. In a data warehouse or data lake, for which tables is immutable behaviour a given?
Question 8A. Dimension tablesB. Staging tablesC. Fact tablesD. Lookup tablesE. Audit tables
9. What does the insurance business example illustrate about historical data in a data warehouse?
Question 9A. That all historical data must always be storedB. That what history to keep depends on the nature of the business, so irrelevant elements such as address changes may not be storedC. That insurers must store every address changeD. That fact tables should be mutable in insuranceE. That insurers do not need a data warehouse
10. What is the architectural purpose of any data warehouse or data mart with respect to history?
Question 10A. To overwrite transactions with their latest stateB. To keep historical transactional data residing in fact tablesC. To delete data older than the retention periodD. To store only current dimension valuesE. To virtualise transactions from source systems