ITPEC FE Morning October 2020 Question 29
ITPEC FE Morning October 2020 — Question 29 of 80
Lock Granularity — the size of the data unit a transaction locks (row, page, table, database).
- •Large granularity (e.g., table-level lock): fewer locks needed, but other transactions must wait longer → lower throughput
- •Small granularity (e.g., row-level lock): more locks needed, but other transactions can work in parallel → higher throughput
Why (c):
- Large granularity blocks more data per lock → other transactions wait → throughput declines
Why not others:
- (a) Large granularity reduces concurrency, not increases it
- (b) Large granularity does not leave other transactions' data "undisturbed" — it blocks more data
- (d) Large granularity decreases the number of locks (one lock covers more data), not increases
Key rule: Large granularity = fewer locks + less concurrency. Small granularity = more locks + more concurrency.
AI-generated — may contain errors
The original exam layout is preserved in the image so diagrams, formulas, tables, and code remain accurate.
This question comes from an official ITPEC past paper. ITPEC Practice is an independent study tool and is not affiliated with ITPEC. See the official FE past-paper collection or Report an issue.