The Architecture Requirements Repository Knowledge-Based Practice

Questions

1. 1.

   Within the TOGAF Architecture Repository structure, what essential content must the Architecture Requirements Repository maintain to enable architects to assess the coverage and impact of stakeholder needs across the Architecture Development Method (ADM)?

   • A) Operational change requests and formal dispensation approvals issued during Architecture Board governance meetings
   • B) Validated requirement statements alongside their priority, acceptance criteria, and bidirectional traceability to realizing architectural artifacts
   • C) Candidate reference architectures, vendor product sheets, and reusable building blocks harvested from external industry bodies
   • D) Legally binding contracts, service level agreements, and financial allocation models defining enterprise procurement rules
2. 2.

   When evaluating conflicting quality attributes such as high availability and infrastructure cost during architecture definition, how should the enterprise architect utilize the Architecture Requirements Repository to resolve and document the trade-off?

   • A) By altering the Architecture Metamodel to modify the underlying entity definitions and structural rules governing availability and cost attributes.
   • B) By recording the competing requirement attributes, capturing the impact assessment and rationale for the prioritized trade-off, and updating the requirement disposition states.
   • C) By registering the financial constraint as a formal dispensation in the Governance Log and purging the availability requirement from the repository.
   • D) By transferring the unresolved requirements into the Solutions Landscape and requesting an immediate amendment to the Statement of Architecture Work.
3. 3.

   When emergent stakeholder demands conflict with the agreed scope of an in-flight ADM cycle, how should the enterprise architect record and manage them within the Architecture Requirements Repository?

   • A) Log the demands with a formally documented disposition, such as deferred or rejected, along with their impact assessment and traceability metadata to preserve them for subsequent ADM cycles.
   • B) Overwrite the baseline requirements of the current cycle immediately to align the Architecture Vision with the newly submitted stakeholder demands.
   • C) Transfer the demands directly into the Reference Library as reusable pattern specifications, bypassing requirements governance.
   • D) Exclude the demands entirely from repository storage, because the Architecture Requirements Repository only holds requirements that are currently being implemented.
4. 4.

   When managing enterprise change across multiple concurrent ADM cycles, which operational role does the Architecture Requirements Repository fulfill to maintain architectural coherence?

   • A) It serves as a persistent, centralized store that captures, statuses, and links requirements, constraints, and assumptions to architecture artifacts across iterative delivery lifecycles.
   • B) It holds reusable architecture patterns, industry reference models, and generic guidelines to accelerate target architecture modeling.
   • C) It documents formal Architecture Board approvals, dispensations, and compliance audit reports for ongoing enterprise oversight.
   • D) It catalogs operational deployment scripts, commercial software licenses, and runtime environment specifications used in solution implementation.
5. 5.

   During the establishment of an enterprise-wide Architecture Repository, the lead architect must ensure that artifacts are cataloged according to the TOGAF Standard taxonomy. Which category of artifacts should be held specifically within the Architecture Requirements Repository rather than other repository partitions?

   • A) Approved baseline application models, target technology architectures, and transition architectures
   • B) Industry standards, foundational building blocks, and technical reference models approved for reuse across solutions
   • C) Architecture governance board meeting minutes, SLA audit reports, and signed Architecture Contracts
   • D) Stated functional and non-functional requirements, architectural constraints, business assumptions, and requirements traceability matrices

Answers and step-by-step solutions appear after you finish the test.