What is a memory protection unit (MPU) and how does it contribute to software safety in a mission computer?

What is a memory protection unit (MPU) and how does it contribute to software safety in a mission computer?

• A. It provides cryptographic protection for memory.
• B. It enforces per-task memory access permissions and isolates faults.
• C. It manages memory allocation for the kernel only.
• D. It speeds up memory access by caching.

Answer: (B)

A memory protection unit enforces boundaries around memory so each task can only access its own designated regions, keeping separate tasks from interfering with one another or with the kernel. It does this by defining memory regions with specific access permissions (read, write, execute) and often privilege levels. If a task tries to access memory outside its allowed regions, the MPU triggers a fault that the operating system can handle, instead of causing silent data corruption across the system. In a mission computer with safety-critical software, this isolation is essential. It contains faults to the offending task, prevents corruption from spreading, and supports predictable, recoverable failure modes. Because the protection is hardware-enforced, it provides stronger guarantees than software-only checks and works alongside other safety measures to improve overall software safety. The other options describe different concerns—cryptography, kernel-only memory allocation, or caching—that don’t capture how an MPU safeguards memory access and fault containment.

A memory protection unit enforces boundaries around memory so each task can only access its own designated regions, keeping separate tasks from interfering with one another or with the kernel. It does this by defining memory regions with specific access permissions (read, write, execute) and often privilege levels. If a task tries to access memory outside its allowed regions, the MPU triggers a fault that the operating system can handle, instead of causing silent data corruption across the system.

In a mission computer with safety-critical software, this isolation is essential. It contains faults to the offending task, prevents corruption from spreading, and supports predictable, recoverable failure modes. Because the protection is hardware-enforced, it provides stronger guarantees than software-only checks and works alongside other safety measures to improve overall software safety. The other options describe different concerns—cryptography, kernel-only memory allocation, or caching—that don’t capture how an MPU safeguards memory access and fault containment.