ORIGINAL COMPANY-CONTEXT PRACTICE
Reconcile virtual-machine inventory with software entitlements
Original practice scenario: A hypothetical infrastructure-software report compares virtual-machine inventory with license entitlements across hosts. How would you prevent snapshot and join errors?
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
Choose an as-of time and a license-consumption rule before comparing counts. A migrating virtual machine may appear on two hosts even though it is one logical machine.
Work through it
- Give virtual machines stable identities and retain host membership intervals; collapse duplicate observations within each authoritative inventory snapshot.
- Map entitlements at their contractual grain, such as host or resource pool, and aggregate consumption independently before joining to entitlement totals.
- Produce separate rows for uncovered consumption, unused entitlement and unknown mappings, with controls over both populations and their effective dates.
Tradeoffs to discuss
- A current-state report is simpler than interval accounting but cannot explain historical migration or entitlement changes.
Common pitfalls
- Do not assume every license is consumed per virtual machine; the metric is part of the hypothetical contract.
- Treat missing inventory coverage as unknown rather than evidence that capacity is unused.