โ† All TOGAF Flashcard Decks

Enterprise Architecture Flashcards

7 cards from real TOGAF practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Enterprise Architecture flashcards as text
  1. What neither constitutes an enterprise architecture component nor a domain?

    Answer: Service Oriented Architecture

    Explanation: Service Oriented Architecture (SOA) is actually a component and a domain of enterprise architecture. It is an architectural approach that emphasizes the design, development, and use of services to enable the integration and interoperability of different systems within an enterprise. SOA provides a framework for organizing and aligning various IT resources and applications to support business processes and goals.

  2. Which of the following best describes the enterprise architecture's main objective?

    Answer: All of the above is correct

    Enterprise Architecture's objective encompasses all the listed goals: maximizing organizational efficiency and effectiveness, increasing business and IT agility, and aligning business and IT strategies. Since each option is a legitimate part of EA's overarching purpose, "All of the above" is correct.

  3. Which of the following frameworks represents best practices for creating enterprise architecture?

    Answer: Togaf

    Explanation: The best practice framework for developing enterprise architecture is indeed TOGAF (The Open Group Architecture Framework). TOGAF is a widely recognized and widely adopted framework that provides a structured approach for designing, planning, implementing, and managing enterprise architecture. It offers a comprehensive set of methods, guidelines, and tools that organizations can use to develop and maintain their enterprise architecture.

  4. How many ADM phases or processes are there?

    Answer: 10

    TOGAF's Architecture Development Method (ADM) consists of 10 phases: the Preliminary Phase plus Phases A through H (Architecture Vision, Business, Information Systems, Technology, Opportunities & Solutions, Migration Planning, Implementation Governance, and Architecture Change Management), with Requirements Management at the center. The other counts (11, 12, 13) overstate the number of phases.

  5. Which of the following describes the ADM sequence's initial steps or phases?

    Answer: Preliminary/Requirement management

    Explanation: The correct first step/phase in the ADM sequence is the Preliminary Phase. The Preliminary Phase is the starting point of the ADM and involves activities such as establishing the enterprise architecture team, defining the scope of the enterprise architecture effort, identifying stakeholders, and establishing governance processes. It sets the foundation for the subsequent phases of the ADM, including requirement management, by establishing the necessary organizational structure and understanding the context of the architecture work.

  6. Which of the following describes the final stage or phase of the ADM sequence?

    Answer: Architecture Change Management

    Explanation: Architecture Change Management is not one of the last steps/phases in the ADM (Architecture Development Method) sequence. The final phase in the ADM is typically Phase G: Implementation Governance, which focuses on overseeing the implementation of the architecture and ensuring that it aligns with the architectural vision and requirements. This phase involves monitoring the implementation progress, managing risks and issues, and providing guidance and support to stakeholders involved in the implementation.

  7. Which of the following is not a preliminary ADM architecture concept example?

    Answer: Acquire new system and technology i the market every year

    Explanation: "Acquire new system and technology in the market every year" is not an example of an architecture principle in the ADM preliminary phase. Architecture principles are fundamental guidelines and rules that inform the decision-making process during the development of enterprise architecture. They help ensure consistency, coherence, and alignment with the organization's goals and strategies.