The Open Group OGEA-103 Practice Test 33
Question 320
Architecture peer review: A manufacturer expects customer benefits from an API program but identity work remains a hidden prerequisite. Which assumption, if accepted, most directly leaves this problem unresolved?
- Phase B is principally the selection of server operating systems.
- Phase F is complete once the architect draws a colorful target-state picture.
- An Architecture Contract with implementation contractors replaces authorization for initial architecture development.
- Prioritizing each project solely by its isolated ROI always yields an executable portfolio.
Explanation
Correct Answer
D:This is precisely the false assumption to challenge for Phase F benefit dependencies. The governing principle is: Business value can depend on prerequisite capabilities and should be assessed in planning decisions. This matters here because architecture peer review: A manufacturer expects customer benefits from an API program but identity work remains a….
Incorrect Answers
A:This false belief is about Phase B business baseline. The central misconception is that prioritizing each project solely by its isolated ROI always yields an executable portfolio.
B:This is also a risky claim, but it directly concerns Phase F implementation plan rather than the error in the current case: A manufacturer expects customer benefits from an API program but identity work remains a hidden prerequisite.
C:The shortcut would be dangerous for Phase A work authorization; it is not the particular misconception driving the described Phase F benefit dependencies situation.
Question 321
Consider this enterprise-change situation: A supplier delivers a new platform without clear architectural acceptance criteria or an accountable design authority. What is the most appropriate architecture action?
- Establish Architecture Contracts and governance checkpoints for the implementation work.
- Establish relevant Baseline Business Architecture and compare it with the intended target business design.
- Define Data Architecture ownership, semantics, quality rules, and information exchange needs.
- Use the Preliminary Phase to establish the Architecture Capability and adapt the framework to enterprise needs.
Explanation
Correct Answer
A:This directly addresses Phase G architecture contract. Phase G Implementation Governance governs delivery against the agreed architecture and approved deviations. A useful acceptance check is: Delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
Incorrect Answers
B:This proposal belongs primarily to Phase B business baseline. It does not show that delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
C:Although relevant to Phase C data ownership, this is not the most direct response to Phase G architecture contract. For this decision, what matters is whether delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
D:This action targets another architecture concern: Preliminary capability. The priority here is Phase G architecture contract in this situation; it leaves the specific acceptance result unaddressed: delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
Question 322
During design review: A supplier delivers a new platform without clear architectural acceptance criteria or an accountable design authority. What is the strongest architectural reasoning for the decision?
- Phase A creates a shared starting point for architecture effort and sponsorship.
- Phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
- Value streams describe how an enterprise creates value for stakeholders and can expose cross-capability dependencies.
- Shared principles guide later architecture decisions and reflect enterprise context and governance.
Explanation
Correct Answer
B:This principle addresses Phase G architecture contract. The preferred action is: Establish Architecture Contracts and governance checkpoints for the implementation work. Verify: Delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
Incorrect Answers
A:That principle helps reason about Phase A request scope, but the described concern is specifically governed by Phase G architecture contract. It does not explain phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
C:The statement addresses Phase B value streams. In the present case, a principle for Phase G architecture contract is required: phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
D:That principle helps reason about Preliminary architecture principles, but the described concern is specifically governed by Phase G architecture contract. It does not explain phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
Question 323
A steering committee is checking the result of this engagement: A supplier delivers a new platform without clear architectural acceptance criteria or an accountable design authority. What evidence is most persuasive?
- The technology design documents trust boundaries and tests access restrictions against requirements.
- A responsibility model shows how architects, sponsors, and decision bodies collaborate.
- Delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
- The architecture maps key data exchanges to sources, consumers, and constraints.
Explanation
Correct Answer
C:This checks the Phase G architecture contract outcome. The related decision is: Establish Architecture Contracts and governance checkpoints for the implementation work.
Incorrect Answers
A:The observation could be valid elsewhere for Phase D network trust, but this case needs more direct Phase G architecture contract evidence: delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
B:This result checks another area, Preliminary organizational model. For This case, it does not establish that delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
D:The observation could be valid elsewhere for Phase C data flow, but this case needs more direct Phase G architecture contract evidence: delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
Question 324
Architecture peer review: A supplier delivers a new platform without clear architectural acceptance criteria or an accountable design authority. Which assumption, if accepted, most directly leaves this problem unresolved?
- Phase H exists only to manage help-desk incidents unrelated to enterprise strategy.
- The fastest technical change should always be prioritized before all business-value considerations.
- Business roles can be reliably inferred from server naming conventions.
- An Architecture Contract is simply another name for the initial Architecture Vision.
Explanation
Correct Answer
D:This is precisely the false assumption to challenge for Phase G architecture contract. The governing principle is: Phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
Incorrect Answers
A:This false belief is about Phase H change trigger. The central misconception is that an Architecture Contract is simply another name for the initial Architecture Vision.
B:This is also a risky claim, but it directly concerns Phase F roadmap prioritization rather than the error in the current case: A supplier delivers a new platform without clear architectural acceptance criteria or an accountable design authority.
C:The shortcut would be dangerous for Phase B stakeholder roles; it is not the particular misconception driving the described Phase G architecture contract situation.
Question 325
Architecture case: A federal program funds multiple implementation teams but has no agreement on architectural compliance responsibilities. What should the architect do NEXT to resolve this concern?
- Establish Architecture Contracts and governance checkpoints for the implementation work.
- Use Phase E Opportunities and Solutions to assess candidate solutions and identify meaningful work packages.
- Conduct architecture compliance reviews and document findings, corrective actions, and dispensation decisions.
- Define technology security controls and trusted network paths consistent with cross-cutting architecture requirements.
Explanation
Correct Answer
A:This directly addresses Phase G architecture contract. Phase G Implementation Governance governs delivery against the agreed architecture and approved deviations. A useful acceptance check is: Delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence. This matters here because architecture case: A federal program funds multiple implementation teams but has no agreement on architectural….
Incorrect Answers
B:This action targets another architecture concern: Phase E solution options. The priority here is Phase G architecture contract in this situation; it leaves the specific acceptance result unaddressed: delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
C:This proposal belongs primarily to Phase G compliance. It does not show that delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
D:Although relevant to Phase D network trust, this is not the most direct response to Phase G architecture contract. For this decision, what matters is whether delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
Question 326
Architecture reasoning: A federal program funds multiple implementation teams but has no agreement on architectural compliance responsibilities. Which TOGAF concept MOST directly explains the appropriate response?
- Phase F organizes the execution sequence and governance-ready migration commitments.
- Phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
- Data Architecture should represent how information is created, shared, maintained, retained, and disposed of.
- The EA capability includes people, roles, organizational relationships, skills, and governance arrangements.
Explanation
Correct Answer
B:This principle addresses Phase G architecture contract. The preferred action is: Establish Architecture Contracts and governance checkpoints for the implementation work. Verify: Delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence. This matters here because architecture reasoning: A federal program funds multiple implementation teams but has no agreement on architectural….
Incorrect Answers
A:The statement addresses Phase F implementation plan. In the present case, a principle for Phase G architecture contract is required: phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
C:This is a legitimate concept for Phase C data lifecycle; it does not most directly account for A federal program funds multiple implementation teams but has no agreement on architectural compliance responsibilities. The important distinction is that phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
D:The statement addresses Preliminary organizational model. In the present case, a principle for Phase G architecture contract is required: phase G Implementation Governance governs delivery against the agreed architecture and approved deviations.
Question 327
Following the proposed architecture change: A federal program funds multiple implementation teams but has no agreement on architectural compliance responsibilities. Which outcome should be verified?
- Projects, schedules, dependencies, risks, and accountable owners are captured in the plan.
- Principles have descriptions, rationale, implications, and accountable approval.
- Delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
- Baseline and target business models expose missing capabilities and process dependencies.
Explanation
Correct Answer
C:This checks the Phase G architecture contract outcome. The related decision is: Establish Architecture Contracts and governance checkpoints for the implementation work. This matters here because following the proposed architecture change: A federal program funds multiple implementation teams but has no….
Incorrect Answers
A:This would provide assurance for Phase F implementation plan, not the stated issue. It does not show delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
B:The observation could be valid elsewhere for Preliminary architecture principles, but this case needs more direct Phase G architecture contract evidence: delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
D:This would provide assurance for Phase B business baseline, not the stated issue. It does not show delivery contracts or agreements specify compliance responsibilities, reviews, and acceptance evidence.
Question 328
A proposed decision is challenged in the following case: A federal program funds multiple implementation teams but has no agreement on architectural compliance responsibilities. Which misleading belief must be rejected?
- Phase D should be completed before business outcomes have been considered.
- All work packages are independent by definition once they receive a budget code.
- Phase H exists only to manage help-desk incidents unrelated to enterprise strategy.
- An Architecture Contract is simply another name for the initial Architecture Vision.
Explanation
Correct Answer
D:This is precisely the false assumption to challenge for Phase G architecture contract. The governing principle is: Phase G Implementation Governance governs delivery against the agreed architecture and approved deviations. This matters here because a proposed decision is challenged in the following case: A federal program funds multiple implementation teams but….
Incorrect Answers
A:The shortcut would be dangerous for Phase D platform standards; it is not the particular misconception driving the described Phase G architecture contract situation.
B:This false belief is about Phase E dependency consolidation. The central misconception is that an Architecture Contract is simply another name for the initial Architecture Vision.
C:This is also a risky claim, but it directly concerns Phase H change trigger rather than the error in the current case: A federal program funds multiple implementation teams but has no agreement on architectural compliance responsibilities.
Question 329
Architecture case: A cloud program changes component boundaries during delivery without reviewing their conformity to the target architecture. What should the architect do NEXT to resolve this concern?
- Conduct architecture compliance reviews and document findings, corrective actions, and dispensation decisions.
- Prioritize migration projects using value, cost, risk, dependencies, and resource constraints in Phase F.
- Define technology security controls and trusted network paths consistent with cross-cutting architecture requirements.
- Identify critical data flows, producers, consumers, and interface information requirements.
Explanation
Correct Answer
A:This directly addresses Phase G compliance. Implementation governance maintains conformance between deployed solutions and architecture decisions. A useful acceptance check is: Recorded reviews show compliant changes or formally considered exceptions.
Incorrect Answers
B:This action targets another architecture concern: Phase F roadmap prioritization. The priority here is Phase G compliance in this situation; it leaves the specific acceptance result unaddressed: recorded reviews show compliant changes or formally considered exceptions.
C:This proposal belongs primarily to Phase D network trust. It does not show that recorded reviews show compliant changes or formally considered exceptions.
D:Although relevant to Phase C data flow, this is not the most direct response to Phase G compliance. For this decision, what matters is whether recorded reviews show compliant changes or formally considered exceptions.
Question 330
Architecture reasoning: A cloud program changes component boundaries during delivery without reviewing their conformity to the target architecture. Which TOGAF concept MOST directly explains the appropriate response?
- The Preliminary Phase prepares architecture work by establishing capability, governance, principles, and tailoring.
- Implementation governance maintains conformance between deployed solutions and architecture decisions.
- The EA capability includes people, roles, organizational relationships, skills, and governance arrangements.
- Data movement and sharing must support business processes and application interactions.
Explanation
Correct Answer
B:This principle addresses Phase G compliance. The preferred action is: Conduct architecture compliance reviews and document findings, corrective actions, and dispensation decisions. Verify: Recorded reviews show compliant changes or formally considered exceptions.
Incorrect Answers
A:The statement addresses Preliminary capability. In the present case, a principle for Phase G compliance is required: implementation governance maintains conformance between deployed solutions and architecture decisions.
C:This is a legitimate concept for Preliminary organizational model; it does not most directly account for A cloud program changes component boundaries during delivery without reviewing their conformity to the target architecture. The important distinction is that implementation governance maintains conformance between deployed solutions and architecture decisions.
D:The statement addresses Phase C data flow. In the present case, a principle for Phase G compliance is required: implementation governance maintains conformance between deployed solutions and architecture decisions.