Data As A Product — Learn free

Self-check

Questions 1–10 of 10

1. How does Data-As-a-Product (DAaP) differ from a traditional data product?
Question 1A. DAaP is a curated, production-grade dataset or model designed for consumption by multiple downstream users, systems or applications, rather than a narrow, predefined use caseB. DAaP is always a dashboard, whereas traditional data products are always datasetsC. DAaP is stored only in memory for speedD. DAaP is built exclusively by external vendorsE. DAaP has no owner, whereas traditional data products do
2. Which two pathways lead a data product to become Data-As-a-Product (DAaP)?
Question 2A. Migration and replicationB. Organic maturity and purposeful designC. Certification and auditD. Outsourcing and insourcingE. Archiving and restoration
3. A regional sales insights dashboard's curated datasets start feeding forecasting models, executive dashboards and marketing analytics. Which DAaP pathway does this illustrate?
Question 3A. Purposeful designB. DecommissioningC. Organic maturityD. Cost allocationE. Dependency shifting
4. Which of the following is NOT listed as a core feature that a data product must demonstrate to qualify as DAaP?
Question 4A. Semantic modelling and clarityB. Enforced data contractsC. Discoverability and accessibilityD. Exclusive single-consumer accessE. Independent lifecycle management
5. What must enforced data contracts in DAaP codify and version?
Question 5A. Employee names and departmentsB. Only the price charged to consumersC. The colour scheme of dashboardsD. The hardware specification of serversE. Schemas, data types, expected freshness and delivery protocols
6. What is a dependency web in the context of DAaP?
Question 6A. The situation where a DAaP serves many consumers, so modifying or decommissioning its originating system risks cascading failuresB. A website listing all data productsC. A network diagram of servers in a data centreD. The set of people who report to the Data Product OwnerE. A graph of customer relationships
7. When a DAaP faces decommissioning, what is the stated downside of shifting dependencies so that consumers source data directly from origin systems?
Question 7A. It makes the DAaP more expensive to runB. It increases integration effort and consumer-side complexityC. It removes all governance from the dataD. It requires a new database technologyE. It forces producers to retain the DAaP indefinitely
8. Why do ownership and funding conflicts arise as a DAaP grows in reach?
Question 8A. Because regulators require a single funder for every datasetB. Because DAaP cannot be shared across more than two teamsC. Because producers may resist carrying the operational burden while consumers are reluctant to own upstream complexityD. Because the cost of storage always doubles each yearE. Because data contracts forbid cost sharing
9. Which DAaP management strategy recommends architecting DAaPs as composable services so they can be selectively migrated or deprecated?
Question 9A. Monitor usage patternsB. Implement cost allocation modelsC. Embed collaborative governanceD. Design for modularityE. Plan decommissioning at inception
10. What does 'Plan decommissioning at inception' mean for a DAaP?
Question 10A. Every DAaP should be shut down within its first yearB. A DAaP should never be decommissioned once builtC. Decommissioning should be decided only by the consumersD. A DAaP should be built without any consumersE. Every DAaP should have a sunset strategy aligned with downstream transition plans from the start