TOGAF Enterprise Metamodel Vision Knowledge-Based Practice

Questions

1. 1.

   According to the TOGAF Enterprise Metamodel vision, how does the metamodel fundamentally delineate between architectural specification and concrete implementation across the architecture lifecycle?

   • A) By defining vendor-neutral logical entities that specify Architecture Building Blocks (ABBs), which are later realized by concrete Solution Building Blocks (SBBs) during solution delivery.
   • B) By restricting all entity definitions to physical deployment artifacts, thereby eliminating abstract logical representations from the Architecture Repository.
   • C) By replacing high-level architecture building blocks with operational configuration management database (CMDB) records prior to Phase A.
   • D) By mandating that each logical business service permanently binds to a single proprietary technology product regardless of target state iterations.
2. 2.

   According to the TOGAF Enterprise Metamodel vision, which statement correctly characterizes the relationship between metamodel entities and architecture deliverables such as catalogs, matrices, and diagrams?

   • A) Deliverables and artifacts provide the primary authoritative data definitions, whereas metamodel entities represent secondary abstractions maintained strictly for cross-framework translation.
   • B) Deliverables and artifacts represent stakeholder-specific viewpoints projected from underlying metamodel entities and relationships, ensuring changes to architecture data propagate consistently across representations.
   • C) Each artifact must map exclusively to an isolated metamodel entity to prevent cross-domain dependencies from emerging during architecture development cycles.
   • D) Catalogs and matrices are formally governed by metamodel concepts, whereas graphical diagrams remain outside the metamodel scope to accommodate proprietary modeling notations.
3. 3.

   When structuring an Architecture Repository to evaluate the downstream impact of proposed strategic changes, how does the TOGAF Enterprise Metamodel fundamentally enable end-to-end traceability across disparate architectural domains?

   • A) By mandating a universal modeling grammar that replaces domain-specific notations across all enterprise modeling tools
   • B) By defining standardized entity types and formal relationship semantics that link concepts across business, data, application, and technology layers
   • C) By prescribing a rigid hierarchy of document deliverables that teams must compile during each phase of the ADM
   • D) By providing automated code generation rules that directly translate strategic drivers into executable runtime infrastructure components
4. 4.

   According to the TOGAF Enterprise Metamodel vision, how does the structural distinction between Core and Extension entities enable an organization to balance enterprise-wide consistency with domain-specific depth?

   • A) By mandating that domain-specific extensions replace core entities whenever detailed technical requirements exceed strategic scope
   • B) By establishing a mandatory, universal baseline of essential architectural concepts while permitting modular, specialized extensions tailored to specific stakeholder concerns
   • C) By restricting enterprise repository definitions solely to motivation and business layers while delegating technology entities to external implementation frameworks
   • D) By requiring all modeling notations to map directly to extensions, thereby reserving core entities exclusively for governance and compliance artifacts
5. 5.

   When tailoring the Architecture Content Framework for an organization that utilizes multiple domain-specific modeling notations, what is the primary role of the TOGAF Enterprise Metamodel?

   • A) It enforces a proprietary, mandatory notation across all architectural domains to eliminate the need for specialized external standards.
   • B) It prescribes the operational execution runtime configurations required for deployment across multi-cloud infrastructure environments.
   • C) It provides a formal ontology of core architectural concepts and relationships that establishes consistent traceability across domain-specific models.
   • D) It serves as a static catalog of predefined technology products to standardize software procurement decisions.

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