PDF Downloads

Overview

Practitioner • Building Blocks • Knowledge-Based • 5 questions

Overview Knowledge-Based Download PDF

TOGAF · Architecture Content · Practitioner · Building Blocks

5 Practitioner practice questions on Overview. Questions that assess core concepts and understanding.

Questions

  1. 1.

    According to the TOGAF Standard, how does the structure of building blocks facilitate recursive composition across different levels of architectural modeling?

    • A) By enforcing that building blocks only describe physical implementation assets that cannot be further partitioned.
    • B) By enabling building blocks to be assembled into composite blocks or decomposed into discrete subassemblies according to the required level of abstraction.
    • C) By mandating that each building block maps strictly to an isolated, non-communicating business process.
    • D) By decoupling building block definitions entirely from business goals to maintain permanent structural uniformity.
  2. 2.

    When specifying and assembling building blocks to compose an enterprise architecture, which approach most effectively balances organizational reusability with manageable integration complexity?

    • A) Encapsulating diverse and disparate business processes into monolithic building blocks to eliminate cross-component network calls
    • B) Defining building blocks around cohesive, well-bounded functionalities that interact strictly through standardized, published interfaces
    • C) Designing building blocks with tightly coupled data dependencies tailored directly to individual departmental operational structures
    • D) Restricting all building block boundaries exclusively to vendor-native, proprietary components available in the current technology stack
  3. 3.

    According to the TOGAF Standard, how should an enterprise architect manage the level of detail and granularity of building blocks throughout the architecture development cycle?

    • A) Building blocks must be defined at the most granular, atomic technical level during initial scoping to prevent subsequent architectural rework.
    • B) Building blocks should strictly align with organizational departmental hierarchies to simplify ownership and administrative boundaries.
    • C) Building blocks must remain fixed at an abstract conceptual level throughout the ADM cycle, delegating all structural elaboration entirely to vendor procurement.
    • D) Building blocks should be defined at progressive levels of detail, beginning as broad aggregate specifications in early phases and becoming increasingly refined as decisions mature.
  4. 4.

    According to the TOGAF Standard, which characteristic of a building block is essential to ensure that architecture elements can be independently updated, procured, or replaced without disrupting adjacent capabilities?

    • A) Embedding proprietary platform dependencies within initial specifications to guarantee execution performance
    • B) Maximizing functional interdependency across architecture domains to simplify centralized governance
    • C) Consolidating disparate enterprise functions into monolithic boundaries to minimize component count
    • D) Defining explicit functional boundaries and standardized interfaces that decouple specifications from implementations
  5. 5.

    According to the TOGAF Standard, what is the primary distinction between an Architecture Building Block (ABB) and a Solution Building Block (SBB)?

    • A) An ABB represents a procured physical component or off-the-shelf software package, whereas an SBB defines the conceptual, technology-agnostic capability required by the business.
    • B) ABBs are exclusively developed during Phase E (Opportunities and Solutions), whereas SBBs are documented in the Architecture Vision during Phase A.
    • C) SBBs define what functionality must be achieved without prescribing implementation, whereas ABBs document vendor-specific design parameters and operational configurations.
    • D) ABBs specify the required capability and functionality in a technology-agnostic manner, whereas SBBs define the candidate or actual implementations used to realize that functionality.