nerdexam
CompTIA

SK0-004 · Question #724

Which of the following best practices should an administrator use to build a database server?

The correct answer is B. The transaction log files should be on a journaling filesystem. Transaction log files should reside on a journaling filesystem to ensure atomic writes and protect log integrity against corruption during unexpected crashes.

Server administration

Question

Which of the following best practices should an administrator use to build a database server?

Options

  • AThe transaction log files should be on a separate volume.
  • BThe transaction log files should be on a journaling filesystem.
  • CThe transaction log files should be on the system volume.
  • DThe transaction log files should be compressed.

How the community answered

(21 responses)
  • A
    5% (1)
  • B
    81% (17)
  • C
    5% (1)
  • D
    10% (2)

Why each option

Transaction log files should reside on a journaling filesystem to ensure atomic writes and protect log integrity against corruption during unexpected crashes.

AThe transaction log files should be on a separate volume.

Placing transaction logs on a separate volume improves I/O throughput by reducing contention, but it does not by itself protect log file integrity against corruption during a system crash.

BThe transaction log files should be on a journaling filesystem.Correct

A journaling filesystem such as ext4, XFS, or NTFS maintains a journal of pending filesystem operations before committing them, ensuring writes are atomic. This protects transaction log files from partial writes and metadata corruption during power failures or crashes, which is critical for database recoverability and point-in-time restore operations.

CThe transaction log files should be on the system volume.

Placing transaction log files on the system volume creates I/O contention between the OS and the database engine, degrading both system and database performance.

DThe transaction log files should be compressed.

Compressing transaction log files adds CPU overhead and disrupts the sequential write pattern that database engines depend on for high-throughput logging and fast crash recovery.

Concept tested: Database transaction log filesystem integrity requirements

Source: https://learn.microsoft.com/en-us/sql/relational-databases/sql-server-transaction-log-architecture-and-management-guide

Topics

#database server#transaction logs#filesystem#server configuration

Community Discussion

No community discussion yet for this question.

Full SK0-004 Practice