Java wait/notify facts — select the two true statements from the list provided.

Introduction / Context:The item asks you to evaluate several assertions about Java’s wait/notify mechanism and thread scheduling. Understanding which methods are overloaded, what contexts are required, and what guarantees exist is essential for correct concurrent code.

Given Data / Assumptions (statements):

• 1) Deadlock will not occur if wait()/notify() is used
• 2) A thread will resume execution as soon as its sleep duration expires.
• 3) Synchronization can prevent two objects from being accessed by the same thread.
• 4) The wait() method is overloaded to accept a duration.
• 5) The notify() method is overloaded to accept a duration.
• 6) Both wait() and notify() must be called from a synchronized context.

Concept / Approach:Evaluate each statement against the Java Language Specification and java.lang.Object API.

Step-by-Step Solution:

Verification / Alternative check:Consult Object’s method signatures: wait(), wait(long), wait(long, int), notify(), notifyAll().

Why Other Options Are Wrong:

• Any pair containing 1, 2, 3, or 5 includes at least one false statement.

Common Pitfalls:Believing that sleep guarantees immediate resumption or that using wait/notify magically prevents deadlocks.

Final Answer:4 and 6