Practice Free OGEA-103 Exam Online Questions
Question #61
Refer to the table below:

Which ADM Phase does this describe?
- A . Phase A
- B . Phase B
- C . Preliminary Phase
- D . Phase C
Correct Answer: B
B
Explanation:
Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.
B
Explanation:
Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.
Question #62
Complete the sentence. The “Statement” part of the recommended TOGAF template for Architecture Principles
- A . should highlight the requirements for carrying out the principle
- B . should highlight the business benefits
- C . should be easy to remember
- D . should clearly communicate the fundamental rule
Correct Answer: D
D
Explanation:
In TOGAF, when defining an architecture principle, one part of the standard template is the “Statement.” The purpose of the Statement is to convey clearly and unambiguously the principle itself ― not its rationale, implications, or how to apply it. The Statement should be phrased such that stakeholders can read it and immediately understand the core rule or guiding intent. It is not intended to describe the implementation or benefits or constraints, nor to be a mnemonic. Thus the Statement must clearly communicate the fundamental rule. The rationale, implications, and further explanation belong in other parts of the principle documentation, not in the Statement. This division helps maintain clarity, separation of concerns, and consistency in how principles are documented and governed.
D
Explanation:
In TOGAF, when defining an architecture principle, one part of the standard template is the “Statement.” The purpose of the Statement is to convey clearly and unambiguously the principle itself ― not its rationale, implications, or how to apply it. The Statement should be phrased such that stakeholders can read it and immediately understand the core rule or guiding intent. It is not intended to describe the implementation or benefits or constraints, nor to be a mnemonic. Thus the Statement must clearly communicate the fundamental rule. The rationale, implications, and further explanation belong in other parts of the principle documentation, not in the Statement. This division helps maintain clarity, separation of concerns, and consistency in how principles are documented and governed.
Question #63
Which section of the TOGAF template for Architecture Principles should highlight the requirements for carrying out the principle?
- A . Rationale
- B . Name
- C . Statement
- D . Implications
Correct Answer: D
D
Explanation:
The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.
The other sections of the TOGAF template for Architecture Principles are1:
• Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.
• Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.
• Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.
Reference: 2: The TOGAF Standard, Version 9.2 – Architecture Principles 3: TOGAF 8.1.1 Online – Architecture Principles 1: Architecture Principles Template
D
Explanation:
The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.
The other sections of the TOGAF template for Architecture Principles are1:
• Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.
• Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.
• Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.
Reference: 2: The TOGAF Standard, Version 9.2 – Architecture Principles 3: TOGAF 8.1.1 Online – Architecture Principles 1: Architecture Principles Template
Question #64
Complete the sentence The purpose of the Preliminary Phase is to_____________.
- A . describe the target architecture
- B . define the enterprise strategy
- C . identify the stakeholders and their requirements
- D . architect an Enterprise Architecture Capability
Correct Answer: D
D
Explanation:
The purpose of the Preliminary Phase is to architect an Enterprise Architecture Capability that meets the needs and expectations of the enterprise’s stakeholders and supports and enables subsequent phases of architecture development and transition. This phase involves defining the scope, principles, framework, and governance for the Enterprise Architecture Capability.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.
D
Explanation:
The purpose of the Preliminary Phase is to architect an Enterprise Architecture Capability that meets the needs and expectations of the enterprise’s stakeholders and supports and enables subsequent phases of architecture development and transition. This phase involves defining the scope, principles, framework, and governance for the Enterprise Architecture Capability.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.
Question #64
Complete the sentence The purpose of the Preliminary Phase is to_____________.
- A . describe the target architecture
- B . define the enterprise strategy
- C . identify the stakeholders and their requirements
- D . architect an Enterprise Architecture Capability
Correct Answer: D
D
Explanation:
The purpose of the Preliminary Phase is to architect an Enterprise Architecture Capability that meets the needs and expectations of the enterprise’s stakeholders and supports and enables subsequent phases of architecture development and transition. This phase involves defining the scope, principles, framework, and governance for the Enterprise Architecture Capability.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.
D
Explanation:
The purpose of the Preliminary Phase is to architect an Enterprise Architecture Capability that meets the needs and expectations of the enterprise’s stakeholders and supports and enables subsequent phases of architecture development and transition. This phase involves defining the scope, principles, framework, and governance for the Enterprise Architecture Capability.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.
