Ücretsiz Kullanmaya Başla
PDF Downloads

TOGAF Enterprise Metamodel Vision

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

TOGAF Enterprise Metamodel Vision Knowledge-Based Download PDF

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

5 Practitioner practice questions on TOGAF Enterprise Metamodel Vision. Questions that assess core concepts and understanding.

Questions

  1. 1.

    In the TOGAF Enterprise Metamodel, how does the specification define the relationship between a Logical Application Component and a Physical Application Component?

    • A) A Logical Application Component represents the physical server deployment, whereas a Physical Application Component defines the abstract business logic executing on that server.
    • B) A Physical Application Component serves as a vendor-neutral functional design, which is subsequently decomposed into multiple Logical Application Components during migration planning.
    • C) A Logical Application Component defines an autonomous, vendor-independent packaging of application functionality, whereas a Physical Application Component represents the specific software product or executable deployable that realizes it.
    • D) A Logical Application Component models the persistent data schemas and data entities, whereas a Physical Application Component models the graphical user interface elements.
  2. 2.

    Within the TOGAF Enterprise Metamodel, how does the specification distinguish a Business Service from a Business Process?

    • A) A Business Service defines the sequence of internal tasks and state changes, whereas a Business Process defines the external governance constraints.
    • B) A Business Service encapsulates physical data storage mechanisms, whereas a Business Process orchestrates technological network nodes.
    • C) A Business Service represents an explicitly defined behavioral outcome exposed to consumers, whereas a Business Process orchestrates the internal activities and workflows that realize that service.
    • D) A Business Service represents an organizational business unit, whereas a Business Process represents an individual human actor performing a role.
  3. 3.

    According to the TOGAF Enterprise Metamodel, how is an Application Service positioned in relation to Application Components and Business Processes?

    • A) It represents an externally visible behavioral unit provided by an Application Component that automates or supports one or more Business Processes.
    • B) It defines the internal execution logic of a Business Process that must be physically embedded within an infrastructure Technology Node.
    • C) It acts as an organizational boundary entity that assigns direct operational ownership of Application Components to external business Stakeholders.
    • D) It serves as a persistent data structure that directly maps Logical Data Entities to underlying Technology Services.
  4. 4.

    According to the TOGAF Enterprise Metamodel Vision, how are Business Capabilities positioned to establish direct traceability between strategic intent and operational delivery?

    • A) They serve as the focal architectural constructs that realize Courses of Action, deliver stages of Value Streams, and are enabled by People, Processes, and Application Services.
    • B) They replace structural Organization Units and functional Processes to provide a purely technical specification for Application Components.
    • C) They act solely as runtime deployment boundaries that map Technology Services directly to strategic Drivers without operational intermediary constructs.
    • D) They are classified strictly as transient governance artifacts created within Phase F to record Work Package milestones.
  5. 5.

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

    • A) To prescribe an immutable physical database schema that all commercial Enterprise Architecture repository software must implement natively without modification
    • B) To enforce a proprietary graphical notation that supersedes industry-standard modeling languages such as ArchiMate, BPMN, and UML
    • C) To specify operational cost-accounting structures and project work breakdown packages governed exclusively by the Project Management Office
    • D) To establish a coherent, tailorable conceptual ontology of architecture entities and relationships that supports consistency, traceability, and cross-domain integrity across deliverables