Overview Knowledge-Based Practice

TOGAF · Architecture Content · Practitioner · Building Blocks

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

Layout:

Choose how questions appear in the preview and test.

Preview the questions below, then start to answer and see your results.

Questions

  1. 1.

    When an enterprise architect evaluates whether to maintain a consolidated, composite Building Block or decompose it into finer-grained constituent Building Blocks, what primary trade-off is accepted by retaining the composite structure?

    • A) Reduced interface and governance complexity across the enterprise, at the expense of lower reusability and reduced flexibility to independently replace internal capabilities.
    • B) Greater vendor independence and modular agility, at the expense of higher operational dependency on specialized point-to-point integration mechanisms.
    • C) Direct traceability to Solution Building Blocks (SBBs), at the expense of omitting non-functional requirements from Architecture Building Blocks (ABBs).
    • D) Complete alignment with physical technology deployment models, at the expense of losing conceptual synchronization with the Business Architecture.
  2. 2.

    According to the TOGAF Standard, which core characteristic enables building blocks to be reliably substituted, recombined, or evolved throughout the architecture lifecycle without unintended disruptions to dependent systems?

    • A) A well-defined boundary with documented interfaces that fully encapsulate internal implementation details
    • B) Direct coupling of operational data schemas to the underlying implementation platforms
    • C) Fixed alignment to a specific commercial vendor's proprietary technology stack
    • D) Complete avoidance of decomposition into smaller subassembly building blocks
  3. 3.

    In the TOGAF Content Framework, what fundamentally distinguishes a building block from an architectural artifact or deliverable?

    • A) A building block represents a reusable, recombineable package of functionality or enterprise capability, whereas artifacts are descriptive representations and deliverables are formally specified work products.
    • B) A building block is exclusively a commercial off-the-shelf software package, whereas artifacts and deliverables represent proprietary internal operational models.
    • C) A building block is limited to governance documentation reviewed at milestone phase gates, whereas deliverables represent physical assets in production.
    • D) A building block consists solely of catalogs and matrices, whereas artifacts and deliverables describe physical hardware and network components.
  4. 4.

    When determining the appropriate boundaries and granularity of building blocks within enterprise architecture content, which principle must an architect apply to maximize long-term flexibility and reusability?

    • A) Establish high functional cohesion within the building block while maintaining well-defined, loosely coupled interfaces to minimize cross-boundary dependencies.
    • B) Couple the functional scope directly to a single vendor implementation to accelerate near-term procurement and delivery cycles.
    • C) Expand the functional boundary to encapsulate all related cross-departmental capabilities into a single monolithic block to eliminate integration points.
    • D) Decompose every business capability into the finest possible atomic operational tasks regardless of governance and integration overhead.
  5. 5.

    During the transition from architecture definition to implementation planning, an enterprise architect must distinguish between Architecture Building Blocks (ABBs) and Solution Building Blocks (SBBs). Which statement best describes the operational relationship between ABBs and SBBs according to the TOGAF Standard?

    • A) ABBs define the required architecture capabilities and business functionality independently of vendor products, whereas SBBs represent the specific candidate or procured components that realize those specifications.
    • B) ABBs represent physical deployments and packaged software products, whereas SBBs define conceptual metamodel entities and organizational governance boundaries.
    • C) ABBs are exclusively authored during Phase F to specify procurement criteria, whereas SBBs are documented during the Preliminary Phase to establish architecture principles.
    • D) ABBs prescribe proprietary vendor configurations and runtime parameters, whereas SBBs define standard open interfaces that constrain vendor selection.

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