For reliable DBMS operation and performance at scale, which hardware component is most critical because it provides fast, persistent storage for tables, indexes, and transaction logs?

Difficulty: Easy

Correct Answer: high speed, large-capacity disk

Explanation:


Introduction / Context:
Database performance hinges on how quickly data can be durably read and written. While CPUs and memory matter, the storage subsystem directly affects response times for queries, writes, checkpoints, and recovery. This question focuses on identifying the single most important hardware component that underpins a DBMS's dependable operation and throughput.


Given Data / Assumptions:

  • The database must persist data and transaction logs safely.
  • High I/O workloads demand low latency and high throughput.
  • Component choices impact durability (ACID), backup speed, and recovery.


Concept / Approach:

Persistent storage (disks or modern SSD/NVMe arrays) stores data files, indexes, and logs. Transaction logs are write-intensive and sensitive to latency; data files require both random and sequential I/O. Consequently, a high speed, large-capacity disk subsystem (often with RAID/NVMe and caching) is essential for both performance and reliability. Displays, mice, plotters, and printers do not influence DBMS durability or query execution speed.


Step-by-Step Solution:

Identify the DBMS bottleneck: durable reads/writes.Relate ACID durability to storage performance and resilience.Choose the component that directly addresses I/O: high speed, large-capacity disk.Exclude peripherals unrelated to data persistence or I/O paths.


Verification / Alternative check:

Benchmarking commonly shows that improving disk I/O (e.g., moving from HDD to NVMe) drastically reduces query times and recovery windows, validating the selection.


Why Other Options Are Wrong:

Video display, mouse, plotter, printer: User-interface/output devices; they do not impact transaction throughput or durability.


Common Pitfalls:

Underestimating the log write path; slow disks cause commit stalls and long recovery times after failures.


Final Answer:

high speed, large-capacity disk

More Questions from Database Systems

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion