Linux /var Directory MCQ Quiz

Question 1 Not answered

What does `/var` mean in Linux?

Virtual archive root Variable data Verified application records Versioned admin repository

Explanation: `/var` stands for variable data. It stores files that change frequently while the system is running.

Question 2 Not answered

Which type of data is commonly stored in `/var`?

Kernel source code only Changing system and application data Only user desktop files Only bootloader files

Explanation: `/var` stores changing data such as logs, cache, spool files, application state, mail, databases, and web files.

Question 3 Not answered

Which directory is mainly used for Linux log files?

/var/log /var/cache /var/tmp /var/spool

Explanation: `/var/log` stores system and application logs, which are very important for troubleshooting.

Question 4 Not answered

Which file is commonly used as the main system log on Ubuntu/Debian?

/var/log/messages /var/log/syslog /var/log/secure /var/log/yum.log

Explanation: Ubuntu/Debian commonly use `/var/log/syslog` as a main system log file.

Question 5 Not answered

Which file is commonly used as the main system log on RHEL/CentOS/Fedora?

/var/log/messages /var/log/auth.log /var/log/syslog /var/log/apt.log

Explanation: RHEL-based systems commonly use `/var/log/messages` for general system logs.

Question 6 Not answered

Which directory stores cached data used by applications and package managers?

/var/cache /var/mail /var/www /var/lock

Explanation: `/var/cache` stores temporary cached data that can usually be recreated.

Question 7 Not answered

Which command cleans package cache on Ubuntu/Debian?

sudo apt clean sudo dnf clean all sudo yum remove cache sudo cachectl clear apt

Explanation: `sudo apt clean` removes downloaded package cache on Ubuntu/Debian systems.

Question 8 Not answered

Which command cleans package cache on RHEL/Fedora systems?

sudo apt clean sudo dnf clean all sudo dpkg clean sudo cache clear

Explanation: `sudo dnf clean all` is used on many modern RHEL/Fedora systems to clean DNF cache.

Question 9 Not answered

What is the purpose of `/var/spool`?

To store queued jobs waiting to be processed To store only kernel modules To store user pictures To store bootloader configuration

Explanation: `/var/spool` stores queued work such as mail queues, print jobs, cron jobs, and at jobs.

Question 10 Not answered

Which directory may store user crontabs on many Linux systems?

/var/spool/cron /var/cache/cron /var/log/cron /var/www/cron

Explanation: User crontabs are often stored under `/var/spool/cron`.

Question 11 Not answered

What is the main difference between `/tmp` and `/var/tmp`?

/tmp is for logs; /var/tmp is for users /tmp may be cleared on reboot; /var/tmp may survive reboot /tmp is only for root; /var/tmp is only for normal users There is no difference at all

Explanation: `/tmp` often contains short-lived temporary files, while `/var/tmp` is for temporary data that may remain after reboot.

Question 12 Not answered

Which directory stores application state data such as Docker data, databases, and package manager state?

/var/lib /var/log /var/run /var/mail

Explanation: `/var/lib` stores persistent application state data and should not be deleted carelessly.

Question 13 Not answered

Where is Docker data commonly stored by default?

/var/lib/docker /var/cache/docker /var/log/docker /var/www/docker

Explanation: Docker commonly stores images, containers, layers, and other data in `/var/lib/docker`.

Question 14 Not answered

Which directory is commonly used as a default web root for Apache or NGINX labs?

/var/www/html /var/spool/html /var/cache/html /var/log/html

Explanation: `/var/www/html` is commonly used as a default web document root, although the exact root depends on web server configuration.

Question 15 Not answered

What is `/var/mail` used for on some Linux systems?

Local user mail Kernel boot files Temporary package files Systemd unit files

Explanation: `/var/mail` may store local mail files for users.

Question 16 Not answered

On modern Linux systems, `/var/run` is often a symbolic link to which directory?

/run /root /etc/run /usr/run

Explanation: On many modern Linux systems, `/var/run` points to `/run`, which stores runtime data.

Question 17 Not answered

What does `/var/lock` store?

Lock files used to prevent conflicting access to resources Encrypted user passwords Firewall rules Bootloader locks only

Explanation: `/var/lock` stores lock files so processes do not use the same resource at the same time.

Question 18 Not answered

Which command checks the total size of `/var`?

sudo du -sh /var df -commands /var ls --size-only /var journalctl --var-size

Explanation: `sudo du -sh /var` shows the total disk usage of the `/var` directory in human-readable format.

Question 19 Not answered

Which command shows large first-level directories inside `/var` sorted by size?

sudo du -h /var --max-depth=1 | sort -h sudo ls /var --biggest sudo df /var --sort sudo find /var --folders

Explanation: `du` with `--max-depth=1` shows first-level directory sizes, and `sort -h` sorts them in human-readable order.

Question 20 Not answered

Which command checks overall filesystem disk space?

df -h du -sh /var lsblk -mail free -h

Explanation: `df -h` shows filesystem disk usage in human-readable format.

Question 21 Not answered

Which command checks systemd journal disk usage?

journalctl --disk-usage systemctl --disk-usage logrotate --disk-usage du --journal-only

Explanation: `journalctl --disk-usage` shows how much disk space the systemd journal is using.

Question 22 Not answered

Which command safely removes old journal logs older than 7 days?

sudo journalctl --vacuum-time=7d sudo rm -rf /var/log/journal sudo gzip -r /var/log sudo journalctl --delete-all

Explanation: `journalctl --vacuum-time=7d` safely removes old journal logs based on time.

Question 23 Not answered

Which command should you avoid because it can destroy important `/var` data?

sudo rm -rf /var/* sudo du -sh /var df -h ls -l /var

Explanation: `sudo rm -rf /var/*` is dangerous because it can delete logs, databases, package data, Docker data, web files, and service state.

Question 24 Not answered

What is the safer approach when `/var` is full?

Find what is large, understand what owns it, then clean safely Delete everything inside `/var` Compress `/var` in place using gzip -r Change ownership of `/var` to your user

Explanation: A safe admin approach is to identify large directories, understand the responsible application, and use proper cleanup commands.

Question 25 Not answered

Is it safe to blindly compress the whole `/var` directory in place using `gzip -r /var`?

Yes, always recommended No, it can compress active files and break services Yes, but only on Ubuntu Yes, if `/var` is small

Explanation: Compressing `/var` in place can break services because many active files are expected to remain in normal readable/writable form.

Result