Systems, OS & Memory Safety practice test
How the kernel isolates processes, Unix permissions, setuid and capabilities, SELinux and AppArmor, Windows tokens and Active Directory, memory-corruption bugs and the mitigations against them, fuzzing, reverse engineering, and boot integrity: the systems layer every sandbox and agent runtime rests on. The pool for this topic holds 12 easy, 21 medium and 19 hard items. Each answer comes with its reasoning and a link to the question or concept page it was drawn from.
Sample items with answers
Isolation comes from virtual memory: the MMU translates addresses through the current process's page tables, and the kernel switches tables on every context switch. Bounds checks and encryption are not what provide it. Debugging interfaces are deliberate, access-checked exceptions.
Root's code runs in user mode like any program and asks the kernel through system calls. Root is allowed to ask for more, including loading kernel modules, which is how root reaches kernel code execution.
After the test
Choosing from options is easier than reasoning it out in front of a panel. These pages make you reason it out: