Questions DA4-029–042
DA4-029 — Activities · Standard · Apply
An organization has several architecture diagrams, but no one knows whether they still match the live systems. What should the Data Architecture team do first?
A. Evaluate existing architecture specifications for accuracy, completeness, and level of detail and update them as needed.
B. Discard all existing documentation and start with the target architecture.
C. Build the 3–5 year roadmap before checking current state.
D. Wait for a new project to discover the differences organically.
DA4-030 — Roadmap · Standard · Recall
What is the main purpose of the Enterprise Data Architecture roadmap?
A. Describe only the current application inventory.
B. Provide a pragmatic 3–5 year development path for moving from actual conditions toward target architecture in alignment with business needs and resources.
C. Replace the overall Enterprise Architecture roadmap.
D. Specify every physical database table for the next five years.
DA4-031 — Roadmap · Difficult · Apply
A business-data-driven roadmap has several capabilities that depend on data created by upstream capabilities. How does Chapter 4 suggest sequencing them?
A. Begin with the most dependent capability because it has the greatest complexity.
B. Sequence only by application age and ignore data dependencies.
C. Begin with the least-dependent/data-originating capabilities and work toward more dependent capabilities.
D. Always begin with reporting and invoicing regardless of business context.
DA4-032 — Projects · Difficult · Apply
A project specification is complete. Which question should a Data Architect ask according to Chapter 4?
A. Did the project use the same UI framework as every other application?
B. Can the project skip business definitions because its goals are local?
C. Should all project-specific entities be automatically added to the EDM?
D. Do enterprise-wide entities conform to standards, and should any project entities/definitions be added or generalized in the Enterprise Data Architecture?
DA4-033 — Projects · Standard · Apply
During project scope definition, what should architecture help determine?
A. Alignment with the enterprise data model, reuse opportunities, project contribution to enterprise architecture, and external/downstream dependencies.
B. Only the project's coding language and development IDE.
C. Only the project budget and staffing plan.
D. Only final physical storage sizing after design is complete.
DA4-034 — Projects · Standard · Recall
Which data-related requirements does Chapter 4 say projects should capture?
A. Only server CPU, memory, and storage volume.
B. Entity, source(s), availability, quality, pain points, and the business value of meeting requirements.
C. Only user-interface fields and screen layouts.
D. Only data retention dates.
DA4-035 — Projects · Standard · Distinguish
When buying a COTS application, what does Chapter 4 recommend if the vendor does not provide a data model?
A. Accept the vendor structure as the new enterprise standard without analysis.
B. Ignore the package data structure because COTS is outside enterprise architecture.
C. Reverse engineer as needed, map the package to enterprise data structures, identify/document gaps, and try to negotiate for model documentation.
D. Replace the EDM with the vendor product schema.
DA4-036 — Projects · Standard · Distinguish
When reusing existing data, what does Chapter 4 emphasize?
A. Always create a new copy of the data for each application.
B. Reverse engineer only purchased vendor software.
C. Ignore authoritative sources if the local application already has a convenient copy.
D. Map application data models to common structures and processes, understand CRUD, enforce authoritative/system-of-record use, and document gaps.
DA4-037 — Projects · Standard · Distinguish
What is the core Chapter 4 guidance when building a new solution?
A. Implement storage according to the data structure and integrate according to standardized or designed specifications.
B. Let each project invent its own structures without reference to enterprise standards.
C. Use only vendor reverse engineering.
D. Avoid data integration until after production.
DA4-038 — Projects · Difficult · Apply
An agile team says formal data architecture is incompatible with sprints. What response best matches Chapter 4?
A. Architecture must stop until the agile project is finished.
B. Agile still needs specifications for data models, capture, storage, and distribution, with strong architect-programmer collaboration and standards.
C. Agile teams should use only physical models and skip enterprise context.
D. Architecture applies only to waterfall tollgates.
DA4-039 — Integration · Difficult · Apply
Why should Enterprise Data Architecture be integrated with project portfolio management?
A. So architects can approve every project budget line item.
B. So application architects are no longer needed.
C. So enterprise-wide architecture matters and roadmap priorities can proactively influence funded project scope and improve outcomes.
D. So the Data Architecture roadmap can replace the enterprise roadmap.
DA4-040 — Tools · Standard · Recall
Why are data modeling tools and model repositories important to Enterprise Data Architecture?
A. They replace the need for an enterprise data model.
B. They are used only for network packet diagrams.
C. They calculate business-value metrics automatically.
D. They manage enterprise models across levels and track lineage/relationships between models created for different purposes and abstraction levels.
DA4-041 — Tools · Standard · Apply
How can asset management software help Data Architecture?
A. Its inventory and system Metadata can help research current state and create data flows.
B. It automatically designs the target enterprise data model.
C. It is used only to draw architecture diagrams.
D. It replaces software-license management with data governance.
DA4-042 — Techniques · Standard · Distinguish
A technology is currently supported and used in production. Which lifecycle projection status best fits?
A. Emerging.
B. Current.
C. Reviewed.
D. Retirement.