Architecture Landscape Knowledge-Based Download PDF

Questions

1. 1.

   When multiple concurrent transformation projects develop architectures that impact shared business capabilities across the Architecture Landscape, which governance practice best ensures consistency across these overlapping architectures?

   • A) Consolidating all active segment initiatives into a single monolithic strategic architecture before allowing individual capability work to proceed
   • B) Restricting the Architecture Landscape to document only operational baseline architectures while delegating future-state modeling to project-level repositories
   • C) Deferring the resolution of conflicting target building blocks to implementation governance in Phase G to avoid slowing initial architecture definition
   • D) Establishing synchronized transition architectures as formal intermediate plateaus and reconciling building block dependencies across the landscape during architecture development
2. 2.

   An enterprise architecture team is experiencing high governance overhead because its Architecture Landscape has been populated with granular operational asset inventories and device configurations. According to the TOGAF Standard, how should the team adjust the repository content to maintain architectural effectiveness while avoiding operational duplication?

   • A) Migrate the device configurations into the Standards Information Base to enforce compliance through formal architecture governance.
   • B) Restrict the Architecture Landscape exclusively to Strategic Architectures to eliminate detailed architectural descriptions across all domains.
   • C) Retain architectural models and conceptual building blocks within the Architecture Landscape while delegating operational asset details to operational management repositories.
   • D) Replace the enterprise-specific baseline descriptions with generic industry reference models stored within the Reference Library.
3. 3.

   When a major transformation initiative concludes deployment and transitions into live operations, the enterprise architecture team must update the Architecture Repository to ensure future architecture iterations remain valid. How should the team incorporate the newly operational building blocks and configurations in accordance with the TOGAF Standard?

   • A) By archiving the implementation blueprints in the Governance Log while registering interface protocols in the Standards Information Base
   • B) By publishing the enterprise-specific system designs directly into the Reference Library as reusable industry patterns
   • C) By retiring historical roadmap artifacts and preserving the delivered design solely within the Architecture Requirements Repository
   • D) By updating the relevant baseline architecture models within the Architecture Landscape to reflect the newly operational state
4. 4.

   An enterprise architecture team is conducting an impact assessment for a corporate merger and must evaluate the organization's existing operational structures alongside committed transition plateaus and future vision states. Which component of the TOGAF Architecture Repository is specifically designated to hold these point-in-time baseline, transition, and target architectural representations?

   • A) Standards Information Base
   • B) Reference Library
   • C) Architecture Landscape
   • D) Solutions Landscape
5. 5.

   An enterprise architecture team is structuring its Architecture Landscape within the Architecture Repository to support both executive long-range investment planning and program-level solution delivery. How should the team categorize these architectural representations to ensure proper separation of concerns across abstraction levels according to the TOGAF Standard?

   • A) Group architectures into Foundation, Common Systems, and Industry architectures to classify them by market reusability.
   • B) Organize the views into Standards Information Base, Governance Log, and Reference Library to separate compliance rules from design models.
   • C) Classify architectures strictly by development lifecycle state into In-Flight, Implemented, and Retired states.
   • D) Organize the architecture assets into Strategic, Segment, and Capability architectures to reflect varying granularity, operating horizons, and stakeholder concerns.