The defining characteristic examiners look for: OOP models a system as a set of interacting objects, each bundling its own data and behavior, rather than as a sequence of procedures acting on shared data.

class Account
{
private:
    double balance;
public:
    Account(double initial) : balance(initial) {}
    void deposit(double amt) { balance += amt; }
    double getBalance() const { return balance; }
};

A single class bundling data (balance) and behavior (deposit, getBalance) — this bundling is the core shift from procedural code.

Why this distinction is tested

Examiners ask "what is THE main characteristic of OOP" expecting a single, precise answer — not a list of the four pillars. The precise answer: OOP organizes a program around objects (bundled data + behavior) rather than around a sequence of procedures acting on shared data. Everything else (encapsulation, inheritance, polymorphism) follows from this one structural shift.

Side-by-side: solving the same problem, two ways

Procedural approach — data and functions are separate:

struct Account { double balance; };
void deposit(struct Account* a, double amt) { a->balance += amt; }
// Any function anywhere can touch a->balance directly -- no protection

OOP approach — data and functions are bundled, access is controlled:

class Account
{
private:
    double balance;
public:
    void deposit(double amt) { balance += amt; }   // only this class can touch balance directly
};

Consequences that follow from this one shift

• Data hiding becomes possible — since data lives inside the object, access modifiers can restrict it
• Code becomes reusable through inheritance — because behavior is attached to a class, not floating as free functions
• Objects map naturally to real-world entities — a Car object behaves like an actual car conceptually, aiding design and communication among developers

Important MCQs

1. The single most defining characteristic of OOP, as distinct from procedural programming, is:
   • a) Use of loops and conditionals b) Organizing code around objects that bundle data and behavior c) Faster compilation d) Absence of functions
2. In procedural programming, data is typically:
   • a) Bundled with functions b) Global/shared and accessed by many functions freely c) Always private d) Inaccessible
3. Which of these follows directly from OOP's core structural shift (bundling data + behavior)?
   • a) Faster runtime always b) Ability to apply access control (data hiding) c) No need for classes d) Removal of functions
4. A struct Account with a free function deposit(Account*, double) is an example of:
   • a) OOP encapsulation b) Procedural style — data and function are separate c) Polymorphism d) Inheritance