Answers & Rationales DA4-043–056
DA4-043 — C
Why: Preferred = recommended for broad appropriate use; Containment = limited/restricted use.
Weaker: A confuses Emerging/Retirement; B reverses meanings; D treats distinct statuses as synonyms.
Source: pp. 116–117.
Confusion pair: Preferred vs Containment.
DA4-044 — D
Why: Reviewed = evaluated, results known, and not currently in another lifecycle status.
Weaker: Emerging is active research/pilot; Deployment/Strategic Period are time-horizon classifications.
Source: pp. 116–117.
Confusion pair: Reviewed vs Emerging.
DA4-045 — A
Why: Visual differences such as color, box size, or line thickness should signify meaning; random differences reduce diagram clarity.
Weaker: B/C/D concern lifecycle, replication, and measurement rather than visual semantics.
Source: p. 117.
Confusion pair: diagramming clarity.
DA4-046 — B
Why: Chapter 4 recommends launching at least two implementation components together because teams/methods, artifacts, and awareness reinforce one another.
Weaker: A assumes big-bang artifact completion; C is tool-first; D postpones a required behavioral component.
Source: pp. 117–118.
Confusion pair: artifacts + activities + behavior implementation.
DA4-047 — C
Why: In an Agile/solution-oriented culture, maintain an enterprise/Subject Area outline while architects engage early and incrementally in sprints.
Weaker: A freezes too much detail before learning; B abandons enterprise intent; D ignores the chapter’s innovation-oriented implementation distinction.
Source: p. 118.
Confusion pair: Agile architecture implementation.
DA4-048 — D
Why: Multiple senior supporters make architecture more resilient to reorganizations and decision-maker changes.
Weaker: A invents unanimous approval; B contradicts project collaboration; C resembles the source risk of an apprehensive/controlling sponsor.
Source: pp. 118–119.
Confusion pair: management support vs apprehensive sponsor.
DA4-049 — A
Why: One application owner imposing a local ERP data structure on every domain is the source’s dominance of a one-dimensional view risk.
Weaker: B concerns credibility/track record; C is lifecycle; D is visual communication.
Source: p. 119.
Confusion pair: local application view vs enterprise view.
DA4-050 — B
Why: Adoption is supported by treating data as a business asset, adopting enterprise perspective, integrating architecture into projects, and accepting Data Governance.
Weaker: A/C/D reinforce localism or reject the governance/coordination required by the source.
Source: pp. 119–120.
Confusion pair: architecture-friendly culture.
DA4-051 — C
Why: Architecture directly supports alignment/control, architects act as business liaisons, and architects/stewards should align around Subject Areas and entities.
Weaker: A collapses two disciplines; B makes stewards sole architects; D contradicts standards-based project governance.
Source: p. 120.
Confusion pair: Data Architecture vs Data Governance.
DA4-052 — D
Why: Overseeing projects includes ensuring required architecture activities occur, assets are used/improved, and implementation aligns to standards.
Weaker: A collapses governance into execution; B assumes no justified exception; C replaces enterprise direction with project schedules.
Source: p. 120.
Confusion pair: architecture governance vs project execution.
DA4-053 — A
Why: Architecture standard compliance measures how closely projects follow established architecture and the enterprise-architecture engagement process.
Weaker: B is artifact volume; C is a potential business-value outcome; D is a lifecycle mix, not the named compliance measure.
Source: p. 120.
Confusion pair: compliance vs value.
DA4-054 — B
Why: Implementation trends include use/reuse/replace/retire and project execution efficiency such as lead time/resource cost.
Weaker: A is compliance; C and D are business outcome/value measures.
Source: pp. 120–121.
Confusion pair: implementation trend vs business value.
DA4-055 — C
Why: Reduced correction cost and better operational accuracy are business outcomes produced by better integration—strong business-value evidence.
Weaker: A is compliance; B is implementation trend; D is internal review activity/time.
Source: pp. 120–121.
Confusion pair: business value vs compliance/implementation.
DA4-056 — D
Why: Chapter 4 succeeds when enterprise blueprints, flows, roadmaps, project requirements, governance, and behavior reinforce one another and improve outcomes—artifacts + activities + behavior.
Weaker: A is artifacts without adoption; B is local delivery without enterprise alignment; C is tool-first architecture.
Source: pp. 99–121.
Confusion pair: architecture as operating practice vs artifacts/tooling only.