Original practice scenario: A hypothetical network appliance serves flows with different packet sizes. Compare a simple round-robin queue with a byte-aware fair scheduler.
Read model answer +
Fairness should be defined in bytes or service time when packet sizes differ. Serving one packet from each flow per round can allocate very different bandwidth shares.
Work through it
State the desired weights and maximum acceptable delay, then maintain per-flow queues with bounded total memory and an explicit overflow policy.
Use a deficit counter or comparable byte-aware mechanism: add each flow quantum, transmit eligible packets, and carry unused credit across rounds.
Test small packets against large packets, idle-to-active transitions and persistent overload, recording throughput share and tail waiting time.
Tradeoffs to discuss
Larger quanta reduce scheduling overhead but can increase short-flow latency; strict priority lowers selected latency while risking starvation.
Common pitfalls
Reset or retain unused credit deliberately when a queue becomes empty.
Bound queue admission separately from fair service, because a fair scheduler cannot prevent memory exhaustion.
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?
Read 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.
