Ownership and governance: Within organizations, are databases enterprise resources rather than the property of a single function or individual?

Introduction / Context:Data governance emphasizes that databases support multiple processes and stakeholders. Treating them as shared enterprise assets improves consistency, compliance, and value creation.

Given Data / Assumptions:

• Databases often integrate data from numerous business functions.
• Multiple teams consume, update, and audit data.
• Policies and stewardship govern shared assets.

Concept / Approach:Positioning databases as enterprise resources avoids siloed ownership and promotes consistent definitions, master data management, and security controls. Even when a department funds a system, the organization benefits from standardized data and controlled access rather than exclusive ownership by an individual or single function.

Step-by-Step Solution:Identify stakeholders and data domains.Define governance roles: owners, stewards, custodians, consumers.Implement shared policies: access control, data quality, lifecycle management.Monitor usage and compliance through audits and metadata catalogs.

Verification / Alternative check:Review cross-functional reporting and integrations; if many consumers rely on the same database, treating it as a shared asset aligns with reality.

Why Other Options Are Wrong:Limiting “enterprise asset” status to read-only marts ignores operational databases. Funding source does not determine governance best practices.

Common Pitfalls:Shadow databases and spreadsheet silos; inconsistent definitions across departments; ad hoc access without stewardship.

Final Answer:Correct