I85PREP
⌘ K
GAA study materials
GAA study resources

GAA: IT Asset Management Fundamentals and Governance

GAA · Work through your exam, one topic at a time.

All guide sections

IT Asset Management Fundamentals and Governance

What the exam tests

IT Asset Management (ITAM) Fundamentals and Governance covers the vocabulary, scope, and control structure every other domain depends on: what counts as an asset, how the asset register relates to the CMDB, which policies and roles make ITAM enforceable, and how governance keeps data trustworthy over time.

Core rules

  • An asset is anything with financial or operational value the organization must track and control - hardware, software entitlements, cloud subscriptions, and in some scopes data and contracts. A configuration item (CI) is anything that must be managed to deliver a service. Assets and CIs overlap but are not the same set.
  • ISO/IEC 19770-1 frames ITAM as a management system built on governance, discovery, and continual improvement; ITIL 4 places asset and configuration management inside the service value chain.
  • Governance needs a documented policy, named accountable owners (RACI), and a decision body that resolves conflicts between cost, risk, and service.
  • The asset register is a financial and contractual record; the CMDB is a relationship model. Both should draw on the same discovery and procurement data, but they answer different questions.

Worked example

An organization has 5,000 endpoints. The asset register holds 4,700 records; the CMDB holds 5,400 CIs. Neither number is wrong. The register excludes 300 devices bought by business units outside procurement, while the CMDB counts virtual instances and a few non-capitalized CIs. The analyst reconciles by serial number, flags 180 unmatched records as data-quality defects, and assigns owners to close them within 30 days. The lesson: define the entity model before arguing about the count.

Traps that cost marks

  • Treating asset management as a tool purchase rather than a governed process.
  • Assuming a 1:1 mapping between assets and CIs.
  • Leaving licenses, subscriptions, and contracts out of scope because they are intangible.
  • No executive sponsor, so policy exceptions are never enforced.