The Enterprise Continuum Knowledge-Based Download PDF

Questions

1. 1.

   When architecting a reusable enterprise-wide identity and access management capability that applies across multiple business domains but remains independent of any specific industry vertical, at which level of the Architecture Continuum should this architecture be classified?

   • A) Common Systems Architectures
   • B) Industry Architectures
   • C) Foundation Architectures
   • D) Organization-Specific Architectures
2. 2.

   According to the TOGAF Standard, 10th Edition, which fundamental trade-off occurs as architectural artifacts and solutions progress from left to right along the Enterprise Continuum?

   • A) Artifacts gain broader portability across unrelated industry domains while losing direct alignment with organizational strategic goals.
   • B) Architectural artifacts gain business contextual relevance and specificity while their scope of universal applicability and external reusability decreases.
   • C) Architectural descriptions transition toward higher levels of conceptual abstraction while reducing implementation-level constraints.
   • D) Solutions become decoupled from vendor-specific product implementations while increasing the governance overhead required for regulatory compliance.
3. 3.

   According to the TOGAF Standard, 10th Edition, what conceptual role does the Enterprise Continuum play within an enterprise's broader Architecture Repository structure?

   • A) It acts as a physical database management system that automates version control and dependency tracking for operational source code repositories.
   • B) It defines the mandatory chronological phasing of the Architecture Development Method (ADM) iterations across project life cycles.
   • C) It serves as a compliance auditing checklist used strictly by the Architecture Board to reject non-standard vendor proposals during Phase G.
   • D) It provides a conceptual categorization structure within the Architecture Repository that organizes architectural assets from general to specific, enabling discovery, reuse, and informed trade-offs.
4. 4.

   In the TOGAF Standard, 10th Edition, how does the relationship between the Architecture Continuum and the Solutions Continuum guide the practical development and realization of enterprise architectures?

   • A) The Solutions Continuum defines the abstract business requirements and conceptual models, which are then formally translated into structural guidelines within the Architecture Continuum.
   • B) The Architecture Continuum provides the architectural rules, representations, and relationships that guide and constrain the procurement, configuration, and implementation of concrete assets categorized in the Solutions Continuum.
   • C) The Architecture Continuum replaces the Solutions Continuum once baseline architectural models reach the organization-specific level of maturity.
   • D) The Solutions Continuum governs the governance framework and repository structures, whereas the Architecture Continuum tracks procurement agreements and commercial vendor contracts.
5. 5.

   When establishing an architecture repository to support systematic reuse across diverse business units, an enterprise architecture team must classify reference models, patterns, and implementation assets from generic industry standards to customized internal deployments. According to the TOGAF Standard, 10th Edition, how does the Enterprise Continuum structure this classification to guide architectural evolution?

   • A) By categorizing assets strictly according to their chronological development across the Architecture Development Method cycle from Phase A through Phase H
   • B) By classifying assets across the Architecture Continuum and Solutions Continuum, progressing from Foundation Architectures to Organization-Specific Architectures
   • C) By segregating strategic business deliverables into the Architecture Repository while placing all operational software components into the Standards Information Base
   • D) By partitioning artifacts based on governance oversight tiers, evolving sequentially from Strategic Architecture down to Transition Architectures