TOGAF Enterprise Architecture Part 2 Exam - Practitioner Free Sample Questions

According to TOGAF, principles should be robust and complete. When principles conflict (e.g., stability vs. innovation), the framework relies on the trade-off analysis inherent in the principle's Rationale and Implications sections. Creating separate sets creates silos, while prioritizing one set universally undermines the other. The architecture governance process uses these defined implications to resolve specific scenarios.

The Preliminary Phase is responsible for defining the 'where, what, why, who, and how' of the architecture capability. This includes tailoring the ADM and defining how it interfaces with other enterprise frameworks such as Project Management (PMBOK), Operations, and Strategy.

The Standards Information Base (SIB) within the Architecture Repository captures the standards with which the new architecture must comply. This includes industry standards, regulatory obligations, and internal governance standards regarding data sovereignty and control in the cloud.

The Enterprise Continuum provides a method for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures. It structures the Architecture Repository.

False. The Architecture Capability Framework is a set of guidelines, structures, and processes for establishing and operating an architecture function within an enterprise. It is not a set of vertical industry reference models.

Defining the organizational model helps clarify roles, responsibilities, and the value proposition of architecture governance. Without a clear governance framework established in the Preliminary Phase, stakeholders will not understand or respect the engagement model.

In the Power/Interest grid, High Power / Low Interest stakeholders should be 'Kept Satisfied'. You do not want to bore them with details (Keep Informed) or ignore them (Monitor), but you must ensure they don't use their power to negatively impact the project.

Business Scenarios are a technique used to help identify and understand the business requirements and thereby to derive the business requirements that the architecture must support. They are excellent for surfacing conflicts between goals (speed vs. security) and facilitating a trade-off discussion based on business value.

A Stakeholder Map should identify who the key stakeholders are, their roles, and their responsibilities/interests regarding the architecture effort.

Categorizing stakeholders into classes (often derived from Power/Interest analysis) is a critical part of the mapping process to determine engagement strategy.

A Security Architecture Viewpoint is specifically designed to address concerns related to security, risk, compliance, and data protection, which aligns directly with the CISO's role.