Standards Library Knowledge-Based Practice

Questions

1. 1.

   When structuring the Standards Library, an enterprise architecture team classifies standards by organizational scope into enterprise-wide standards and segment-specific standards. What is the primary architectural trade-off of permitting segment-specific standards alongside enterprise-wide standards?

   • A) It guarantees seamless cross-unit interoperability at the expense of requiring mandatory architecture board dispensations for routine business operations.
   • B) It enables localized operational agility and fit-for-purpose capability delivery at the expense of potentially increased total cost of ownership and cross-segment integration complexity.
   • C) It eliminates the need for architecture governance within business units while enforcing rigid infrastructure uniformity across the enterprise.
   • D) It automatically converts proprietary vendor specifications into open industry standards while eliminating vendor lock-in across all business domains.
2. 2.

   Within the Architecture Repository's Standards Library lifecycle, what governance rule applies when a technology specification is assigned the "Phasing-out" status?

   • A) Existing production deployments must be immediately decommissioned, and runtime operations are halted until migration completes.
   • B) New solutions may freely adopt the specification provided that the associated technical debt is registered in the architecture repository.
   • C) Existing implementations may continue operating, but new initiatives are restricted from adopting it without an approved architecture dispensation.
   • D) The specification is reverted to candidate status so that the governance board can re-evaluate its original functional fit.
3. 3.

   An architecture governance board is evaluating whether to adopt a vendor-specific proprietary interface specification rather than an open industry standard within the Standards Library. What is the primary architectural trade-off associated with designating a proprietary specification as an organizational standard?

   • A) It can deliver immediate functionality tailored to specific vendor capabilities but increases the risk of vendor lock-in and constrains long-term portability.
   • B) It ensures automatic compliance with external legal mandates but prevents the specification from progressing beyond Trial status in the standards lifecycle.
   • C) It eliminates the requirement for architecture dispensations across all projects while permanently precluding multi-vendor procurement strategies.
   • D) It simplifies data modeling across the enterprise but requires the organization to publish the interface specification into the public Reference Library.
4. 4.

   When classifying specifications within the Standards Library, what is the primary governance implication of categorizing an architectural standard as "Mandatory" rather than "Recommended"?

   • A) It restricts the scope of the standard exclusively to foundational technology infrastructure and hardware components.
   • B) It triggers the immediate decommissioning of all existing production systems that do not currently comply with the specification.
   • C) It delegates compliance assessment authority entirely to individual solution delivery teams without central oversight.
   • D) It obligates any architecture initiative seeking deviation from the standard to obtain a formal dispensation from the Architecture Board.
5. 5.

   An enterprise architecture review board is evaluating a newly piloted cloud messaging protocol that has shown promising results in a single project and is now approved for controlled, trial use in selected low-risk initiatives to evaluate its viability. According to the TOGAF Standard, how should this specification be classified within the Standards Library lifecycle?

   • A) As a Provisional standard, enabling constrained deployment across designated projects to assess operational fit before potential enterprise-wide mandate.
   • B) As a Phased-out standard, permitting existing implementations to continue functioning while prohibiting any new project adoption.
   • C) As a Standard, establishing mandatory compliance across all current and future enterprise solutions without exception.
   • D) As a Retired standard, removing formal operational support and requiring immediate migration of all prototype instances.

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