Explanation

In function overriding, the function name and return type in the derived class must be the same as in the base class.

The parameter list also remains identical, ensuring the derived class redefines the base class behavior.

Explanation

Overloaded functions must have different parameter lists (number or type of parameters).

The function name remains the same, and return type does not differentiate overloaded functions.

Explanation

Function overloading requires the same function name but different parameter lists.

Return type can be the same or different, but it alone cannot distinguish overloaded functions.

Explanation

Abstraction hides implementation details and focuses on high-level design concepts.

It helps manage complexity by showing only essential features to the user.

Explanation

Polymorphism allows different classes to respond uniquely to the same function or message.

It enhances flexibility and code reusability in object-oriented programming.

Explanation

Encapsulation hides an object’s internal data and exposes only necessary methods.

It controls access to data, ensuring integrity and security.

Explanation

FCFS schedules processes in the order they arrive, ensuring every process eventually executes.

It is simple and fair, making it least prone to starvation compared to SJN or priority-based methods.

Explanation

SJN favors shorter jobs, so long jobs may wait indefinitely, causing starvation.

FCFS and Round Robin are more fair, reducing the risk of starvation.

Explanation

For a deadlock to occur in an operating system, four necessary conditions

(known as the Coffman conditions).

1. Mutual Exclusion
2. Hold and Waite 
3. No Preemption
4. Circular Wait

Last updated 15-feb-2026

Explanation

Deadlock requires mutual exclusion, hold and wait, and circular wait, but preemption is not necessary.

Preemption can actually help prevent or resolve deadlocks by forcibly reallocating resources.