Question 160In a separate fictional assessment of Aurora Enterprise 040, a public benefits provider, after a delivery readiness review, the architecture team finds: A merger team cannot follow a business capability through the information it uses to the applications supporting it. Which negative outcome most directly follows from leaving this architecture problem unresolved? Unclassified reusable assets can be misapplied or repeatedly recreated for similar enterprise needs. Fragmented records encourage outdated design reuse and weaken traceability of architecture decisions. An untested target-state vision can omit important transition work and leave capabilities incomplete. Missing relationships make transition impact and ownership questions unreliable during a merger. ExplanationCorrect Answer D:Missing relationships make transition impact and ownership questions unreliable during a merger. Define consistent capability, information, and application relationships in the enterprise metamodel and populate the architecture views. A shared architecture metamodel makes cross-domain impact analysis possible through explicit entity relationships. Incorrect Answers A:Unclassified reusable assets can be misapplied or repeatedly recreated for similar enterprise needs. This is applicable when a team stores generic reference patterns and company-specific solution designs without indicating how one specializes the other; the present condition is that a merger team cannot follow a business capability through the information it uses to the applications supporting it. B:Fragmented records encourage outdated design reuse and weaken traceability of architecture decisions. It is relevant if architecture decisions, reusable patterns, governance records, and target-state models are scattered among unrelated team folders, but the reported issue is that a merger team cannot follow a business capability through the information it uses to the applications supporting it. C:An untested target-state vision can omit important transition work and leave capabilities incomplete. This could help if a team announces a future customer platform but cannot identify which present capabilities are missing or must change, but not when a merger team cannot follow a business capability through the information it uses to the applications supporting it.
Question 161At fictional Orchard Services 041, a public transport operator, during an integration design meeting, the enterprise architecture group identifies: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. What architectural intervention most directly resolves the stated issue? Set explicit breadth, depth, time, and relevant architecture domains before beginning detailed development. Develop the Application Architecture to assign application services, interfaces, and their relationships to business processes. Apply Phase G implementation governance with explicit compliance assessment and managed deviations. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. ExplanationCorrect Answer D:Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. Incorrect Answers A:Set explicit breadth, depth, time, and relevant architecture domains before beginning detailed development. That could help when a transformation requests an enterprise-wide design but does not state the business breadth, detail, or planning time horizon; here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. B:Develop the Application Architecture to assign application services, interfaces, and their relationships to business processes. This is applicable when several teams define inconsistent application responsibilities for the same customer eligibility function; the present condition is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. C:Apply Phase G implementation governance with explicit compliance assessment and managed deviations. It is relevant if delivery teams have begun building a target platform but there is no architecture conformance or exception review during implementation, but the reported issue is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 162At fictional Orchard Services 041, a public transport operator, during an integration design meeting, the enterprise architecture group identifies: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. Which foundation-level architecture principle best explains the appropriate response? The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Phase F migration planning must reflect dependencies and risks, not only individual project preferences. Phase E connects completed architecture definition to practical opportunities and solution options rather than selecting detailed deployment dates. ADM domain phases distinguish business structure, information and application systems, and supporting technology infrastructure. ExplanationCorrect Answer A:The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. Incorrect Answers B:Phase F migration planning must reflect dependencies and risks, not only individual project preferences. That could help when several projects share a new identity platform but the migration plan schedules dependent applications before identity readiness; here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. C:Phase E connects completed architecture definition to practical opportunities and solution options rather than selecting detailed deployment dates. This is applicable when a target architecture is approved but nobody has identified deliverable change initiatives or initial architecture transition options; the present condition is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. D:ADM domain phases distinguish business structure, information and application systems, and supporting technology infrastructure. It is relevant if the architecture team assigns infrastructure topology design to Phase B while leaving business services and capabilities undefined, but the reported issue is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 163At fictional Orchard Services 041, a public transport operator, during an integration design meeting, the enterprise architecture group identifies: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. What evidence most directly demonstrates that the architecture concern was addressed? The migration roadmap places identity capability before dependent migrations and records approved transition mitigations. A reviewed business architecture links operating capabilities, actors, and processes to future service objectives. The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. New requirements and their impacts appear in phase work products and decision logs as changes occur. ExplanationCorrect Answer C:The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. Incorrect Answers A:The migration roadmap places identity capability before dependent migrations and records approved transition mitigations. It addresses a different problem: Several projects share a new identity platform but the migration plan schedules dependent applications before identity readiness. Here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. B:A reviewed business architecture links operating capabilities, actors, and processes to future service objectives. This could matter when a digital payments project models servers and applications but cannot explain which business capabilities or organizational roles need to change. In this case, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. D:New requirements and their impacts appear in phase work products and decision logs as changes occur. This is applicable when a project treats requirements as a one-time business analysis document instead of an activity supporting every architecture phase; the present condition is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 164At fictional Orchard Services 041, a public transport operator, during an integration design meeting, the enterprise architecture group identifies: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. What is the specific likely consequence of failing to address the described issue? A mistaken waterfall interpretation can suppress feedback and produce architecture work disconnected from changing requirements. Partial requirement updates can create contradictory responsibilities at implementation. A missing requirement trace can result in architecture outputs that disagree with accepted stakeholder obligations. A rigid phase boundary can preserve contradictions that invalidate the proposed target state. ExplanationCorrect Answer A:A mistaken waterfall interpretation can suppress feedback and produce architecture work disconnected from changing requirements. The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. Incorrect Answers B:Partial requirement updates can create contradictory responsibilities at implementation. It addresses a different problem: A security review changes an access requirement but only the technology diagram is updated, leaving application responsibilities inconsistent. Here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. C:A missing requirement trace can result in architecture outputs that disagree with accepted stakeholder obligations. This could matter when an architectural requirement changes in one project but is not traced to the ADM phase outputs it affects. In this case, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. D:A rigid phase boundary can preserve contradictions that invalidate the proposed target state. That could help when a solution team refuses to revisit business architecture after a critical technology constraint is discovered in a later phase; here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 165In a separate fictional assessment of Oakridge Group 076, a regional insurer, after a business capability assessment, the architecture team finds: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. Which correction should the architecture team prioritize? Sequence work packages so enabling capabilities precede their dependents and record any necessary interim architecture. Capture, prioritize, and trace architecture requirements and their changes throughout all ADM phases. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. Define ongoing review and maintenance controls for architecture decisions throughout the ADM and their implementation. ExplanationCorrect Answer C:Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Incorrect Answers A:Sequence work packages so enabling capabilities precede their dependents and record any necessary interim architecture. The choice would be appropriate if several projects share a new identity platform but the migration plan schedules dependent applications before identity readiness. Here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. B:Capture, prioritize, and trace architecture requirements and their changes throughout all ADM phases. That option concerns an architectural requirement changes in one project but is not traced to the ADM phase outputs it affects. The problem here is different: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. D:Define ongoing review and maintenance controls for architecture decisions throughout the ADM and their implementation. This could matter when a program treats its architecture decisions as approved forever once the first target diagrams have been published. In this case, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 166In a separate fictional assessment of Oakridge Group 076, a regional insurer, after a business capability assessment, the architecture team finds: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. Which architecture principle most directly supports the targeted correction? Opportunities and Solutions groups architecture changes into feasible work packages and forms initial transition architecture candidates. Architecture Vision work establishes a common change direction and a basis for authorizing further architecture development. The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Requirements Management is continuous across the ADM rather than a single sequential phase performed once. ExplanationCorrect Answer C:The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. Incorrect Answers A:Opportunities and Solutions groups architecture changes into feasible work packages and forms initial transition architecture candidates. This addresses a situation in which a program proposes one monolithic replacement even though the architecture gaps suggest separable migration work; however, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. B:Architecture Vision work establishes a common change direction and a basis for authorizing further architecture development. The choice would be appropriate if business sponsors and technologists describe incompatible success criteria for the same transformation initiative. Here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. D:Requirements Management is continuous across the ADM rather than a single sequential phase performed once. It addresses a different problem: A project treats requirements as a one-time business analysis document instead of an activity supporting every architecture phase. Here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 167In a separate fictional assessment of Oakridge Group 076, a regional insurer, after a business capability assessment, the architecture team finds: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. Which observable architecture review result would best validate that the correction was effective? The endorsed migration roadmap lists ordered work packages, milestones, and transition states. Product increments trace their architectural decisions to agreed constraints while detailed designs evolve with feedback. The decision log documents evaluated alternatives, criteria, accepted trade-offs, and affected stakeholder signoff. The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. ExplanationCorrect Answer D:The team can explain the distinct purposes of architecture phases and demonstrate appropriate iteration between them. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Incorrect Answers A:The endorsed migration roadmap lists ordered work packages, milestones, and transition states. That relates to circumstances in which approved work packages lack a sequenced roadmap or agreement on which transition should happen first. Here the problem is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. B:Product increments trace their architectural decisions to agreed constraints while detailed designs evolve with feedback. This addresses a situation in which an Agile product team receives an exhaustive enterprise blueprint with no priorities or increments suitable for iterative delivery; however, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. C:The decision log documents evaluated alternatives, criteria, accepted trade-offs, and affected stakeholder signoff. The choice would be appropriate if a council endorses one target option without examining competing choices or the concerns of affected stakeholders. Here, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 168In a separate fictional assessment of Oakridge Group 076, a regional insurer, after a business capability assessment, the architecture team finds: An architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. Which negative outcome most directly follows from leaving this architecture problem unresolved? Unresolved sponsor disagreement can destabilize later baseline and target architecture decisions. A single undifferentiated implementation proposal can conceal dependency and migration risks. Unexamined infrastructure failure modes can make the target architecture operationally unsafe. A mistaken waterfall interpretation can suppress feedback and produce architecture work disconnected from changing requirements. ExplanationCorrect Answer D:A mistaken waterfall interpretation can suppress feedback and produce architecture work disconnected from changing requirements. Describe the ADM as an iterative architecture development method with phases and requirements management adapted to the enterprise context. The ADM guides development and governance of enterprise architecture rather than prescribing a single chronological project execution plan. Incorrect Answers A:Unresolved sponsor disagreement can destabilize later baseline and target architecture decisions. It is useful for situations where business sponsors and technologists describe incompatible success criteria for the same transformation initiative; the reported fault, though, is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. B:A single undifferentiated implementation proposal can conceal dependency and migration risks. That relates to circumstances in which a program proposes one monolithic replacement even though the architecture gaps suggest separable migration work. Here the problem is that an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps. C:Unexamined infrastructure failure modes can make the target architecture operationally unsafe. This addresses a situation in which a platform modernization diagram names cloud components but omits network failure and availability constraints; however, an architecture office calls the ADM a mandatory linear software delivery schedule and omits business and transition architecture steps.
Question 169At fictional Bridgewater Holdings 042, a logistics platform, during a transition roadmap review, the enterprise architecture group identifies: A project uses an unfinished architecture vision document as binding implementation approval without stakeholder review. Which architecture action best addresses the specific problem? Run Phase H architecture change management to monitor drivers and determine whether architecture updates or new cycles are warranted. Label provisional architecture deliverables as draft and obtain required reviews before treating an approved version as a baseline. Revisit the affected ADM analysis iteratively and update dependent architecture outputs with the new constraint. Develop the Application Architecture to assign application services, interfaces, and their relationships to business processes. ExplanationCorrect Answer B:Label provisional architecture deliverables as draft and obtain required reviews before treating an approved version as a baseline. Draft deliverables capture work in progress, while approved deliverables have passed the agreed architecture governance acceptance steps. Repository records clearly show version, draft or approved status, decision owner, and approval date for the architecture vision. Incorrect Answers A:Run Phase H architecture change management to monitor drivers and determine whether architecture updates or new cycles are warranted. This relates to a case where an architecture is considered finished even as regulations and business strategy change materially after implementation; the current situation is that a project uses an unfinished architecture vision document as binding implementation approval without stakeholder review. C:Revisit the affected ADM analysis iteratively and update dependent architecture outputs with the new constraint. That relates to circumstances in which a solution team refuses to revisit business architecture after a critical technology constraint is discovered in a later phase. Here the problem is that a project uses an unfinished architecture vision document as binding implementation approval without stakeholder review. D:Develop the Application Architecture to assign application services, interfaces, and their relationships to business processes. This addresses a situation in which several teams define inconsistent application responsibilities for the same customer eligibility function; however, a project uses an unfinished architecture vision document as binding implementation approval without stakeholder review.
Question 170At fictional Bridgewater Holdings 042, a logistics platform, during a transition roadmap review, the enterprise architecture group identifies: A project uses an unfinished architecture vision document as binding implementation approval without stakeholder review. What architectural distinction justifies the correct response? Technology Architecture must support application and data needs through viable infrastructure and operational capabilities. Appropriate architecture scope balances breadth, depth, time, and enterprise boundaries rather than assuming every effort requires equal detail. Architecture governance provides accountability for architecture creation, development, maintenance, and conformance decisions. Draft deliverables capture work in progress, while approved deliverables have passed the agreed architecture governance acceptance steps. ExplanationCorrect Answer D:Draft deliverables capture work in progress, while approved deliverables have passed the agreed architecture governance acceptance steps. Label provisional architecture deliverables as draft and obtain required reviews before treating an approved version as a baseline. Repository records clearly show version, draft or approved status, decision owner, and approval date for the architecture vision. Incorrect Answers A:Technology Architecture must support application and data needs through viable infrastructure and operational capabilities. This could help if a platform modernization diagram names cloud components but omits network failure and availability constraints, but not when a project uses an unfinished architecture vision document as binding implementation approval without stakeholder review. B:Appropriate architecture scope balances breadth, depth, time, and enterprise boundaries rather than assuming every effort requires equal detail. This relates to a case where a portfolio asks a one-quarter integration effort to specify the detailed end state for a decade-long enterprise strategy; the current situation is that a project uses an unfinished architecture vision document as binding implementation approval without stakeholder review. C:Architecture governance provides accountability for architecture creation, development, maintenance, and conformance decisions. It is useful for situations where a program treats its architecture decisions as approved forever once the first target diagrams have been published; the reported fault, though, is that a project uses an unfinished architecture vision document as binding implementation approval without stakeholder review.