TOGAF

Describe how the TOGAF Standard's Fundamental Content and Series Guides relate to the wider TOGAF Library.

Summarize the objective and principal result of each Architecture Development Method phase.

Select the appropriate ADM phase for a stated architecture activity.

Explain how Requirements Management supports every ADM phase.

Distinguish iteration between ADM cycles, across ADM phases, and within an ADM phase.

Choose an appropriate architecture level and degree of detail for a stated enterprise context.

Distinguish deliverables, artifacts, building blocks, views, and viewpoints in TOGAF Architecture Content.

Use the Enterprise Continuum to classify reusable architecture assets and locate them within the Architecture Repository.

Assess an organization's baseline architecture capability using people, skills, processes, governance, and information criteria.

Explain the purpose and key outputs of the Preliminary Phase.

Define organizational scope and architecture partitioning for an architecture engagement.

Formulate an architecture principle with a statement, rationale, and practical implications.

Tailor the ADM to the case study's scale, governance, delivery methods, and constraints.

Design an architecture governance structure with clear decision rights and escalation paths.

Model the relationships among stakeholders, drivers, goals, requirements, building blocks, and work packages using a fit-for-purpose Enterprise Metamodel.

Create a requirements register that supports ownership, prioritization, status management, and traceability.

Create a stakeholder map using influence, interest, concerns, and required engagement.

Select architecture viewpoints that address specific stakeholder concerns and explain how the resulting views will be used.

Apply the Business Scenarios technique to clarify a transformation problem and its desired outcomes.

Define the breadth, depth, time horizon, and domain coverage of an architecture engagement.

Draft an Architecture Vision that connects drivers, outcomes, scope, and constraints.

Define measurable business outcomes and success indicators for the transformation.

Develop a value proposition that supports executive approval of the architecture work.

Draft the core scope, approach, and governance sections of a Statement of Architecture Work.

Map baseline organizational units, actors, and core business processes.

Construct a business capability map for the case-study enterprise.

Model a value stream that connects customer value to enabling business capabilities.

Apply capability-based planning to identify maturity gaps that obstruct the transformation outcomes.

Document the target business architecture for roles, processes, organization, capabilities, and governance.

Perform a business architecture gap analysis between the baseline and target states.

Derive traceable architecture requirements from identified business architecture gaps.

Validate the target business architecture against stakeholder concerns and measurable business outcomes.

Document the baseline data landscape by identifying key data entities, owners, authoritative sources, locations, and flows.

Define target data ownership and governance responsibilities for shared enterprise information.

Model the target lifecycle, authoritative sources, and movement of a critical data entity across business capabilities.

Document the baseline application portfolio and its significant dependencies.

Define target application services and interactions that support the target business and data architectures.

Evaluate application rationalization options against business value, cost, risk, and strategic fit.

Specify data and application requirements for interoperability, data protection, privacy, and application security.

Perform Data and Application Architecture gap analyses and record the resulting requirements.

Document baseline technology services, platforms, locations, standards, and dependencies.

Derive hybrid-platform security, identity, privacy, and compliance requirements from a technology risk assessment.

Specify architecture requirements for availability, resilience, backup, disaster recovery, performance, and observability.

Define target technology services and standards that support the target business, data, and application architectures.

Design a conceptual identity and access architecture with explicit trust boundaries for the hybrid environment.

Design a conceptual connectivity and integration pattern spanning on-premises systems, Azure, and Microsoft 365.

Evaluate candidate Azure, Microsoft 365, and on-premises solution building blocks against documented architecture criteria.

Perform a Technology Architecture gap analysis and record its requirements and roadmap implications.

Consolidate cross-domain gaps into a non-duplicative set of transformation needs.

Generate and compare solution options and work packages that address the consolidated gaps.

Use readiness and implementation-factor assessments to identify transformation risks and derive planning actions.

Define a transition architecture by grouping mutually dependent work packages into a viable transformation increment.

Map dependencies among work packages, capabilities, applications, data, and technology changes.

Prioritize work packages using business value, cost, risk, dependencies, and organizational readiness.

Create an Architecture Roadmap showing work packages, transition states, milestones, and expected outcomes.

Draft an Implementation and Migration Plan aligned with the Architecture Roadmap.

Define an Architecture Contract that clarifies delivery obligations and conformance expectations.

Define governance checkpoints that align architecture decisions with project, product, Agile, and operational delivery.

Plan an architecture compliance review using explicit criteria and required evidence.

Evaluate a delivery design for conformance with the approved architecture and requirements.

Classify and manage architecture deviations, dispensations, and corrective actions.

Trace architecture requirements from approved designs through implementation and operational evidence.

Assess a change request for its impact on architecture, requirements, risks, and the transformation roadmap.

Classify an architecture change and determine whether it requires maintenance, partial ADM work, or a new ADM cycle.

Assemble a coherent Architecture Definition Document by selecting and reconciling the case study's baseline, target, gap, and requirements artifacts.

Build a stakeholder-specific architecture briefing using appropriate views and levels of detail.

Justify an architecture trade-off using business outcomes, principles, requirements, cost, and risk.

Align TOGAF architecture governance with Agile, product, project, and DevOps delivery methods.

Diagnose a transformation scenario by identifying the relevant ADM phase, stakeholder concern, technique, and expected output.

Answer Foundation-style questions by applying TOGAF terminology and core concepts and explaining why plausible distractors are incorrect.

Answer Practitioner-style scenario questions by navigating the permitted TOGAF reference materials and justifying the best response.

Use an exam-error log to diagnose missed questions and plan targeted remediation.