The Architecture Requirements Repository Knowledge-Based Download PDF

Questions

1. 1.

   In the TOGAF Standard, how does the Architecture Requirements Repository accommodate requirements that are validated by stakeholders but cannot be implemented within the scope of the current ADM cycle?

   • A) They are discarded from the repository to prevent scope creep, requiring stakeholders to submit fresh requests in subsequent cycles.
   • B) They are moved to the Standards Information Base as provisional guidelines until an implementation project adopts them.
   • C) They are migrated to the Governance Log as unassigned non-compliance waivers awaiting Architecture Board adjudication.
   • D) They are retained in the repository with a deferred disposition status and supporting rationale to inform future architecture iterations.
2. 2.

   When conflicting stakeholder demands arise across concurrent ADM cycles, which action correctly leverages the Architecture Requirements Repository to maintain architectural integrity and guide trade-off decisions?

   • A) Registering temporary requirement exemptions directly inside the Standards Information Base to decouple delivery teams from governance milestones.
   • B) Reclassifying conflicting stakeholder requests as architecture building blocks in the Architecture Landscape to supersede baseline models.
   • C) Transferring unvetted feature change requests to the Solutions Landscape to allow individual project teams to resolve scope discrepancies locally.
   • D) Assessing Requirements Impact Assessments alongside the Architecture Requirements Specification to evaluate dependency trade-offs and trace consequences across target architectures.
3. 3.

   According to the TOGAF Standard, which specific architectural deliverables are maintained within the Architecture Requirements Repository to manage the evolution and consequence of stakeholder needs?

   • A) Industry reference models, foundation architectures, and architectural patterns
   • B) Dispensation records, formal audit findings, and decision logs
   • C) Requirements Impact Assessments and the Architecture Requirements Specification
   • D) Deployed solution building blocks, transition state baselines, and implementation roadmaps
4. 4.

   When organizing architectural assets across the Architecture Repository, which group of artifacts must be cataloged within the Architecture Requirements Repository to support continuous traceability throughout the ADM?

   • A) Reusable architecture patterns, industry reference models, and generic technology guidance
   • B) Agreed architectural constraints, gap-derived functional needs, and validated quality-of-service criteria with lifecycle statuses
   • C) Approved formal dispensation records, architecture contracts, and post-implementation compliance review logs
   • D) Current baseline application catalogs, target data schemas, and transition infrastructure descriptions
5. 5.

   During an Architecture Development Method (ADM) cycle, an enterprise architecture team must systematically store stakeholder-agreed functional and non-functional requirements, architectural constraints, and their lifecycle status. Which component of the Architecture Repository is specifically designated to hold this information?

   • A) The Standards Information Base, to ensure that all non-functional requirements are cataloged as formal compliance standards.
   • B) The Governance Log, to record stakeholder approvals alongside architectural waivers and compliance audits.
   • C) The Architecture Requirements Repository, to capture agreed statements of requirement, assumptions, and constraints across ADM phases.
   • D) The Reference Library, to provide guidelines and patterns that define how system requirements are formally specified.