Hardware vs. Software basics.

A kernel module can connect with the core system and help control hardware. For exams treat it as more sensitive than a normal app.

Microcode relates to how instructions are implemented inside a processor. For exams do not treat it as normal application software.

A microcode update can provide improvements at processor level. For exams connect it with internal hardware control.

A type one hypervisor can run directly on hardware without a host operating system. For exams connect it with bare metal hypervisor.

A type two hypervisor runs on top of a host operating system. For exams remember the placement of both hypervisor types.

A virtual network card is not a separate real card but a device shown by software. For exams separate virtual and physical items.

Emulation can imitate while virtualization controls use of real hardware resources. For exams do not treat both terms as the same.

Namespaces can make a container feel like a separate environment. For exams treat containers as software isolation concept.

Control groups can limit resources like CPU and memory. For exams connect this with software control over hardware resources.

A sandbox improves security by keeping an app within controlled limits. For exams understand it as a software security model.

A system call is communication between application and operating system. For exams separate software service from processor level work.

Context switch is used by the operating system to run processes. For exams connect it with multitasking.

A process is a running program and a thread can be a stream of work inside it. For exams treat both as software execution concepts.

A race condition is related to software coordination. For exams focus on shared resource and timing order.

Deadlock is a software resource management problem. For exams identify the words waiting and resources.

Memory protection helps system stability and security. For exams connect it with operating system and hardware cooperation.

Direct answer: Option A is correct. A page fault occurs when a program refers to a virtual memory page that is not currently present in main memory, or RAM. The operating system notices this event, finds the required page in secondary storage if available, loads it into a suitable RAM frame, and then allows the instruction to continue. Thus, a page fault is a normal memory-management event; it does not necessarily mean that the computer is permanently damaged. Option A gives exactly the required condition. Option B is wrong because the amount of paper in a printer is unrelated to virtual-memory pages. Option C is wrong because a clean mouse pad affects mouse movement, not RAM contents. Option D is wrong because a blue monitor display does not indicate that a memory page is absent. Exam cue: page fault means “needed page absent from RAM,” not a physical page falling down.

Thrashing can occur due to low RAM or heavy memory pressure. For exams connect it with slow performance.

A memory leak is a software fault but increases RAM use. For exams distinguish the fault and its effect.

A journaling file system can reduce damage after sudden shutdown. For exams connect it with storage safety.

Metadata helps organize and find a file. For exams understand the difference between data and data about data.

Both can be storage management methods but the place of control differs. For exams identify the role of controller and operating system.

Wear leveling is related to internal management of an SSD. For exams connect it with cooperation of storage hardware and firmware.

TRIM helps storage management between operating system and SSD. For exams understand it as software command and hardware response.

Queue depth tells how many requests storage is handling. For exams connect it with performance analysis.