Practice
Solution
Step 1: Recall linked allocation properties
Linked allocation stores file blocks non-contiguously with pointers linking blocks sequentially.Step 2: Analyze linked allocation eliminates external fragmentation by allowing non-contiguous storage
Correct: linked allocation avoids external fragmentation by allowing scattered blocks.Step 3: Analyze linked allocation supports efficient direct access to any block in the file
Incorrect: linked allocation does not support efficient direct access; it requires sequential traversal.Step 4: Analyze each file block contains a pointer to the next block in the chain
Correct: each block contains a pointer to the next.Step 5: Analyze linked allocation requires only the starting block address to access the entire file
Correct: only the starting block address is needed to traverse the file.Final Answer:
Option B -> Option BQuick Check:
Linked allocation -> no efficient direct access, only sequential traversal.
- Assuming linked allocation supports direct access
- Confusing external fragmentation with internal fragmentation
Solution
Step 1: Recall EAT formula
EAT = (hit ratio x access time on hit) + (miss ratio x access time on miss)Step 2: Analyze each statement
A: Correct, EAT depends on hit ratio and memory times.
B: Incorrect, TLB miss does not always cause page fault; it triggers page table lookup.
C: Correct, formula reflects hit and miss costs.
D: Correct, higher hit ratio lowers average access time.Final Answer:
Option A -> Option AQuick Check:
TLB miss ≠ page fault; page fault only if page not in memory.
- Confusing TLB miss with page fault
- Misapplying EAT formula
Solution
Step 1: Understand inode fixed size
Inodes have a fixed size that includes space for direct and indirect pointers, regardless of file size.Step 2: Analyze impact on small files
Including triple indirect pointers increases inode size, which can waste space when storing many small files.Step 3: Clarify access speed for small files
Accessing small files uses direct pointers only; indirect pointers are not traversed, so no speed penalty.Step 4: Confirm allocation behavior
Indirect blocks are allocated only when needed; small files do not allocate them.Final Answer:
Option A -> Option AQuick Check:
Fixed inode size with many pointers wastes space for small files [OK]
- Assuming indirect pointers slow down small file access
- Believing indirect blocks are allocated for small files
- Thinking triple indirect pointers have no impact on inode size
Solution
Step 1: Understand Waiting state semantics
Waiting means blocked until the awaited event(s) complete.Step 2: Multiple I/O waits in five-state model
The model treats Waiting as a single state without differentiating multiple simultaneous waits.Step 3: Limitation
This means the process stays in Waiting until all I/O events complete, limiting fine-grained concurrency.Final Answer:
Option B -> Option BQuick Check:
Five-state model does not handle multiple simultaneous waits distinctly [OK]
- Assuming process moves to Ready after any I/O completes
- Believing process can split into multiple processes automatically
- Thinking process polls I/O events while Running
Solution
Step 1: Understand current mode
Interrupt handlers run in kernel mode with full privileges.Step 2: System call invoked in kernel mode
Since already in kernel mode, no mode switch is needed; system call executes directly.Step 3: Why other options are incorrect
The CPU switches to user mode before executing the system call to prevent privilege escalation. is incorrect; switching to user mode would reduce privileges improperly. The system call is deferred until the interrupt handler finishes and user mode resumes. is wrong; system calls are not deferred. The system call triggers a nested mode switch to a higher privilege level. is false; kernel mode is the highest privilege level, no nested switch occurs.Final Answer:
Option C -> Option CQuick Check:
System call in kernel mode -> no mode switch -> immediate execution [OK]
- Assuming mode switch always occurs on system call
- Thinking system calls are deferred inside kernel
- Believing nested privilege levels exist beyond kernel mode
