Introduction to Building Blocks Knowledge-Based Download PDF

Questions

1. 1.

   According to the TOGAF Standard, how does the aggregation characteristic of building blocks operate when structuring complex architectures?

   • A) A composite building block can assemble multiple sub-building blocks to deliver broader capabilities while each constituent block retains its own defined boundaries and interfaces.
   • B) Aggregated building blocks merge their internal mechanisms into an indivisible monolithic unit, eliminating all intermediate interfaces to maximize execution performance.
   • C) High-level composite blocks must consist strictly of physical Solution Building Blocks (SBBs) because Architecture Building Blocks (ABBs) cannot be decomposed hierarchically.
   • D) Constituent sub-building blocks are restricted to disparate architectural domains and are prohibited from sharing common enterprise infrastructure.
2. 2.

   When transitioning from architecture definition to implementation planning in the TOGAF ADM, how should an enterprise architect utilize Architecture Building Blocks (ABBs) to guide the selection of candidate Solution Building Blocks (SBBs)?

   • A) By altering the target ABBs to incorporate the proprietary application interfaces and specific data structures of the preferred vendor product.
   • B) By prioritizing candidate SBBs exclusively by procurement cost and deferring any unsatisfied ABB functional requirements to future architecture cycles.
   • C) By mapping candidate SBBs directly to strategic business goals while bypassing intermediate architectural specifications to accelerate delivery.
   • D) By evaluating candidate SBBs against the functional, interface, and interoperability specifications defined in the ABBs to identify gaps and surplus features.
3. 3.

   An enterprise architect observes that a target architecture model specifies its Architecture Building Blocks (ABBs) using proprietary product brand names and vendor-specific configurations. Why does this practice contradict the intended role of ABBs in the TOGAF Standard?

   • A) It violates the principle that ABBs must exclusively represent business capability increments and cannot describe application or technical functionality.
   • B) It prevents the architecture repository from categorizing the assets, because the TOGAF Standard mandates that vendor names only appear in the Architecture Vision.
   • C) It compromises implementation independence by prescribing specific products rather than defining the functional requirements and architectural characteristics needed to evaluate candidate Solution Building Blocks (SBBs).
   • D) It breaches governance rules because ABBs cannot define interfaces or attributes until after Solution Building Blocks (SBBs) have been deployed in Phase G.
4. 4.

   According to the TOGAF Standard, which statement accurately reflects the generic characteristics of a building block?

   • A) It must be intrinsically tied to a specific proprietary vendor platform to guarantee physical execution boundaries and operational governance.
   • B) It represents an indivisible atomic unit of architectural design that cannot be assembled from or decomposed into smaller sub-components.
   • C) It has a defined boundary, aligns to an entity type in the architecture metamodel, and interacts with interdependent blocks through defined interfaces.
   • D) It is tailored exclusively to a single architecture project and is restricted from being reused across broader organizational capabilities.
5. 5.

   During the development of target architectures, an enterprise architect must distinguish between Architecture Building Blocks (ABBs) and Solution Building Blocks (SBBs) to preserve implementation independence. Which statement correctly characterizes the relationship and distinction between ABBs and SBBs in the TOGAF Standard?

   • A) SBBs define functional requirements and interoperability constraints, whereas ABBs represent the physical products selected to fulfill them.
   • B) ABBs capture architectural requirements and functional specifications independent of implementation, whereas SBBs define specific candidate implementations and components that realize those requirements.
   • C) ABBs are exclusively defined during Phase F to manage decommissioning, whereas SBBs are drafted during Phase A to set the initial architecture vision.
   • D) SBBs provide vendor-neutral interface definitions, whereas ABBs document vendor-specific configurations and procurement contracts.