1. What is the main purpose of POSIX real-time extensions?
(A) To ignore deadlines
(B) To reduce CPU idle exclusively
(C) To perform batch processing only
(D) To provide standardized APIs for developing real-time applications on Unix-like systems
2. POSIX real-time extensions include support for:
(A) Disk batch-only tasks
(B) CPU idle exclusively
(C) Real-time threads, scheduling policies, and timers
(D) Memory-only operations
3. Which POSIX scheduling policies are commonly used for real-time threads?
(A) SCHED_FIFO and SCHED_RR
(B) CPU idle exclusively
(C) Disk batch-only scheduling
(D) Memory-only policies
4. SCHED_FIFO scheduling in POSIX is:
(A) CPU idle exclusively
(B) A fixed-priority, first-in-first-out scheduling for real-time threads
(C) Disk batch-only scheduling
(D) Memory-only policy
5. SCHED_RR scheduling is characterized by:
(A) CPU idle exclusively
(B) Fixed-priority round-robin execution with time slices
(C) Disk batch-only round-robin
(D) Memory-only scheduling
6. POSIX real-time signals allow:
(A) Memory-only notification
(B) CPU idle exclusively
(C) Disk batch-only signals
(D) Asynchronous notification of events to real-time threads
7. POSIX message queues are used for:
(A) CPU idle exclusively
(B) Inter-task communication in real-time systems
(C) Disk batch-only communication
(D) Memory-only messaging
8. POSIX semaphores provide:
(A) Disk batch-only locking
(B) CPU idle exclusively
(C) Mechanisms for synchronization and mutual exclusion
(D) Memory-only synchronization
9. POSIX timers allow:
(A) Memory-only timing
(B) CPU idle exclusively
(C) Disk batch-only timers
(D) Execution of tasks at specific times or intervals
10. Real-time threads in POSIX can have:
(A) Disk batch-only execution
(B) CPU idle exclusively
(C) Explicit priorities to support deterministic scheduling
(D) Memory-only priorities
11. POSIX mutexes support:
(A) Priority inheritance to prevent priority inversion
(B) CPU idle exclusively
(C) Disk batch-only mutexes
(D) Memory-only locks
12. Timers in POSIX can be:
(A) CPU idle exclusively
(B) One-shot or periodic
(C) Disk batch-only timers
(D) Memory-only clocks
13. POSIX real-time extensions improve system predictability by:
(A) Memory-only allocation
(B) CPU idle exclusively
(C) Disk batch-only operations
(D) Allowing precise control over thread scheduling and synchronization
14. A key feature of POSIX real-time extensions is:
(A) CPU idle exclusively
(B) Standardization across Unix-like operating systems
(C) Disk batch-only APIs
(D) Memory-only standardization
15. POSIX condition variables are used for:
(A) CPU idle exclusively
(B) Blocking threads until a specific condition is met
(C) Disk batch-only conditions
(D) Memory-only signaling
16. POSIX real-time extensions allow the creation of:
(A) Memory-only threads
(B) CPU idle exclusively
(C) Disk batch-only threads
(D) High-priority threads that can meet strict deadlines
17. Priority inheritance in POSIX mutexes helps to:
(A) CPU idle exclusively
(B) Prevent lower-priority threads from blocking higher-priority threads indefinitely
(C) Disk batch-only execution
(D) Memory-only management
18. POSIX provides functions for:
(A) Real-time scheduling, timers, semaphores, and message queues
(B) CPU idle exclusively
(C) Disk batch-only APIs
(D) Memory-only operations
19. Using POSIX real-time extensions helps in:
(A) CPU idle exclusively
(B) Building deterministic and predictable real-time applications on Unix-like systems
(C) Disk batch-only programming
(D) Memory-only operations
20. The main advantage of POSIX real-time extensions is:
(A) Standardized API support for real-time threads, synchronization, and timing
(B) CPU idle exclusively
(C) Disk batch-only optimization
(D) Memory-only efficiency