The Open Group OGBA-101 Online Practice Questions and Exam Preparation

The Open Group OGBA-101 Online Questions & Answers

• Question 51:

  Which of the following is a purpose of mapping capabilities to value stream stages?

  A. To identify and eliminate business capabilities that do not contribute to the business.
  B. To classify, group, and align capabilities into categories for a deeper understanding.
  C. To describe the business in terms of services provided and consumed.
  D. To provide a self-contained business description that is independent of the organizational structure.
  B. To classify, group, and align capabilities into categories for a deeper understanding.

  ---

  Explanation

  One of the purposes of mapping capabilities to value stream stages is to classify, group, and align capabilities into categories for a deeper understanding of how they support value creation and delivery2. By mapping capabilities to value stream stages, the architect can identify which capabilities are required for each stage of the value stream, how they relate to each other, and how they contribute to the overall value proposition. This can help to assess the maturity, effectiveness, performance, and value or cost contribution of each capability.

• Question 52:

  Which of the following is a benefit of developing a TOGAF business scenario?

  A. It provides a versatile approach to business planning.
  B. It can be an important aid to vendors in delivering appropriate solutions.
  C. It provides an organizing framework for the change activity in a project.
  D. It provides general rules and guidelines to support planning at the enterprise level.
  B. It can be an important aid to vendors in delivering appropriate solutions.

  ---

  Explanation

  Developing a TOGAF business scenario provides several benefits, particularly in aiding vendors to deliver appropriate solutions. Here's a detailed explanation:

  TOGAF Business Scenarios:

  Business scenarios are used to capture and describe business requirements, helping to identify and understand business needs and challenges.

  Role in Vendor Engagement:

  Clarity of Requirements: Business scenarios provide clear and detailed descriptions of the business context, needs, and requirements. This helps vendors understand what solutions are necessary to address specific business challenges.

  Alignment of Solutions: By providing a comprehensive view of the business environment and requirements, business scenarios ensure that the solutions proposed by vendors are aligned with the actual business needs and strategic goals.

  TOGAF ADM

  References:

  Phase A: Architecture Vision: In this phase, business scenarios are developed to capture stakeholder concerns and requirements, providing a basis for the architecture vision. Vendor Communication: Business scenarios are communicated to

  vendors to ensure that their solutions fit within the overall architecture and meet the specific requirements of the business.

  Benefits:

  Effective Solution Design: Vendors can design solutions that are tailored to the specific needs of the business, reducing the risk of misalignment and ensuring better outcomes. Improved Collaboration: Business scenarios facilitate better

  collaboration between the enterprise and vendors by providing a common understanding of the requirements and expected outcomes.

  In summary, developing a TOGAF business scenario aids vendors in delivering appropriate solutions by providing clear and detailed descriptions of business requirements, ensuring alignment with business needs and strategic goals.

• Question 53:

  What are the four architecture domains that the TOGAF standard deals with?

  A. Baseline, Candidate, Transition, Target
  B. Capability, Segment, Enterprise, Federated
  C. Business, Data, Application, Technology
  D. Application, Data, Information, Knowledge
  C. Business, Data, Application, Technology

  ---

  Explanation

• Question 54:

  Consider the diagram.

  

  What are the items labelled A, B and C?

  A. A-Enterprise Strategic Architecture, B-Segment Architecture, C-Solutions Architecture
  B. A-Enterprise Continuum, B-Architecture Continuum. C-Solutions Continuum
  C. A-Architecture Vision, B-Business Architecture. C-lnformation Systems Architecture
  D. A-Enterprise Architecture, B-Architecture Building Blocks, C-Solutions Building Blocks
  B. A-Enterprise Continuum, B-Architecture Continuum. C-Solutions Continuum

  ---

  Explanation

  The diagram shows the Enterprise Continuum, which is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures4. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum. The Architecture Continuum shows the relationships among foundational frameworks, common system architectures, industry architectures, and enterprisearchitectures4. The Solutions Continuum shows the relationships among foundational solutions, common system solutions, industry solutions, and enterprise solutions4.

• Question 55:

  Which of the following is the element of a value stream stage that describes the end state condition denoting the completion of the value stream stage?

  A. Target state
  B. Exit criteria
  C. Completion stage
  D. End point
  B. Exit criteria

  ---

  Explanation

  In TOGAF's Business Architecture, a value stream stage is a high-level representation of a sequence of activities that create value for an organization. The end state condition denoting the completion of a value stream stage is known as the "Exit Criteria." This term is used to specify the conditions that must be met for the stage to be considered complete, ensuring that the output meets the required quality and performance standards before progressing to the next stage. The concept of "Exit Criteria" is essential to ensure that each stage of the value stream adds the expected value and aligns with the overall business objectives.

• Question 56:

  Consider the following:

  In Phase A a business capability map and a core set of value streams were created while developing the Architecture Vision.

  Why would such Architecture Descriptions need to be updated in Phase B?

  A. Phase B requires that all Architecture Descriptions be updated.
  B. The development of Business Architecture Descriptions is always iterative.
  C. Phase B is an ADM Architecture Development phase.
  D. A new value stream was assessed as in the project scope.
  B. The development of Business Architecture Descriptions is always iterative.

  ---

  Explanation

  The development of Business Architecture Descriptions is always iterative because it involves constant refinement and validation of the architecture models and views based on stakeholder feedback and changing requirements. Therefore, any Architecture Description that was created in Phase A may need to be updated in Phase B as new information or insights emerge. Phase B does not require that all Architecture Descriptions be updated, only those that are relevant and necessary for the Business Architecture. Phase B is an ADM Architecture Development phase, but that does not explain why Architecture Descriptions need to be updated. A new value stream may or may not require updating existing Architecture Descriptions depending on its scope and impact.

  In TOGAF's ADM, the development of architecture is an iterative process. During Phase A, initial business capability maps and value streams are created to establish the Architecture Vision. However, as stakeholders provide more detailed inputs and requirements are refined, it isnecessary to update the Architecture Descriptions. This is an iterative process that continues into Phase B, Business Architecture, where these descriptions are further developed and refined.

• Question 57:

  What can architects present to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture?

  A. Business Scenarios and Business Models
  B. Alternatives and Trade-offs
  C. Solutions and Applications
  D. Architecture Views and Architecture Viewpoints
  A. Business Scenarios and Business Models

  ---

  Explanation

  Business Scenarios and Business Models are tools that architects can present to stakeholders to facilitate discussions that reveal underlying assumptions, agendas, principles, and requirements. They help in understanding the context, extracting and validating requirements, and identifying potential impacts on the target architecture. By discussing scenarios and models, stakeholders can express their vision and concerns, which may include unspoken or implicit needs that are crucial for the architecture's success.

• Question 58:

  Which of the following is an analysis technique which is used to show a range of different perspectives on the same set of business capabilities?

  A. Capability decomposition
  B. Heat mapping
  C. Relationship mapping
  D. Information mapping
  B. Heat mapping

  ---

  Explanation

  Heat mapping is an analysis technique used to provide a visual representation of data, often to show performance against a set of criteria. In the context of business capabilities, heat maps can be used to represent various dimensions such as maturity levels, investment priorities, risk levels, etc., on the same set of business capabilities. This allows different stakeholders to quickly grasp where attention is needed or how capabilities align with strategic priorities.

• Question 59:

  Which of the following best describes information mapping?

  A. A technique to represent business information assets in use, or planned by the enterprise.
  B. A technique to create a maturity model for information management.
  C. A technique to construct a baseline description of the structure and interaction of information assets that support key business functions.
  D. A technique to construct a high level description of the informational requirements of a business.
  A. A technique to represent business information assets in use, or planned by the enterprise.

  ---

  Explanation

  Information mapping in TOGAF is a technique used to represent business information assets that are either currently in use or planned for future use by the enterprise. Here's a detailed explanation:

  Purpose of Information Mapping:

  Information mapping provides a clear visualization of how information flows within the enterprise, highlighting the information assets and their interactions. This is crucial for understanding the current state and planning the future state of

  information management.

  TOGAF Framework:

  Phase C: Information Systems Architectures: Within this phase, information mapping is used to develop the Data Architecture, which outlines the structure of an organization's logical and physical data assets and data management resources.

  Supporting Analysis: Information mapping supports various analyses, including gap analysis, impact analysis, and the identification of information dependencies and redundancies.

  Benefits:

  Clear Representation: It provides a clear and structured representation of business information assets, aiding in the understanding and management of information flows. Alignment with Business Processes: Helps ensure that information

  assets are aligned with business processes and objectives, enhancing the efficiency and effectiveness of information usage.

  Components:

  Current Information Assets: Information mapping identifies and catalogs the information assets currently in use within the enterprise. Planned Information Assets: It also includes planned information assets that will be needed to support future

  business processes and strategies.

  In summary, information mapping is a technique to represent business information assets in use or planned by the enterprise, providing a structured view of information flows and supporting effective information management.

• Question 60:

  Consider the following example using the Business Model Canvas:

  

  What are the segments labeled A, D and I?

  A. Customer Relationships, Value Propositions, Market Segments.
  B. Customer Segments, Value Add Services, Profit Channels.
  C. Key Partners, Customer Relationships, Revenue Streams.
  D. Key Resources. Revenue Streams. Cost Structure
  C. Key Partners, Customer Relationships, Revenue Streams.

  ---

  Explanation

  The segments labeled A, D and I in the Business Model Canvas are Key Partners, Customer Relationships, and Revenue Streams respectively. The Business ModelCanvas is a tool that can be used to describe how an organization creates, delivers, and captures value for its stakeholders. The Business Model Canvas consists of nine segments that cover four main areas: customers (segments B,C,D), offer (segment E), infrastructure (segments A,F,G), and financial viability (segments H,I). The segments are defined as follows:

  Key Partners (segment A): The network of suppliers and partners that make the business model work. Key partners can provide resources, activities, or support that enable the organization to offer its value proposition. Customer Relationships (segment D): The type of relationship that the organization establishes with its customer segments. Customer relationships can be driven by customer acquisition, retention, or loyalty objectives. Customer relationships can also

  influence the customer experience and satisfaction.

  Revenue Streams (segment I): The sources of income that the organization generates from each customer segment1. Revenue streams can be derived from different pricing mechanisms, such as asset sale, subscription, fee, commission, or

  advertising1. Revenue streams can also reflect the value that customers are willing to pay for the organization's offer.