The Enterprise Repository Knowledge-Based Download PDF

Questions

1. 1.

   When structuring enterprise asset governance, an architecture team must establish appropriate boundaries between the Architecture Repository and other asset holdings within the broader Enterprise Repository. Which asset classification decision correctly aligns with the TOGAF Standard?

   • A) Architecture Building Blocks (ABBs) and reference architectures reside within the Architecture Repository, whereas tangible Solution Building Blocks (SBBs), procured applications, and deployment artifacts reside in specialized solution repositories within the Enterprise Repository.
   • B) Both abstract Architecture Building Blocks (ABBs) and deployable code binaries reside in the Architecture Repository to keep architecture specifications coupled to physical release artifacts.
   • C) The Architecture Repository ingests all runtime configuration databases and commercial vendor license registers directly to eliminate the need for an external Enterprise Repository.
   • D) Architecture Building Blocks (ABBs) are permanently replaced by Solution Building Blocks (SBBs) in the Architecture Repository as soon as an implementation project reaches operational deployment.
2. 2.

   In a federated enterprise environment, how should an architecture team structure the relationship between the Architecture Repository and authoritative corporate assets maintained in the wider Enterprise Repository?

   • A) Ingest all corporate compliance records, procurement contracts, and runtime operational metrics into the Architecture Landscape to maintain centralized control.
   • B) Establish logical references from the Architecture Repository to external authoritative enterprise repositories, maintaining traceability while preventing data duplication.
   • C) Restrict the Enterprise Repository to storing deprecated architectural assets, reserving the Architecture Repository for active corporate policies and operational governance.
   • D) Subsume runtime operational databases into the Architecture Repository so that daily configuration changes directly modify the baseline Architecture Metamodel.
3. 3.

   In the TOGAF Standard, how does the broader Enterprise Repository support the Architecture Repository when coordinating architectural change with operational business execution and portfolio investments?

   • A) By serving as the authoritative source of enterprise-level operational, strategic, and portfolio data that grounds architectural assets within actual organizational capabilities and ongoing initiatives.
   • B) By functioning as an isolated archive that stores deprecated versions of the Architecture Landscape to prevent clutter in the active architecture repository.
   • C) By replacing specialized architecture tools with a monolithic database that unifies all architectural metamodels, reference models, and software source code into a single schema.
   • D) By acting exclusively as a technical runtime database that automatically translates physical infrastructure telemetry into conceptual business capability models.
4. 4.

   During an enterprise modernization initiative, an architecture team must establish traceability between target architectural components and physical operational assets without duplicating configuration management data. Which governance strategy correctly leverages the relationship between the Architecture Repository and the Enterprise Repository to achieve this balance?

   • A) Ingest all operational server configuration items and real-time incident logs directly into the Architecture Landscape to maintain a single authoritative baseline.
   • B) Restrict the Architecture Repository solely to high-level strategic principles while migrating all logical application architectures to the Enterprise Repository's service catalog.
   • C) Maintain architectural definitions and conceptual or logical building blocks in the Architecture Repository while referencing deployed physical instances managed within operational repositories of the Enterprise Repository.
   • D) Consolidate the Architecture Metamodel into the Enterprise Repository's procurement database to automate vendor contract validation against technical standards.
5. 5.

   An enterprise architecture team is defining the boundary and integration model between the Architecture Repository and the broader Enterprise Repository. How does the TOGAF Standard distinguish the scope and relationship of the Architecture Repository relative to the Enterprise Repository?

   • A) The Architecture Repository governs all financial, human capital, and operational runtime registries, whereas the Enterprise Repository is restricted solely to conceptual blueprints and architectural principles.
   • B) The Architecture Repository serves as a temporary staging workspace for draft models during ADM cycles, whereas the Enterprise Repository archives finalized, immutable compliance records.
   • C) The Architecture Repository supersedes and replaces all disparate enterprise configuration and asset management databases, providing a single consolidated database for daily operational management.
   • D) The Architecture Repository is a specialized component that manages architecture models, viewpoints, and governance artifacts, whereas the Enterprise Repository encompasses the broader collection of all enterprise assets, including operational solutions, deployed systems, and portfolio management data.