Licensing Models and Entitlement Management
The Licensing Landscape
Candidates must recognize the major licensing constructs and how each is measured. Per-device and per-user licenses tie entitlement to a named person or machine. Concurrent licensing caps simultaneous users, not named users. Processor/core-based licensing (common for server and database products) scales with physical cores and often requires a core factor table. Named-user plus subscription models (SaaS) bill per seat per period. Also understand CAL (client access license) models, per-instance limits, and virtualization rules such as license mobility and dedicated-host requirements.
Entitlement Management
An entitlement is proof of the right to use software: a purchase order, contract, certificate, or subscription record. Entitlement management means maintaining a license repository with quantity, metric, term, and constraints (edition downgrade rights, geographic restrictions, affiliate eligibility). Traps include counting a perpetual license as covering future versions when Software Assurance or subscription has lapsed, and confusing maintenance with right-to-upgrade.
Worked Example
A vendor sells a server product licensed per core with a 0.5 core factor for a specific processor family. A host with 16 physical cores, two sockets, and that processor family yields 16 × 0.5 = 8 licenses. If the host is virtualized across a cluster, licensing may apply to every host in the cluster unless the cluster is dedicated. Always confirm the metric before calculating quantity.
Exam Traps
Do not assume virtual machines reduce licensing. Do not treat a quote as an entitlement. Do not assume unlimited virtualization rights without documented contract language.