PDF Downloads

Introduction

Practitioner • Architecture Deliverables • Knowledge-Based • 5 questions

Introduction Knowledge-Based Download PDF

TOGAF · Architecture Content · Practitioner · Architecture Deliverables

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

Questions

  1. 1.

    When establishing governance and milestone review gates across an ADM cycle, how does the TOGAF Standard, 10th Edition characterize the relationship between architecture deliverables and the artifacts they contain?

    • A) Artifacts must be confined to a single deliverable to prevent configuration and versioning conflicts during phase transitions.
    • B) Each deliverable must strictly correspond to a single architecture domain to ensure clean separation of architectural concerns.
    • C) Artifacts replace formal deliverables once an architecture project transitions from planning phases into implementation governance.
    • D) Deliverables serve as the formal work products that package relevant catalogs, matrices, and diagrams to satisfy contractual review and stakeholder sign-off requirements.
  2. 2.

    According to the TOGAF Standard, 10th Edition, how should an enterprise architecture practice utilize the standard architecture deliverable descriptions provided in the Architecture Content framework?

    • A) As adaptable starting points that must be tailored and packaged to suit the specific governance, methodology, and stakeholder needs of the enterprise
    • B) As mandatory documentation templates that must be produced verbatim to guarantee formal architectural compliance
    • C) As final physical specifications intended exclusively for direct configuration and deployment by technology operations teams
    • D) As informal working notes that bypass contractual specification and formal sign-off during project execution
  3. 3.

    According to the TOGAF Standard, 10th Edition, how are documentation-based architecture deliverables typically managed upon the formal completion of an architecture project?

    • A) They are immediately refactored into Solution Building Blocks to directly guide operational deployment teams.
    • B) They are either archived or transitioned into the Architecture Repository as reusable reference models, specifications, or standards.
    • C) They are decomposed into atomic artifacts and permanently deleted from records management to avoid version divergence.
    • D) They are retained in an unapproved draft state across subsequent ADM cycles until an Architecture Board audit occurs.
  4. 4.

    An enterprise architecture team is defining the contractual work products required for formal review, stakeholder sign-off, and milestone governance during an enterprise transformation. According to the TOGAF Standard, 10th Edition, which work product correctly represents an architecture deliverable rather than an artifact or building block?

    • A) An Architecture Definition Document that consolidates core architectural models, rationale, and transition views for stakeholder approval.
    • B) A System/Technology Matrix that correlates business software applications with target cloud infrastructure platforms.
    • C) A centralized customer authentication service deployed as a reusable enterprise software component.
    • D) A Business Capability Catalog listing enterprise operational capabilities across functional business units.
  5. 5.

    According to the TOGAF Standard, 10th Edition, which statement correctly characterizes an architecture deliverable within the Architecture Content framework?

    • A) It is an individual architectural view rendered specifically as a catalog, matrix, or diagram to describe a single viewpoint.
    • B) It is a work product that is contractually specified and typically formally reviewed, agreed, and signed off by stakeholders.
    • C) It is a deployable physical component or software package procured to fulfill operational implementation specifications.
    • D) It is an informal working document maintained strictly for internal team collaboration without formal governance review.