Study guide

12.1 APO Strategy, Architecture, and Innovation

ISACA COBIT 2019 Foundation Certificate Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Certificate Rules, Retakes, and How to Study

2 Chapter 2: Framework Introduction

2.1 Purpose of COBIT and EGIT 2.2 I&T Versus the IT Function 2.3 COBIT 2019 Product Family 2.4 Stakeholders, Audience, and Benefits

3 Chapter 3: Framework Positioning

3.1 Umbrella Framework and Related Standards 3.2 Evolution from COBIT 5 to COBIT 2019

4 Chapter 4: Governance System Principles I

4.1 Provide Stakeholder Value 4.2 Holistic Approach 4.3 Dynamic Governance System

5 Chapter 5: Governance System Principles II and Framework Principles

5.1 Governance Distinct from Management 5.2 Tailored to Enterprise Needs 5.3 End-to-End Coverage 5.4 Three Governance Framework Principles

6 Chapter 6: Governance System Components Overview

6.1 Seven Governance System Components 6.2 Generic Versus Variant Components 6.3 Focus Areas

7 Chapter 7: Process and Structure Components

7.1 Processes Component 7.2 Practices, Activities, and Metrics 7.3 Organizational Structures 7.4 Principles, Policies, and Frameworks

8 Chapter 8: Information and People Components

8.1 Information Component 8.2 Culture, Ethics, and Behavior 8.3 People, Skills, and Competencies 8.4 Services, Infrastructure, and Applications

9 Chapter 9: Integrating Governance System Components

9.1 How Components Work Together 9.2 RACI Charts and Key Roles 9.3 Components Supporting Objectives

10 Chapter 10: The Goals Cascade

10.1 The Goals Cascade 10.2 Enterprise Goals and Alignment Goals

11 Chapter 11: Core Model and EDM Governance Objectives

11.1 The 40-Objective Core Model 11.2 EDM Governance Objectives 11.3 Governance Versus Management Objectives

12 Chapter 12: APO Align, Plan, and Organize

12.1 APO Strategy, Architecture, and Innovation 12.2 APO Portfolio, Resources, and Relationships 12.3 APO Risk, Security, Data, and Quality

13 Chapter 13: BAI, DSS, and MEA Management Objectives

13.1 BAI Build, Acquire, and Implement 13.2 DSS Deliver, Service, and Support 13.3 MEA Monitor, Evaluate, and Assess

14 Chapter 14: Performance Management

14.1 Performance Management Principles 14.2 Capability Levels 0–5 and Maturity

15 Chapter 15: Designing a Tailored Governance System

15.1 Why Tailor: Design Factors 15.2 The Eleven Design Factors 15.3 Design Workflow and Toolkit

16 Chapter 16: Business Case

16.1 Business Case for EGIT 16.2 Benefits, Costs, Risk, and Tracking

17 Chapter 17: Implementation Lifecycle

17.1 Implementation Lifecycle Overview 17.2 Seven Implementation Phases 17.3 Roles, Pain Points, and Challenges 17.4 Design Guide and Implementation Guide Together

12.1 APO Strategy, Architecture, and Innovation

Key Takeaways Explain This Topic AI

APO is the largest management domain: 14 objectives, all titled Managed, inside the 23% Governance and Management Objectives blueprint.

APO01 Managed I&T Management Framework designs and implements the I&T management system from enterprise goals and design factors.

APO02 Managed Strategy covers the current and future environment, digital maturity, and the I&T strategy and roadmap.

APO03 Managed Enterprise Architecture maintains business, information, data, application, and technology layers for baseline and target.

APO01 is the management system; EDM01 is the board ensuring the governance system. APO04 harvests innovation only when it still serves strategy.

Last updated: August 2026

Quick Answer: Align, Plan and Organize (APO) is the largest management domain in the COBIT 2019 40-objective core model : 14 objectives, all titled Managed . This section covers the first four. APO01 Managed I&T Management Framework designs and implements the I&T management system from enterprise goals and design factors. APO02 Managed Strategy describes the current and future environment, digital maturity, and the I&T strategy and roadmap. APO03 Managed Enterprise Architecture maintains business, information, data, application, and technology layers for both baseline and target. APO04 Managed Innovation harvests emerging-technology opportunities that still align to that strategy. APO01 is not EDM01 — the board ensures the governance system; management manages the I&T management system.

Governance and Management Objectives is 23% of the 75-question COBIT 2019 Foundation exam — roughly seventeen items. APO is the biggest slice of that domain because planning work is where enterprises either convert board direction into a coherent I&T system or scatter into unconnected projects. Memorize the official titles. Do not invent “Managed Suppliers,” do not drop APO14 , and do not slide APO01 into the board’s Evaluate, Direct and Monitor (EDM) column.

Where APO sits

Management’s verb set is plan, build, run, and monitor . APO is the plan domain. It takes EDM direction — enterprise goals, risk appetite, resource priorities — and turns it into a management system, a strategy, an architecture, an innovation pipeline, a portfolio, budgets, people, relationships, agreements, vendors, quality, risk, security, and data.

The four objectives in this section are the north-star cluster. If strategy, architecture, and innovation do not share one story, later portfolio and project work will fund yesterday’s estate.

The four official objectives

ID Official title One-sentence purpose

APO01 Managed I&T Management Framework Design and implement a consistent I&T management system — processes, structures, roles, repeatable activities, skills — from enterprise goals and design factors.

APO02 Managed Strategy Provide a holistic view of the current and future business and I&T environment, assess digital maturity, and produce an I&T strategy and roadmap.

APO03 Managed Enterprise Architecture Establish business, information, data, application, and technology architecture layers, with baseline and target models, standards, and reusable building blocks.

APO04 Managed Innovation Stay aware of I&T trends, identify innovation opportunities, and plan how emerging and existing technology will serve the defined I&T strategy.

Learn those four titles as a chain, not as four isolated flashcards.

APO01 Managed I&T Management Framework

APO01 is how management installs the operating system for I&T work. After the board, through EDM01 Ensured Governance Framework Setting and Maintenance , directs that an enterprise governance of information and technology (EGIT) system must exist, someone still has to design the management approach: process definitions, organizational structures, role descriptions, decision rights, skills, and repeatable ways of working. That someone is management, and that work is APO01.

Design factors matter here. A 40-person firm and a global insurer should not copy the same committee stack. APO01 takes enterprise goals and the 11 design factors and produces a management system that is consistent and tailored. “We printed the 40-objective poster” is not APO01. “We designed how I&T will actually be planned, built, run, and monitored here” is.

APO02 Managed Strategy

APO02 answers four exam-ready questions: Where are we now? Where is the environment going? How digitally mature are we? What roadmap gets us to the desired future?

The official purpose is a holistic view of the current business and I&T environment, the future direction, and the initiatives required to migrate. It includes a digital-maturity assessment and an I&T strategy and roadmap . Strategy here is not a slogan on a slide. It is the management artifact that later APO05 Managed Portfolio will use to accept or reject demand.

If a stem describes scanning competitors, rating digital maturity, and publishing a three-year I&T roadmap tied to enterprise goals, you are in APO02 — not in Build, Acquire and Implement (BAI) project delivery and not in EDM board appetite-setting.

APO03 Managed Enterprise Architecture

APO03 is the common architecture that keeps strategy from becoming a pile of disconnected systems. Official layers are:

  • Business — value streams, capabilities, and process architecture
  • Information — what information the enterprise needs
  • Data — how that information is structured and stored
  • Application — the systems that process it
  • Technology — platforms, infrastructure, and technical standards

APO03 maintains baseline (as-is) and target (to-be) architectures, plus taxonomy, standards, guidelines, templates, and reusable building blocks. The Foundation exam likes the layer list and the baseline/target pair. It also likes the purpose: alignment, agility, information quality, and cost savings from reuse — not “draw pretty diagrams after the vendor is already chosen.”

APO04 Managed Innovation

APO04 keeps the enterprise aware of I&T and service trends, finds innovation opportunities, and plans how to benefit from them in relation to business needs and the defined I&T strategy . Emerging technology, new services, I&T-enabled business innovation, and even new uses of existing technology all sit here. Innovation that ignores APO02 is a science fair. Innovation that never informs architecture becomes unmaintainable.

APO04 influences strategic planning and enterprise-architecture decisions. It does not replace them. A lab that pilots every vendor demo without a strategy filter is failing APO04, not “being agile.”

Scenario: Northline Mutual goes digital

Northline Mutual is a mid-size property-and-casualty insurer. The board has already done EDM work: it evaluated the threat from digital-direct competitors, directed a “claims in minutes” ambition inside a stated risk appetite, and asked for monitoring on benefit, risk, and resource signals. That is governance. Now management has to plan.

The chief information officer (CIO) starts with APO01 . Northline does not have a single I&T management system. Claims runs its own shadow tools, underwriting bought a rating engine on a corporate card, and corporate IT still thinks “governance” means the change-advisory board. APO01 designs one management approach: decision rights for product, data, and vendors; a lightweight process set tailored to an insurer of this size; role descriptions; and the skills the new model needs. The board did not write those role descriptions. Management did.

APO02 then produces the strategy. Current environment: a 20-year policy-administration core, paper-heavy claims, and a digital maturity that is “channel brochure, not channel product.” Future environment: mobile first-notice-of-loss, straight-through simple claims, and a fraud-scoring platform. The roadmap names three years of moves — not 40 equally important objectives, but a sequenced set of initiatives that APO05 will later prioritize against funding.

APO03 translates that roadmap into architecture. Baseline: the policy core, a claims desktop, a data warehouse that is really a dump, and a branch-centric network. Target layers are explicit. Business: a digital claims value stream. Information: a claimant and policy information model. Data: a governed claims data product, not another spreadsheet mart. Application: a claims service in front of the core, not a second core. Technology: a cloud landing zone with standards so every experiment does not invent a new platform. Without APO03, every squad will pick a different stack and call it innovation.

APO04 is how Northline stays current without becoming a gadget museum. A vendor pitches generative-AI claim summaries. Another pitches telematics. APO04 assesses those opportunities against the APO02 strategy and the APO03 target architecture. Telematics may wait; it does not serve “claims in minutes” this year. The AI summary tool may proceed as a bounded experiment because it fits the claims value stream and the data architecture. APO04 feeds both strategy (maybe the roadmap should add a language-model capability) and architecture (the target information layer now needs a model-governance building block).

The chain is the teaching point: strategy sets direction, architecture makes direction buildable, innovation keeps both honest about what is now possible. Reverse the chain — buy the gadget, then invent a strategy, then draw architecture as documentation — and you fail all four objectives at once.

APO01 is not EDM01

This is the highest-yield distinction in the section.

  • Lens EDM01 Ensured Governance Framework Setting and Maintenance APO01 Managed I&T Management Framework
  • Layer Governance Management
  • Who Board / governing body Executive management, including the CIO
  • Title tell Ensured Managed

Job Evaluate, direct, and monitor the governance system itself so EGIT stays designed, current, and fit Design and implement the I&T management system — processes, structures, roles, skills, repeatable activities

Typical artifact Decision that a tailored governance system will exist; oversight that it remains fit Process model, RACI, role catalog, management procedures tailored by design factors

Failure mode Board never asks whether the EGIT system itself works Management never installs a consistent way of working, so every team invents its own

If a stem says the board reviews whether the governance system still fits after a merger, that is EDM01. If it says the CIO designs the process and role model that will run I&T day to day, that is APO01. Same word “framework.” Different altitude.

Exam traps

Calling APO a governance domain. APO is management. Only EDM is governance.

Collapsing APO01 into EDM01. Governance system versus management system.

Skipping layers in APO03. Official layers are business, information, data, application, and technology. “Applications and infrastructure” is too thin.

Treating APO04 as unmanaged experimentation. Innovation is aligned to strategy, not a waiver from it.

Starting with projects. BAI11 Managed Projects delivers work packages. It does not set strategy or architecture.

Prefer the answer that keeps APO in the plan layer, keeps the four official titles intact, and refuses to let the CIO’s management system steal the board’s EDM01 job.

Loading diagram... APO01–APO04: management system, then strategy to architecture to innovation