[Solved] Why does less use a buffer to display file content instead of reading the entire file at once? — Ans: To improve performance and allow quick navigation in large files | Linux CLI

Linux CLI - Viewing and Editing Files

Why does less use a buffer to display file content instead of reading the entire file at once?

ATo improve performance and allow quick navigation in large files

BBecause it cannot read files larger than 1MB

CTo prevent users from editing the file accidentally

DBecause it only supports text files

Step-by-Step Solution

Solution:

Step 1: Understand less buffering behavior
less reads files in chunks (buffering) to handle large files efficiently without loading all content into memory.
Step 2: Analyze incorrect options
It can read files larger than 1MB; it is a viewer, not editor; it supports text files but buffering is for performance.
Final Answer:
To improve performance and allow quick navigation in large files -> Option A
Quick Check:
Buffering improves performance [OK]

Quick Trick: Buffering helps less handle big files smoothly [OK]

Common Mistakes:

Master "Viewing and Editing Files" in Linux CLI

9 interactive learning modes - each teaches the same concept differently

More Linux CLI Quizzes

Why does less use a buffer to display file content instead of reading the entire file at once?