You have set Extended Round Robin on a server with intensive sequential I/O profile. Which two benefits result from implementing this algorithm? (Choose two.)

Question

Options

• Atracks preloaded to cache
• Bblocks held permanent in Read Cache
• Cno tracks preloading on the system
• Defficient cache usage on the storage system

Explanation

Extended Round Robin (ERR) with a sequential I/O profile yields two key benefits: C (no tracks preloading) and D (efficient cache usage).

ERR is designed for heavy sequential workloads by recognizing that data is read in order and will not be revisited - so preloading tracks ahead of time is wasteful. Instead of filling cache with anticipated reads, ERR skips preloading entirely (C), which directly leads to more efficient use of the cache (D) by keeping it available for data that actually benefits from caching.

• A is wrong because ERR does the opposite - it deliberately avoids preloading tracks into cache.
• B is wrong because ERR does not hold blocks permanently in read cache; blocks are used and released rather than pinned.

Memory tip: Think of ERR as "Efficient Read Release" - for sequential I/O, data is read once and gone, so ERR skips the preload and keeps cache clean. If you preload sequential data, you waste cache on blocks you'll only read once anyway.

No community discussion yet for this question.