Overview of Enterprise Architecture and the TOGAF Standard
What EA and TOGAF actually are
Enterprise architecture (EA) is the fundamental organisation of an enterprise - its people, processes, information and technology - together with the principles and roadmap that govern how it changes. TOGAF's purpose is to provide a method and a framework for developing, maintaining and using EA. It is explicitly a framework to be tailored, never a prescriptive methodology that must be applied verbatim.
Know the shape of the TOGAF Standard, 10th Edition: TOGAF Fundamental Content (core concepts; the ADM; ADM Guidelines and Techniques; Architecture Content; EA Capability and Governance; Architecture Views, Viewpoints and Visualization) plus TOGAF Series Guides that show how to apply the core in specific contexts such as digital transformation, business capability and agile.
Around the ADM sit three supporting notions that appear in almost every exam set: the Enterprise Continuum (Architecture Continuum plus Solutions Continuum, classifying assets from generic to organisation-specific), the Architecture Repository (where assets are stored, catalogued and governed), and the Architecture Capability (roles, skills, processes, tools and governance that let architecture be practised at all).
Traps: questions swap the Continuum (a classification scheme, generic to specific) with the Repository (storage plus the governance log); they imply TOGAF mandates one fixed set of deliverables rather than a tailorable set; they present the ADM as strictly waterfall despite TOGAF's explicit endorsement of iteration; and they attribute generic EA benefits to the standard itself. Remember too that TOGAF is vendor- and technology-neutral and complements - does not replace - frameworks such as ITIL, COBIT or PMBOK.
Rule of thumb: if the wording is 'reusable, from generic to specific', think Continuum; if it is 'stored, catalogued, governed', think Repository.