What is a key limitation of the working set model in preventing thrashing that candidates often overlook?

medium🪤 Complexity Trap Q13 of Q15

Operating Systems - Thrashing - Working Set Model & Prevention

AIt requires tracking all page references, which can be expensive and complex

BIt guarantees zero page faults once the working set is allocated

CIt works best when all processes have identical working set sizes

DIt eliminates the need for load control mechanisms

Step-by-Step Solution

Step 1: Understand working set model overhead
The model requires monitoring page references over time windows, which can be costly.
Step 2: Analyze options
A is correct because tracking page references precisely is resource-intensive.
B is incorrect because even with working set allocation, some page faults can occur.
C is incorrect because working set sizes vary widely among processes.
D is incorrect because load control is still needed when total working sets exceed memory.
Final Answer:
Option A -> Option A
Quick Check:
Working set tracking overhead is a practical limitation often underestimated.

Quick Trick: Working set tracking = overhead cost

Common Mistakes:

MISTAKES

Trap Explanation:

PITFALL

Option B is tempting as candidates think working set allocation is perfect; option D confuses prevention with elimination of thrashing.

Interviewer Note:

CONTEXT

Tests candidate's understanding of practical trade-offs and limitations of the working set model.

Master "Thrashing - Working Set Model & Prevention" in Operating Systems

2 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Operating Systems Quizzes