Skip to content

60-Second Rapid Recall — R37–R54

  1. R37. What is the practical meaning of Implement Data Governance? (p. 90)
  2. R38. What makes governance standards/procedures operational rather than decorative? (pp. 91–92)
  3. R39. What is the purpose of developing a Business Glossary? (pp. 92–93)
  4. R40. How should DG coordinate with Data Architecture? (p. 93)
  5. R41. What should Governance do about data-asset valuation? (pp. 79–81, 93)
  6. R42. What does it mean to Embed Data Governance? (pp. 93–94)
  7. R43. Give the deciding distinction between DG and IT Governance. (p. 73)
  8. R44. What is the strongest clue for the Steering Committee? (pp. 75–77)
  9. R45. What is the strongest clue for the DGC? (pp. 75–77)
  10. R46. What is the strongest clue for the DGO? (pp. 75–77)
  11. R47. What is the strongest clue for a Stewardship Team? (pp. 76–78)
  12. R48. What can distinguish a Chief Data Steward? (pp. 78–79)
  13. R49. What distinguishes an Executive Data Steward? (pp. 78–79)
  14. R50. What distinguishes an Enterprise Data Steward? (pp. 78–79)
  15. R51. What distinguishes a Coordinating Data Steward? (p. 79)
  16. R52. What should policy contain, and what detail should it avoid absorbing from standards/procedures? (p. 79; pp. 91–92)
  17. R53. What makes a Data Standard different from a Policy? (pp. 91–92)
  18. R54. What makes a Procedure different from a Standard? (pp. 91–92)

← R19–R36 · R55–R70 →