Configure Linux Components   «Prev  Next»

Kernel Modules and Concepts for Red Hat - Quiz

Each question is worth one point. Select the best answer or answers for each question.
1. Where should an administrator place persistent module options and aliases for modprobe?
Please select the best answer.
  A. /etc/conf.modules
  B. A .conf file under /etc/modprobe.d/
  C. A file under /etc/modules-load.d/
  D. /lib/modules/$(uname -r)/modules.dep

2. Which statement correctly describes Linux kernel architecture and loadable modules?
Please select the best answer.
  A. Loading a module changes Linux from a monolithic kernel into a microkernel.
  B. Loadable modules execute as isolated user-space services.
  C. Linux has a monolithic architecture, while selected features can be built as loadable modules that still execute in kernel space.
  D. Every feature in a monolithic kernel must be built into the kernel image.

3. Which statement best describes automatic module loading on a current Linux system?
Please select the best answer.
  A. A single kernel thread named kmod runs all module functionality.
  B. Device or subsystem aliases can trigger a module request, and modprobe uses dependency metadata and configuration while loading the required module.
  C. modules-load.d detects every device and chooses its driver automatically.
  D. Every installed module is loaded during startup.

4. Which statements correctly distinguish installed, loaded, and built-in kernel functionality?
Please select all the correct answers.
  A. lsmod lists modules currently loaded in the running kernel.
  B. modinfo can display metadata and accepted parameters for an available module.
  C. A working built-in driver does not appear in lsmod.
  D. Any .ko file under /lib/modules is automatically loaded.

5. A storage driver is configured as a module and is required to reach the real root filesystem. What must be true for a normal boot?
Please select the best answer.
  A. The driver and its required dependencies must be available in the initramfs and loadable early enough to reach the root filesystem.
  B. The driver only needs to exist somewhere on the unmounted root filesystem.
  C. Adding the driver name to /etc/modprobe.d/ copies it into the initramfs automatically.
  D. Running lsmod before reboot guarantees that the next boot can load the driver.