Data As A Product
From the book I Am Datapedia!, published here free by the author.
Part of I Am Datapedia!
Questions 1–10 of 10
1. How does Data-As-a-Product (DAaP) differ from a traditional data product?
2. Which two pathways lead a data product to become Data-As-a-Product (DAaP)?
3. A regional sales insights dashboard's curated datasets start feeding forecasting models, executive dashboards and marketing analytics. Which DAaP pathway does this illustrate?
4. Which of the following is NOT listed as a core feature that a data product must demonstrate to qualify as DAaP?
5. What must enforced data contracts in DAaP codify and version?
6. What is a dependency web in the context of DAaP?
7. When a DAaP faces decommissioning, what is the stated downside of shifting dependencies so that consumers source data directly from origin systems?
8. Why do ownership and funding conflicts arise as a DAaP grows in reach?
9. Which DAaP management strategy recommends architecting DAaPs as composable services so they can be selectively migrated or deprecated?
10. What does 'Plan decommissioning at inception' mean for a DAaP?