1. Threads created by a single program share the same memory address space. T/F

2. Threads created by a single program share the same memory stack. T/F

3. Threads created by a single program share the same scheduling state (e.g., Ready, Waiting). T/F

4. Threads created by a single program share the same open files. T/F

5. A thread enters the Running state when the thread scheduler resumes it. T/F

6. The thread_exit() call can immediately garbage collect the exited thread's resources and destroy the exited thread's thread control block. T/F

7. Threads are less expensive to create and destroy than processes. T/F

8. It is correct programming logic to assume that, once resumed, a thread will run without interruption up to the point of its next system call. T/F

9. It is correct programming logic to assume that the thread scheduling pattern will be the same on each run when the same program is executed multiple times with the same data and the same command line arguments. T/F

10. The Unix fork() system call is used to create a new process, and the Unix exec() system call is used to create a new thread. T/F