Ücretsiz Kullanmaya Başla
PDF Downloads

Overview

Practitioner • TOGAF Content Framework and Enterprise Metamodel • Knowledge-Based • 5 questions

Overview Knowledge-Based Download PDF

TOGAF · Architecture Content · Practitioner · TOGAF Content Framework and Enterprise Metamodel

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

Questions

  1. 1.

    Within the TOGAF Standard, 10th Edition, how is the relationship between the Architecture Development Method (ADM) and the TOGAF Content Framework fundamentally defined?

    • A) The Content Framework specifies the sequential phases and governance gates used to execute the ADM.
    • B) The ADM defines the underlying semantic metamodel entities, while the Content Framework defines project management milestones.
    • C) The ADM defines the iterative process and activities for developing architecture, whereas the Content Framework defines the structural model for the work products and content produced by that process.
    • D) The Content Framework replaces the ADM by consolidating process guidelines into standard architecture repository templates.
  2. 2.

    Within the TOGAF Content Framework, how are Architecture Building Blocks (ABBs) fundamentally distinguished from Solution Building Blocks (SBBs)?

    • A) ABBs define the required functionality and architecture-driven specifications, whereas SBBs define the candidate or concrete implementations used to realize those specifications.
    • B) ABBs represent contractually signed-off deliverables produced for executive sponsors, whereas SBBs represent internal catalogs and matrices used solely by technical teams.
    • C) ABBs describe physical IT assets and commercially off-the-shelf software packages, whereas SBBs capture high-level strategic business goals and driver models.
    • D) ABBs are deployed exclusively during baseline architecture definition, whereas SBBs are defined solely during transition planning to decommission legacy systems.
  3. 3.

    When establishing an architecture practice based on the TOGAF Content Framework, what is the primary structural rationale for separating architectural metamodel concepts into a Core Content Metamodel and Metamodel Extensions?

    • A) It allows deliverables to be managed as informal work products while artifacts remain subject to formal configuration control and governance sign-off.
    • B) It establishes a minimal, coherent baseline of essential architectural concepts while offering modular, optional entity sets tailored to specific organizational depth or viewpoint needs.
    • C) It separates business architecture entities that are technology-agnostic from technical architecture entities that depend on specific physical vendor implementations.
    • D) It enforces a strict waterfall sequence in which core models must be baseline-approved across all ADM phases before any extension concepts can be instantiated.
  4. 4.

    In the TOGAF Standard, 10th Edition, what is the primary purpose of the Enterprise Metamodel within the TOGAF Content Framework?

    • A) It prescribes the exact governance committee structures and milestone approval gates required to transition architectural deliverables into operational projects.
    • B) It serves as a linear project lifecycle template that mandates the sequential execution and completion of ADM Phases A through H.
    • C) It specifies the physical data storage formats and schema definitions required to implement an Architecture Repository tooling solution.
    • D) It defines the types of architectural entities, their attributes, and the relationships between them to enable consistent structuring and cross-domain traceability of architecture content.
  5. 5.

    According to the TOGAF Content Framework, how is an architectural deliverable fundamentally distinguished from the architectural artifacts it contains?

    • A) A deliverable is an individual catalog, matrix, or diagram, whereas artifacts represent the overarching contractual package approved by stakeholders.
    • B) A deliverable is a contractually specified work product that is formally reviewed and signed off, typically encompassing multiple artifacts such as catalogs, matrices, and diagrams.
    • C) A deliverable represents an instantiated solution building block, whereas artifacts represent vendor-agnostic architecture building blocks.
    • D) A deliverable provides the underlying metamodel schema and entity relationships, whereas artifacts are the populated operational data instances.