What is present in all phases within the ADM and should be identified, classified and mitigated before starting a transformation effort?
Correct Answer: B
According to the TOGAF Standard, 10th Edition, risk is present in all phases within the Architecture Development Method (ADM), and it should be identified, classified, and mitigated before starting a transformation effort 1. Risk is defined as "the effect of uncertainty on objectives" 2, and it can have positive or negative impacts on the architecture project. Risk management is a technique that helps to assess and address the potential risks that may affect the achievement of the architecture objectives, and to balance the trade-offs between opportunities and threats. Risk management is applied throughout the ADM cycle, from the Preliminary Phase to the Requirements Management Phase, and it is integrated with other techniques, such as stakeholder management, business transformation readiness assessment, gap analysis, and migration planning 1. The other options are not correct, as they are not present in all phases within the ADM, and they are not necessarily identified, classified, and mitigated before starting a transformation effort. Budgetary constraints are the limitations on the financial resources available for the architecture project, and they are usually considered in Phase E: Opportunities and Solutions, and Phase F: Migration Planning 3. Schedule constraints are the limitations on the time available for the architecture project, and they are also usually considered in Phase E and F 3. Information gaps are the missing or incomplete data or knowledge that may affect the architecture project, and they are usually identified in Phase B: Business Architecture, Phase C: Information Systems Architecture, and Phase D: Technology Architecture . References: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 16: Phase E: Opportunities and Solutions, and Chapter 17: Phase F: Migration Planning. : TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 13: Phase B: Business Architecture, Chapter 14: Phase C: Information Systems Architecture, and Chapter 15: Phase D: Technology Architecture.
Question 47
Complete the sentence. The key purpose of Gap Analysis is to _____
Correct Answer: B
Gap Analysis is a technique that compares the Baseline Architecture and the Target Architecture to identify the differences and gaps between them. The purpose of this technique is to determine the changes and additions that are required to achieve the desired future state of the architecture. One of the main aspects of Gap Analysis is to identify the functions that are missing or overlapping in the current and future architectures, and to plan how to address them. This helps to ensure that the architecture is complete, consistent, and aligned with the business objectives and requirements3
Question 48
Which of the following statements about architecture partitioning are correct*? 1 Partitions are used to simplify the management of the Enterprise Architecture 2 Partitions are equivalent to architecture levels 3 Partitions enable different teams to work on different element of the architecture at the same time. 4 Partitions reflect the organization's structure
Correct Answer: B
Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization's structure, which may change over time or differ from the architecture's scope and boundaries. Reference: The TOGAF Standard | The Open Group Website, Section 2.5 Architecture Partitioning.
Question 49
Consider the following statements about Architecture Partitioning: * The TOGAF ADM requires a partitioning model for architecture development * Architectures are partitioned when different teams need to work on different elements of the architecture at the same time * Partitions can be used to facilitate architecture re-use Which statements are correct?
Correct Answer: D
Comprehensive and Detailed Explanation Architecture Partitioning is an ADM technique in TOGAF that addresses how large and complex architectures can be broken down into manageable parts. The intent is to make architecture development more effective, especially in large enterprises with multiple teams, stakeholders, and domains. Key points from TOGAF: * TOGAF does not mandate a partitioning model. It provides guidelines and techniques to help architects determine whether and how to partition. This means statement 1 is incorrect. * Statement 2: Correct. Architectures may be partitioned to allow different teams to work on different elements in parallel (e.g., by domain, line of business, geographic scope). Partitioning provides clear ownership and reduces overlap or conflict. * Statement 3: Correct. Partitions can be structured in a way that supports architecture re-use, since well-defined partitions (e.g., capability-based or domain-based) enable consistent re-use of architecture building blocks across projects. Correct Mapping * Statement 1: Incorrect (partitioning is not required by ADM). * Statement 2: Correct. * Statement 3: Correct. Correct answer is D (2 and 3). Why the other options are incorrect * A (1, 2 and 3): Incorrect because TOGAF does not require partitioning. * B (1 and 3): Incorrect because 1 is not correct. * C (1 and 2): Incorrect because 1 is not correct. References * The Open Group, TOGAF Standard, Version 9.2, Part III: ADM Guidelines & Techniques - Architecture Partitioning. * The Open Group, TOGAF 9 Certified Study Guide - coverage of partitioning and its uses in large- scale architecture development.
Question 50
What can architects present to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture?
Correct Answer: D
According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1. An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1. Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23: Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs. Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context. Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements, ensuring that they are balanced and prioritized in the architecture design and decision-making. Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance. 1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders 2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework? 3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section 31.1: Basic Concepts
