Software Licensing, IT Assets and Subscription Economics

Introduction and Context

Software and hardware are no longer acquired through a single, easily identifiable purchase. An organisation may own servers, lease laptops, subscribe to cloud platforms, consume software through APIs, license products per user, or obtain rights that vary according to geography, processor capacity, data volume, or business function. Consequently, IT costing and procurement require more than comparing supplier prices. They require an integrated understanding of legal rights, technical deployment, financial commitments, operational usage, and governance.

Software licensing is the contractual mechanism by which a supplier grants defined rights to use software. The customer normally does not acquire ownership of the software intellectual property. IT asset management (ITAM) establishes what technology assets exist, who is responsible for them, where they are located, how they are configured, what rights have been acquired, and when they should be retired. Subscription economics examines recurring commitments, usage variability, renewal exposure, and the relationship between price and realised business value.

Weak control in these areas creates several risks: compliance penalties, unnecessary expenditure, service disruption at renewal, unsupported equipment, cybersecurity exposure, duplicated tools, and dependence on a supplier from which migration is difficult. Effective practice integrates procurement, finance, legal, information security, architecture, service management, and business ownership.

Learning Objectives

By the end of this chapter, a student should be able to:

1. Distinguish major software licensing and subscription models.
2. Relate contractual entitlements to technical installations, users, devices, and consumption.
3. Design practical software and hardware asset controls.
4. Calculate total cost, recurring commitment, utilisation, and renewal economics.
5. Plan audit evidence and respond to non-compliance findings.
6. Evaluate optimisation opportunities, shadow IT, switching costs, and vendor lock-in.
7. Recommend governance arrangements that balance compliance, agility, cost, and user productivity.

1. The Licensing and Asset Management System

A useful conceptual model separates five related but different objects:

• Asset: A physical or virtual item controlled by the organisation, such as a laptop, server, virtual machine, or cloud resource.
• Software product: The supplier’s technical product, edition, version, and components.
• Entitlement: The contractual right to use a product under specified conditions.
• Deployment or consumption: The actual installation, activation, access, or resource usage.
• Business service: The organisational capability supported by the technology.

A compliance problem occurs when deployment or consumption exceeds entitlement. A cost problem may occur even when the organisation is compliant—for example, when many purchased licences are unused. A security problem may occur when an asset is not recorded or is running unsupported software. These are distinct conditions and should not be confused.

A mature control environment maintains a relationship such as:

Supplier contract → entitlement record → deployment or usage evidence → assigned owner → business service → financial treatment

The relationship must be sufficiently precise to support decisions. A generic record stating “office software: 1,000 licences” is less useful than a record specifying product edition, metric, territory, contract dates, downgrade rights, reassignment rules, included support, renewal price, and current assignments.

Important terminology

Licence metric is the unit used to measure permitted use, such as named user, concurrent user, device, processor, core, capacity, transaction, or storage volume. Entitlement is the quantity and scope purchased. Installation is the technical presence of software; it is not always equivalent to use. Activation is the supplier-recognised enablement of a licence. Consumption is measured use, often relevant to cloud or API services. True-up is a contractual or commercial adjustment for additional use. True-down is a reduction in recurring quantity where the agreement permits it. Maintenance commonly provides support and updates for perpetual licences. Subscription provides time-limited rights, usually with recurring payment. Renewal continues rights after the current term. End of life is the point after which a product or version is no longer supported by the supplier.

2. Major Licensing Models

2.1 Perpetual licensing

A perpetual licence grants continuing rights to use a specified version or product, subject to contractual restrictions. The initial purchase may be accompanied by annual maintenance. Perpetual licensing can be economically attractive where usage is stable over a long period and the organisation can operate the software without frequent upgrades. However, it may require substantial upfront capital, create upgrade costs, and leave the customer responsible for infrastructure and support if maintenance ends.

A perpetual licence is not necessarily unrestricted. It may prohibit transfer, limit installation to a specified number of devices, restrict use to a legal entity, or define how virtualisation is counted. A perpetual right also does not guarantee access to every future version.

2.2 Subscription licensing

A subscription grants use for a defined period, commonly monthly or annually. It normally includes updates and may include support, hosting, identity integration, or service-level commitments. Subscription expenditure is often treated as operating expenditure, although accounting treatment depends on the arrangement and applicable standards. Managers should not assume that a subscription is financially cheaper merely because its initial payment is smaller.

Subscriptions create renewal concentration risk. If a critical service is renewed automatically, a missed notice period can extend the commitment. Procurement records should therefore capture notice dates, price-escalation clauses, minimum commitments, service credits, data-return provisions, and termination assistance.

2.3 User-based models

A named-user licence is assigned to a particular person. It is appropriate where an individual requires access across several devices. A unique-user metric counts distinct authorised users, whereas a named-user metric may require explicit assignment. A concurrent-user model limits the number of simultaneous users and may be efficient for shift-based or intermittent work, but it requires reliable measurement.

User licensing becomes difficult when contractors, temporary workers, shared accounts, service accounts, subsidiaries, and external collaborators are involved. Identity governance should align joiner, mover, and leaver processes with licence assignment and revocation.

2.4 Device-based models

A device licence permits use on a specified workstation, terminal, server, or other device. It may be preferable where many people share a small number of workstations. The main control challenge is identifying the device consistently across replacement, virtual desktop, mobile, and laboratory environments.

2.5 Capacity, processor, and core models

Enterprise software may be licensed by processor, physical core, virtual core, server, or a supplier-defined capacity unit. These metrics are technically complex because virtualisation, clustering, partitioning, failover, and disaster-recovery environments may affect the count. The contract, not a general industry assumption, determines how the metric is calculated.

2.6 Consumption and transaction models

Cloud platforms, data services, APIs, and security products may charge according to compute time, storage, data transfer, requests, records, messages, or processed data. Consumption pricing can align cost with demand but makes budgets sensitive to workload growth, architecture, and inefficient configuration.

For a simple usage-priced service:

where C_total is total cost for the period, F is any fixed charge, q_i is quantity consumed in category i, and p_i is the price per unit in that category. The formula assumes categories are mutually defined and prices are known for the applicable tier. Taxes, credits, minimum commitments, and currency effects must be added or modelled separately.

2.7 Open-source and source-available software

Open-source software is distributed under licences that grant specified rights, often including use, modification, and redistribution. Licences differ materially. Permissive licences generally impose limited conditions, while copyleft licences may require distribution of derivative works under specified terms. “Open source” does not mean “without obligations” or “without cost.” Costs may arise from security review, integration, support, compliance, and employee time.

Source-available products may provide access to source code but impose restrictions inconsistent with recognised open-source definitions. Procurement, legal, and engineering teams must examine the actual licence text and dependencies rather than rely on marketing labels.

3. Subscription Economics and Total Cost of Ownership

Price comparison should include the complete economic commitment. Total cost of ownership (TCO) for a technology option may include acquisition, implementation, integration, migration, operation, support, security, training, internal labour, exit, and residual value. A compact planning expression is:

where the terms represent acquisition, implementation, integration, operation, support, exit costs, and residual value respectively. The expression is a decision model rather than a universal accounting rule. Costs must be defined consistently over the same time horizon and should not double-count items.

For alternatives with payments occurring at different times, discounted cash flow is more appropriate. The net present value (NPV) of costs can be represented as:

where C_t is the cash cost in period t, r is the discount rate per period, and t begins at 0 or 1 according to the chosen timing convention. The formula assumes a constant discount rate and cash flows measured in the same currency and period. A lower NPV cost is not automatically the better decision: functionality, risk, resilience, compliance, and strategic value also matter.

Worked example: perpetual versus subscription

An organisation evaluates a three-year requirement for 100 users.

• Perpetual option: licence purchase of £480 per user, annual maintenance of £96 per user, and an implementation cost of £12,000.
• Subscription option: £22 per user per month and implementation cost of £6,000.
• Ignore tax, discounting, residual value, and differences in functionality.

Perpetual three-year cost:

Licence purchase = 100 × £480 = £48,000.

Maintenance = 100 × £96 × 3 = £28,800.

Total = £48,000 + £28,800 + £12,000 = £88,800.

Subscription three-year cost:

Subscription = 100 × £22 × 36 = £79,200.

Total = £79,200 + £6,000 = £85,200.

Under these assumptions, the subscription is £3,600 cheaper over three years. The conclusion could change if the perpetual licences remain usable after year three, if subscription prices rise, or if the two options differ in support, functionality, security, or exit cost.

Utilisation and optimisation metrics

A basic utilisation rate is:

where N_used is the number of genuinely active users or units and N_entitled is the number purchased. The metric is meaningful only when “used” is defined—for example, at least one meaningful activity in the preceding 90 days. A login alone may not demonstrate business value.

For a subscription with fixed and variable charges, average cost per active user may be estimated as:

where C_period is cost in the period and N_active is the defined active-user count. This measure can be misleading when users have materially different service tiers or when one user generates substantial consumption.

Optimisation actions include reclaiming licences from leavers, downgrading users, changing assignment rules, consolidating duplicate products, using reserved capacity where demand is stable, scheduling non-production environments, and renegotiating minimum commitments. Optimisation must not remove licences needed for resilience, segregation of duties, accessibility, legal retention, or emergency response.

4. IT Asset Management and Control Architecture

ITAM is a lifecycle discipline, not merely an inventory spreadsheet. Its lifecycle normally includes demand, acquisition, receipt, configuration, deployment, operation, transfer, repair, retirement, disposal, and evidence retention.

4.1 Hardware controls

A controlled hardware record should include asset identifier, serial number, model, owner, custodian, location, purchase or lease details, warranty, encryption status, operating system, configuration, lifecycle state, and disposal evidence. Discovery tools can identify devices, but discovery data must be reconciled with procurement and finance records. Automated discovery may miss powered-off, isolated, personal, or unmanaged devices.

Key controls include:

• approval before purchase;
• standard catalogue and approved configurations;
• serial-number verification at receipt;
• asset tagging and custody acknowledgement;
• encryption and endpoint management before release;
• periodic reconciliation of inventory to network and identity data;
• controlled transfer, repair, and loan procedures;
• secure data erasure or destruction at disposal;
• evidence of disposal and chain of custody.

4.2 Software asset controls

Software asset management (SAM) combines contract interpretation, entitlement records, discovery, usage analytics, deployment control, and optimisation. A robust SAM repository links the supplier, contract, product, metric, quantity, term, cost centre, owner, installations, assignments, and renewal dates.

A reconciliation should answer three questions:

1. What rights has the organisation acquired?
2. What installations, assignments, or consumption have occurred?
3. Do the rights cover the observed use under the contract’s rules?

The answer may require normalising product names, editions, versions, bundles, suites, downgrade rights, and product use rights. A deployment tool that reports 800 installations cannot by itself establish non-compliance if the contract measures active users or allows multiple installations per user.

4.3 Configuration management and financial records

The configuration management database (CMDB) describes configuration items and their relationships to services. The asset register focuses on ownership, lifecycle, and financial or accountability information. They may exchange data but should not be assumed to be identical. Finance may require capitalisation, lease, depreciation, or expense information, while operations requires dependency and status information.

5. Audits, Evidence and Compliance Response

A supplier audit may be contractual, routine, triggered by acquisition, or initiated after suspected overuse. Organisations should prepare continuously rather than reconstruct evidence under pressure.

An audit-ready evidence pack may include:

• executed agreements, amendments, order forms, and product terms;
• entitlement and purchase records;
• deployment, assignment, and consumption reports;
• identity and access records;
• virtualisation and infrastructure topology;
• records of mergers, divestments, and legal-entity scope;
• support and maintenance history;
• exception approvals and remediation records;
• disposal and decommissioning evidence.

A defensible audit process establishes scope, date, metric interpretation, data owners, validation rules, and treatment of uncertainty. Results should distinguish confirmed excess use, probable excess use, data-quality gaps, and legitimate use not yet evidenced.

Organisations should avoid deleting records or changing configurations merely to conceal exposure. Such actions may worsen legal and ethical risk. Instead, they should preserve evidence, obtain legal advice where necessary, correct controls, and negotiate remediation transparently. Remediation could involve purchase of additional rights, removal of unneeded deployments, contract amendment, or a combination.

6. Procurement and Renewal Governance

Procurement should begin with a requirements and rights analysis, not a supplier quotation. A statement of requirements should specify users, devices, environments, expected demand, security controls, integration, data location, availability, support, exit, and compliance obligations.

A contract review should examine:

• licence metric and counting rules;
• permitted entities, territories, affiliates, and contractors;
• assignment, reassignment, and transfer rights;
• virtualisation, backup, disaster recovery, and test environments;
• audit rights, notice, cost allocation, and confidentiality;
• price escalation, currency, minimums, tiers, and overage rates;
• automatic renewal and notice periods;
• service levels, remedies, credits, and support tiers;
• data ownership, portability, deletion, and return formats;
• subcontracting, security, privacy, and regulatory duties;
• termination assistance and transition services.

Renewal management should operate as a staged process. At least several months before renewal, the owner should confirm actual usage, forecast demand, business criticality, alternatives, security posture, unresolved incidents, and exit feasibility. A renewal decision should be based on the value and risk of continuing, not on administrative inertia.

A useful renewal scorecard can combine utilisation, business criticality, switching effort, supplier performance, security risk, and commercial terms. Scores should support judgement rather than replace it. High utilisation does not justify renewal if the service has unacceptable security risk; low utilisation does not automatically justify cancellation if the capability is essential for rare but critical events.

7. Shadow IT, Ethical Issues and Vendor Lock-in

Shadow IT is technology acquired or used without appropriate organisational approval. It can arise because formal procurement is slow, approved tools are unavailable, or teams seek rapid innovation. It may expose confidential information, create unrecorded contractual obligations, duplicate existing capability, and prevent reliable cost forecasting.

A punitive-only response is often ineffective. Better governance combines discovery, education, rapid approval pathways, approved alternatives, data classification, identity controls, and proportionate sanctions. Cloud access security tools, expense analysis, DNS or proxy data, identity logs, and employee surveys can help identify unapproved services, but monitoring must respect privacy, employment law, and legitimate purpose limitations.

Vendor lock-in exists when switching supplier is costly, slow, risky, or technically difficult. Sources include proprietary data formats, specialised interfaces, unique skills, embedded workflows, long-term discounts, regulatory approvals, and dependency on supplier-specific services. Lock-in is not always undesirable: specialisation may create significant value. The managerial issue is whether dependence is deliberate, understood, and economically justified.

Lock-in mitigation includes open standards, documented interfaces, export testing, modular architecture, multi-cloud or hybrid options where justified, staff capability development, escrow or continuity arrangements, termination assistance, and periodic exit exercises. Multi-sourcing can reduce concentration but may increase integration and governance costs. Therefore, resilience architecture should be evaluated on total risk and cost, not on the number of suppliers alone.

8. A Detailed Illustrative Case: Northbridge University

Background

Northbridge University, a fictional institution, has 18,000 students, 2,400 staff, research laboratories, and a hybrid cloud environment. It uses a productivity suite, specialist research software, endpoint security, cloud storage, and several departmental SaaS applications. Procurement records are centralised, but departments can purchase low-value cloud services using payment cards.

Problem

The university faces a 12-month renewal for its productivity suite. It has 3,000 purchased seats but only 2,350 staff and approved contractors. A preliminary report shows 2,780 assigned accounts, 420 accounts with no meaningful activity for 90 days, and 160 guest accounts. Departments also use 27 unrecorded SaaS tools. The supplier proposes an 8% price increase and a three-year minimum commitment.

Analysis

The university forms a cross-functional team from ITAM, procurement, finance, information security, legal, academic administration, and research services. It first normalises identities, distinguishes staff from guests and service accounts, and defines active use as at least one business-relevant activity in the previous 90 days. It validates whether shared mailboxes and emergency accounts require special treatment.

The team finds that 190 leavers still have assigned licences, 140 users have premium features they do not use, and 75 research accounts are funded by external grants with contractual retention requirements. The 27 shadow services include duplicate project-management and file-sharing tools, but three support legitimate research collaborations requiring external access.

Approach and solution

The university removes or suspends licences for leavers, downgrades suitable users, and establishes automatic joiner-mover-leaver integration. Guest accounts are placed under a separate policy. It does not remove research accounts until grant and retention requirements are verified. The procurement team negotiates a smaller base commitment with quarterly adjustment rights, a price cap, data export obligations, and a longer notice period.

Each shadow service receives one of three decisions: migrate to an approved platform, formally approve with a business owner and security review, or retire after data export. A lightweight intake process is introduced so researchers can request exceptions without bypassing governance.

Outcome

The university reduces its initial commitment from 3,000 to 2,550 seats, with a controlled growth band. It eliminates duplicate tools, improves leaver deprovisioning, and obtains clearer exit and data-return terms. The result is not simply a licence reduction: it is improved evidence, lower security exposure, and greater visibility of legitimate exceptions.

Learning points

1. Assignment counts are not automatically equivalent to genuine use.
2. Optimisation must preserve legal, research, accessibility, and continuity requirements.
3. Shadow IT often reveals unmet user needs; eliminating symptoms without improving service design encourages recurrence.
4. Renewal negotiation is stronger when supported by validated usage data.
5. Contract flexibility and exit rights may be more valuable than a small initial discount.

9. Contemporary Developments and AI

Cloud-native services increasingly combine subscription and consumption economics. FinOps practices therefore complement ITAM by allocating cloud costs to products, teams, environments, and business outcomes. Tagging, budgets, anomaly detection, unit-cost measures, and engineering accountability are useful, but allocation models should remain understandable and auditable.

Artificial intelligence introduces distinctive licensing questions. Organisations must determine whether model access is priced by seat, token, input and output volume, throughput, fine-tuning, or infrastructure consumption. They should examine rights to submit organisational data, training and retention practices, output ownership, acceptable use, human oversight, and supplier changes to model availability. A low per-user price may conceal substantial token or data-processing costs.

Automated discovery and AI-assisted contract analysis can improve scale, but they do not replace legal interpretation or accountable judgement. Models may misclassify products, overlook amendments, or infer usage from incomplete data. Human review, provenance, access controls, testing, and documented confidence levels remain necessary.

10. Challenges and Limitations

No asset-management system provides perfect truth. Discovery tools can produce false positives; contracts can contain ambiguous language; users may share credentials; cloud consumption can change rapidly; and suppliers may alter product bundles. Data quality problems often arise at organisational boundaries, during mergers, and when departments use different naming conventions.

Metrics can also distort behaviour. A target to reduce licence count may encourage unsafe sharing or removal of necessary resilience capacity. A target to maximise utilisation may discourage occasional but strategically important capabilities. Effective governance therefore uses balanced measures, including compliance exposure, realised value, security posture, service reliability, user experience, and exit readiness.

Best-Practice Framework

A practical operating model includes:

1. Policy: Define authority, approved acquisition routes, exceptions, ownership, and evidence requirements.
2. Inventory: Maintain authoritative or reconciled records for hardware, software, contracts, identities, and services.
3. Control: Integrate procurement, identity, endpoint, configuration, finance, and disposal processes.
4. Measure: Track entitlement, deployment, consumption, utilisation, unit cost, renewals, and supplier performance.
5. Optimise: Reclaim, downgrade, consolidate, schedule, renegotiate, or redesign where justified.
6. Assure: Conduct internal reviews, audit readiness checks, security assessments, and lifecycle inspections.
7. Improve: Learn from exceptions, shadow IT, incidents, failed renewals, and exit exercises.

Chapter Summary

Software licensing defines contractual rights, while IT asset management records and controls the physical, virtual, software, and service assets through their lifecycles. Perpetual, subscription, user, device, capacity, and consumption models create different financial, technical, and compliance consequences. Entitlement, deployment, assignment, and consumption must be reconciled using the contract’s actual metric.

Subscription decisions should evaluate total cost of ownership, timing of cash flows, utilisation, price escalation, renewal exposure, and exit cost. Hardware and software controls require accurate inventories, accountable owners, lifecycle procedures, identity integration, secure disposal, and audit evidence. Renewal governance must begin before the contractual deadline and should consider value, risk, security, switching cost, and data portability.

Shadow IT is both a governance risk and an indicator of unmet organisational demand. Vendor lock-in may be strategically acceptable when understood and controlled, but organisations should preserve portability and test their ability to exit. Modern cloud and AI services make usage measurement, cost allocation, data governance, and human oversight increasingly important.

Key Terms

Asset: A physical, virtual, software, or service resource controlled by an organisation.

Entitlement: Contractual right to use a product under stated conditions.

Licence metric: Unit used to measure permitted use.

Perpetual licence: Licence granting continuing use rights, usually for a specified version.

Subscription: Time-limited right to use a product or service for recurring payment.

Named user: Licence assigned to a specified individual.

Concurrent user: Licence measured by simultaneous users.

Device licence: Right associated with a specified device or endpoint.

Consumption pricing: Charging based on measured usage such as storage, requests, or compute.

Software asset management: Governance of software contracts, rights, deployments, usage, and optimisation.

IT asset management: Lifecycle management of technology assets and accountability information.

Utilisation rate: Used quantity divided by entitled quantity, expressed as a percentage.

True-up: Adjustment for additional use or quantity.

True-down: Permitted reduction in recurring quantity.

Renewal: Continuation of a contract or subscription after its current term.

Shadow IT: Technology used without appropriate organisational approval or visibility.

Vendor lock-in: Dependence that makes changing suppliers costly or difficult.

Total cost of ownership: Complete cost of acquiring, operating, supporting, and exiting a solution.

Review Questions

Short Answer Questions

1. Distinguish an entitlement from a deployment.
2. State two differences between perpetual and subscription licensing.
3. Why should a CMDB not automatically be treated as the complete asset register?
4. Identify three items that should be reviewed before a subscription renewal.
5. What is shadow IT, and why is it a governance concern?

Long Answer Questions

1. Explain how named-user, concurrent-user, device, and consumption licensing affect control design and cost management.
2. Describe an end-to-end software asset management process from procurement through retirement.
3. Discuss the advantages and limitations of subscription economics compared with perpetual licensing.
4. Explain how an organisation can prepare for and respond to a supplier software audit.
5. Evaluate the relationship between vendor lock-in, portability, architecture, and procurement strategy.

Analytical / Application Questions

1. An organisation has 1,200 entitled users, 1,050 assigned users, and 900 users with meaningful activity in the last 90 days. Calculate the assignment rate and activity-based utilisation rate, and explain why the distinction matters.
2. Design a renewal decision framework for a critical cloud service whose price is increasing, usage is variable, and data migration would take 12 months.
3. Using the Northbridge University case, propose three controls that reduce shadow IT without preventing legitimate research innovation.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes an entitlement from a deployment?

A. An entitlement is a contractual right, while a deployment is actual technical installation or use.

B. An entitlement is always a physical asset, while a deployment is always a financial record.

C. An entitlement measures supplier profit, while a deployment measures tax.

D. There is no meaningful distinction between the two terms.

Correct Answer: A. An entitlement is a contractual right, while a deployment is actual technical installation or use.

Question 2

Which licensing model charges according to measured use such as storage, API requests, or compute time?

A. Perpetual licensing

B. Device licensing

C. Consumption licensing

D. Named-user licensing

Correct Answer: C. Consumption licensing

Question 3

An organisation has 500 entitled users and 425 users with meaningful activity. What is the activity-based utilisation rate?

A. 75%

B. 80%

C. 85%

D. 90%

Correct Answer: C. 85%

Question 4

Which item is most directly associated with reducing vendor lock-in?

A. Removing all contract records

B. Testing data export and maintaining documented interfaces

C. Increasing dependence on proprietary formats

D. Preventing all supplier-specific functionality

Correct Answer: B. Testing data export and maintaining documented interfaces

Question 5

What is the principal purpose of reconciling entitlements with deployments and consumption?

A. To ensure that use is covered by contractual rights and identify unused capacity

B. To replace all financial accounting processes

C. To guarantee that every user has premium functionality

D. To eliminate the need for supplier contracts

Correct Answer: A. To ensure that use is covered by contractual rights and identify unused capacity

Question 6

Which is an appropriate hardware asset control?

A. Allowing disposal without evidence

B. Recording serial number, custodian, location, lifecycle state, and disposal evidence

C. Relying only on employee memory

D. Deleting the asset record when the device is repaired

Correct Answer: B. Recording serial number, custodian, location, lifecycle state, and disposal evidence

Question 7

In the simple cost expression C_total = F + ∑(q_i × p_i), what does F represent?

A. The fixed charge

B. The quantity consumed

C. The price per unit

D. The residual value

Correct Answer: A. The fixed charge

Question 8

Why may an organisation retain a low-utilisation licence?

A. Because low utilisation always proves high value

B. Because it may support rare but critical, legal, research, or continuity requirements

C. Because unused licences cannot be audited

D. Because utilisation is irrelevant to all licensing decisions

Correct Answer: B. Because it may support rare but critical, legal, research, or continuity requirements

Question 9

Which practice is most appropriate when responding to suspected licensing non-compliance?

A. Destroying usage evidence

B. Concealing installations until the audit ends

C. Preserving evidence, validating the interpretation, and implementing transparent remediation

D. Automatically buying the largest available licence bundle

Correct Answer: C. Preserving evidence, validating the interpretation, and implementing transparent remediation

Question 10

Which feature is characteristic of subscription economics?

A. No possibility of renewal exposure

B. Recurring commitments that may include price escalation and minimum quantities

C. Guaranteed ownership of the supplier’s intellectual property

D. No need to monitor usage

Correct Answer: B. Recurring commitments that may include price escalation and minimum quantities