Which of the following activities is NOT a way that enterprise data architecture influences the scope boundaries of projects?
Which of the following activities is NOT a way that enterprise data architecture influences the scope boundaries of projects?
I am thinking the answer should be A since this is typically the responsibility of business analysts or process managers, not data architects. Other options typically fall within the scope of enterprise data architecture.
Reference: Page 111 under Data Architecture of DAMA DMBOK V2
The answer its A
A as explain by others
The listed activities in the book directly describe the key ways Enterprise Data Architecture influences the scope boundaries of projects and system releases. They focus specifically on: Data Requirements: Defining what data is needed for a project. Design Reviews: Ensuring data models align with organizational strategy. Data Lineage: Maintaining traceability and consistency in data flows. Replication Controls: Managing data consistency across systems. Standards Enforcement: Applying architectural standards and principles. Technology Guidance: Coordinating with enterprise architects on data technology decisions. Nowhere in these responsibilities does documenting enterprise business processes appear. That task is outside the domain of data architecture and is typically managed by business analysts or enterprise architects focused on business process management.
las demás están consideradas en el documento
A. Ensuring enterprise business processes are effectively documented → Incorrect activity for data architecture. This falls under Business Process Management (BPM) or Enterprise Architecture (EA) rather than Enterprise Data Architecture. B. Performing design reviews to ensure support of long-term organizational strategy → Correct, as it aligns project scope with data strategy. C. Providing enterprise data requirements for projects → Correct, since data architecture defines data-related needs. D. Enforcing data architecture standards → Correct, as data architecture ensures consistency and compliance. E. Ensuring sufficient data replication controls are in place → Correct, since replication is crucial for data availability and integrity.
Enterprise Data Architecture (EDA) focuses on defining data structures, governance, integration, and long-term data strategy within an organization. It helps shape how data is managed, stored, and shared across projects.