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.
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Ayblaq
Highly Voted 7 months, 2 weeks agoAyblaq
7 months, 1 week agoher_lo
Most Recent 3 weeks, 6 days agoRip696
2 months, 2 weeks agoreeftu
2 months, 3 weeks ago