Home / enterprise-architecture-it-governance / ISACA Certified in the Governance of Enterprise IT (CGEIT) / Cheat Sheet
ISACA Certified in the Governance of Enterprise IT (CGEIT)

CGEIT Cheat Sheet

CGEIT Tests Board-Level IT Governance Judgment — Not IT Management Execution

CGEIT is for senior leaders who direct and oversee enterprise IT. Pick what a governing body or steering committee would own: evaluate, direct and monitor, with business owners accountable for value and risk.

Check Your Readiness →
Among the harder certs
Avg: Not published by ISACA
Pass: 750 / 1000
Most candidates understand ISACA Certified in the Governance of Enterprise IT (CGEIT) concepts — and still fail. This exam tests how you apply knowledge under pressure.

CGEIT Job Practice Domains (2020 outline)

150 questions in four hours, written from the board or executive viewpoint. Stems often ask what to do FIRST or what is BEST; the right option usually establishes alignment, accountability or an assessment before any technical fix. The 2020 outline remains current, with no update announced.

  1. 01
    Governance of Enterprise IT (40%) — governance framework, COBIT 2019 design factors, goals cascade, decision rights, strategy, information ownership, culture
  2. 02
    IT Resources (15%) — sourcing and outsourcing, contracts and SLAs, exit strategy, asset inventory, TCO, people and competencies
  3. 03
    Benefits Realization (26%) — business cases, stage gates, benefit owners, NPV and payback, performance measurement, independent assurance
  4. 04
    Risk Optimization (19%) — appetite, tolerance and capacity, risk owners and responses, KRIs, the enterprise risk register

Wrong instinct vs correct approach

Two business units demand priority for competing IT projects and escalate to the CEO
✕ Wrong instinct

Ask the board to choose between the two projects

✓ Correct approach

Portfolio prioritization belongs to the IT steering committee, working within strategy and criteria the board approved. Score both against enterprise goals and their business cases; the board sets direction and monitors, it does not arbitrate projects.

Residual risk for a cloud migration is already within the board's stated risk appetite
✕ Wrong instinct

Add further controls to reduce the risk anyway

✓ Correct approach

When residual risk sits within appetite, the risk owner can formally accept it. Extra controls waste resources and may block value; risk optimization balances value delivered against risk taken.

An outsourced provider's monthly dashboards are all green, yet business users keep complaining about service
✕ Wrong instinct

Terminate the contract and switch providers

✓ Correct approach

Verify performance independently first through audits, assurance reports or internal measurement, then check that SLAs reflect business requirements. Termination without verification and an executable exit plan can cause more disruption than the underperformance.

The board says IT reports are too long and it cannot see which decisions are needed
✕ Wrong instinct

Add more detailed metrics to the board pack

✓ Correct approach

Governance reporting should be concise, in business terms, linked to enterprise goals and focused on exceptions and decisions. An IT balanced scorecard with lead and lag indicators gives that view.

Know these cold

  • ▸ Governance evaluates, directs and monitors; management plans, builds, runs and monitors within that direction
  • ▸ COBIT 2019 governance objectives sit in the EDM domain; Val IT principles now live in EDM02
  • ▸ Goals cascade — takeholder drivers, enterprise goals, alignment goals, then governance and management objectives
  • ▸ A RACI chart allows exactly one Accountable party for each activity
  • ▸ Risk capacity exceeds board-set appetite; tolerances are measurable thresholds management works within
  • ▸ Risk transfer or insurance leaves accountability, reputation and regulatory exposure with the enterprise
  • ▸ Compare residual risk with appetite; inherent risk exists before any controls apply
  • ▸ NPV reflects time value; payback ignores benefits after recovery; simple ROI usually ignores timing
  • ▸ Information owner decides classification and access; steward maintains quality; custodian implements controls
  • ▸ IT risks belong in the enterprise risk register so the board sees aggregated exposure

Can you answer these without checking your notes?

In this scenario: "Two business units demand priority for competing IT projects and escalate to the CEO" — what should you do first?
Portfolio prioritization belongs to the IT steering committee, working within strategy and criteria the board approved. Score both against enterprise goals and their business cases; the board sets direction and monitors, it does not arbitrate projects.
In this scenario: "Residual risk for a cloud migration is already within the board's stated risk appetite" — what should you do first?
When residual risk sits within appetite, the risk owner can formally accept it. Extra controls waste resources and may block value; risk optimization balances value delivered against risk taken.
In this scenario: "An outsourced provider's monthly dashboards are all green, yet business users keep complaining about service" — what should you do first?
Verify performance independently first through audits, assurance reports or internal measurement, then check that SLAs reflect business requirements. Termination without verification and an executable exit plan can cause more disruption than the underperformance.

Common Exam Mistakes — What candidates get wrong

Holding the CIO or project manager accountable for business benefits

Benefits are realized through business use, so the business executive named as benefit owner is accountable. Project managers answer for delivery at go-live; realization is measured over time against a baseline captured before the change.

Continuing a failing program because most of the budget is spent

Money already spent is sunk. At a stage gate the choices are continue, change, pause or stop, judged only on future costs and benefits against the business case, with the benefit owner and steering committee deciding.

Letting the IT manager or CISO accept residual risk

Only the business risk owner with authority can accept risk on the enterprise's behalf, and acceptance is documented. The board sets risk appetite; management works within measurable tolerances, all below the enterprise's risk capacity.

Answering a governance gap with adopting COBIT across the enterprise

COBIT 2019 must be tailored using design factors such as enterprise strategy, risk profile, compliance needs, sourcing model and size. An untailored framework does not fix the specific accountability or alignment gap the scenario describes.

Treating outsourcing as a transfer of accountability

Execution moves to the provider; accountability for outcomes and compliance stays with the enterprise. Hence contracts need a right to audit, SLAs reflecting business requirements, independent assurance such as SOC 2 Type II, and an exit strategy agreed before signing.

Resources to help you pass ISACA CGEIT on your first attempt

CGEIT asks what the board and its committees should own. Check whether your answers stay at governance level.