QuizzesUser-Level vs Kernel-Level Threads — Concept Check
intermediate
operating-systems

User-Level vs Kernel-Level Threads — Concept Check

Questions on User-Level vs Kernel-Level Threads. User-level threads are managed entirely in user space by a library, while kernel-level threads are managed by the OS, enabling true parallelism at the cost of heavier context-switch overhead.

7 minutes 7 questions Pass at 70%
Time Limit
7 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

7 questions on User-Level vs Kernel-Level Threads — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A developer notices that their multi-threaded application is not utilizing multiple cores effectively. They are using user-level threads. What could be the reason?

    • AThe application is CPU-bound and user-level threads are ideal for I/O-bound tasks.
    • BUser-level threads do not enable true parallelism on multi-core systems.
    • CUser-level threads are inherently slower than kernel-level threads.
    • DUser-level threads require more memory, limiting core usage.
  2. 2.A Java application using virtual threads suddenly experiences increased latency during database queries. What is a likely cause?

    • AVirtual threads are CPU-bound, which virtual threads handle poorly.
    • BVirtual threads are inherently slower than platform threads.
    • CVirtual threads are blocking on I/O, causing delays.
    • DThe application is not using enough kernel threads.
  3. 3.In a system using many-to-one threading model, what happens if one thread makes a blocking I/O call?

    • AAll threads in the process block.
    • BThe kernel automatically switches to another thread.
    • CThe process crashes due to deadlock.
    • DOnly the calling thread blocks.
  4. 4.A developer using Java 21's Project Loom wants to handle millions of concurrent tasks. Which threading model should they use?

    • AVirtual threads for lightweight concurrency.
    • BPlatform threads for CPU-bound tasks.
    • CUser-level threads for better memory management.
    • DKernel-level threads for true parallelism.
  5. 5.Why might an application using kernel-level threads experience higher overhead compared to user-level threads?

    • AKernel-level threads block the entire process on I/O calls.
    • BKernel-level threads do not support parallelism on multi-core systems.
    • CKernel-level threads require syscalls for creation and context switching.
    • DKernel-level threads are slower to execute than user-level threads.
  6. 6.A service using a many-to-many threading model experiences unpredictable performance. What could be the issue?

    • AUser threads blocking kernel threads.
    • BToo many kernel threads causing overhead.
    • CKernel threads not supporting parallelism.
    • DImproper mapping of user threads to kernel threads.
  7. 7.Which threading model does modern JVMs like HotSpot use for platform threads?

    • AOne-to-One mapping for true parallelism.
    • BMany-to-One mapping for simplicity.
    • CUser-level threads for performance.
    • DMany-to-Many mapping for flexibility.