Courseiva
Storage Management →mediumMultiple Choice

LFCS Storage Management Practice Question

An administrator needs to mount an XFS filesystem with options to optimize for a database workload. Which mount option would reduce metadata updates to improve performance?

⚠ Common exam trap

Watch out — candidates often confuse `relatime` (which reduces but does not eliminate atime updates) with `noatime`, or incorrectly assume `nodiratime` is sufficient for database optimization, when only `noatime` fully removes metadata write overhead for all files.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

noatime

The `noatime` mount option disables updates to the inode access time (atime) on every file read. For database workloads, this eliminates a significant source of metadata write I/O, reducing disk contention and improving overall performance by avoiding unnecessary journal updates on XFS.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    noexec

    Why it's wrong here

    noexec only blocks execution of binaries on the mount; it does not alter inode timestamp or metadata write behaviour. It is tempting as a hardening and performance option, and would be correct when the requirement is preventing execution from a data volume rather than reducing metadata updates.

  • ✗

    nodiratime

    Why it's wrong here

    nodiratime suppresses directory inode timestamp updates only; file inode metadata writes still occur, so the reduction is partial and does not target the database workload's file access pattern. It is tempting because it is a genuine atime-related tuning option, and would be correct when directory reads dominate and file timestamps are irrelevant.

  • ✗

    relatime

    Why it's wrong here

    relatime still writes inode timestamps whenever the previous atime is older than mtime or ctime, so metadata updates continue rather than being eliminated. It is tempting because it is the common default atime setting, and would be correct when a balance between timestamp accuracy and write reduction is acceptable.

  • ✓

    noatime

    Why this is correct

    noatime suppresses access-time updates on every file read, eliminating a metadata write per read. For a database workload performing constant reads, this reduces journal and metadata overhead on the XFS filesystem, improving throughput without affecting data integrity.

About these practice questions

Courseiva writes every LFCS question from scratch — 406 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This LFCS practice question is part of Courseiva's free Linux Foundation certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LFCS exam.