TOGAF Architecture Governance Flashcards
6 cards from real TOGAF practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 6 TOGAF Architecture Governance flashcards as text
What are the four levels of the Architecture Governance hierarchy in TOGAF?
Answer: Corporate, IT, Architecture, Design
TOGAF describes four governance levels: Corporate Governance, IT Governance, Architecture Governance, and Design Governance, each with increasing specificity.
What is the purpose of an 'Architecture Compliance Review' in the ADM?
Answer: To assess conformance of a project's architecture with the enterprise architecture
An Architecture Compliance Review formally assesses whether a project's architecture conforms to the enterprise architecture standards and principles.
What categories of compliance outcomes can result from an Architecture Compliance Review?
Answer: Irrelevant, Consistent, Compliant, Conformant, Fully Conformant, Non-conformant
TOGAF defines compliance outcomes ranging from Irrelevant (architecture doesn't apply) through degrees of conformance to Non-conformant (fails to meet requirements).
What is the role of the 'Chief Architect' or 'Lead Architect' in TOGAF governance?
Answer: To chair the Architecture Board and oversee the architecture governance process
The Lead/Chief Architect typically chairs the Architecture Board and is responsible for overseeing the architecture governance process and ensuring architecture quality.
In TOGAF, what triggers an Architecture Compliance Review during the ADM?
Answer: A project reaching a defined milestone, typically before implementation begins
Architecture Compliance Reviews are triggered at defined project milestones, typically at key checkpoints before major implementation phases begin.
What is 'Architecture Debt' in the context of TOGAF governance?
Answer: The accumulated divergence between the defined target architecture and actual implementations
Architecture Debt refers to the accumulated gap between the defined target architecture and the actual implemented architecture, representing technical and governance debt.