Building Blocks and the ADM Knowledge-Based Download PDF

Questions

1. 1.

   During the Building Block Specification Process across ADM Phases B, C, and D, how should an enterprise architect define the interfaces and dependencies of Architecture Building Blocks (ABBs) to ensure independent evolvability and prevent vendor lock-in?

   • A) By mapping each ABB directly to a single proprietary Commercial Off-The-Shelf (COTS) product package to guarantee rapid operational deployment.
   • B) By embedding physical deployment scripts directly into interface definitions to reduce latency between architectural specification and runtime delivery.
   • C) By specifying functionality through standard, published interfaces and explicit architectural contracts rather than proprietary implementation mechanisms.
   • D) By eliminating modular boundaries and internal interfaces so that all enterprise components communicate exclusively across a single shared runtime bus.
2. 2.

   When documenting the Baseline Architecture during Phases B, C, and D of the ADM, how should an enterprise architect treat existing operational legacy applications according to the Building Block Specification Process?

   • A) They must be abstracted into baseline Architecture Building Blocks (ABBs) to identify their underlying architectural functions and interfaces independently of specific implementations.
   • B) They must be documented solely as Solution Building Blocks (SBBs) without deriving ABBs, because architectural abstraction is reserved exclusively for the Target Architecture.
   • C) They must be omitted from Phases B, C, and D and recorded strictly within Phase E to prevent legacy constraints from influencing architecture definition.
   • D) They must be replaced directly with generic industry reference models before conducting gap analysis to eliminate legacy dependencies.
3. 3.

   During the Building Block Specification Process in the ADM, an enterprise architect identifies an unresolved capability gap between the Baseline and Target Architectures. What action must the architect take within Phases B, C, and D before evaluating vendor products or implementation options?

   • A) Issue a Request for Information (RFI) to technology vendors to discover available commercial solution components.
   • B) Define a new Architecture Building Block (ABB) that specifies the required functionality, non-functional requirements, and interfaces independently of implementation.
   • C) Select and configure a preliminary Solution Building Block (SBB) to model the expected technical deployment topology.
   • D) Update the Architecture Principles to eliminate the capability requirement and constrain the target scope.
4. 4.

   During the TOGAF ADM Phases B, C, and D, an enterprise architect specifies Architecture Building Blocks (ABBs) to define the target architecture. Which principle must govern the specification of these ABBs to ensure maximum reusability and architectural adaptability across the enterprise?

   • A) ABBs must encapsulate discrete functionality and define well-specified interfaces while remaining independent of specific vendor implementations and technologies.
   • B) ABBs must be tightly coupled to existing organizational hierarchies and proprietary vendor capabilities to expedite near-term procurement.
   • C) ABBs must specify concrete physical deployment topologies and runtime infrastructure configurations before defining conceptual business requirements.
   • D) ABBs must be scoped strictly as bespoke, single-use application components to prevent shared dependencies across business units.
5. 5.

   In the TOGAF ADM Building Block specification process, how does the relationship between Architecture Building Blocks (ABBs) and Solution Building Blocks (SBBs) evolve as the architecture transitions into Phase E (Opportunities and Solutions)?

   • A) ABBs define the required capability, functionality, and interoperability constraints, providing the architectural specifications against which candidate SBBs are identified and evaluated.
   • B) SBBs establish the business requirements and technology-neutral boundaries, which are then used to synthesize formal ABBs during target architecture definition.
   • C) ABBs represent the physical procured products and legacy components, which dictate the functional boundaries of candidate SBBs in implementation planning.
   • D) SBBs eliminate the need for ABBs once Phase E begins, replacing conceptual definitions with proprietary vendor specifications that govern subsequent phases.