Encapsulation best practices in C++ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is encapsulation in C++?

Encapsulation is the practice of hiding the internal details of a class and only exposing what is necessary through public methods. It helps protect data and keeps code organized.

beginner

Why should data members usually be private?

Making data members private prevents outside code from changing them directly. This protects the data from accidental or harmful changes and enforces controlled access.

beginner

What is the role of getter and setter functions?

Getter functions provide read access to private data, and setter functions allow controlled modification. They help maintain control over how data is accessed or changed.

intermediate

How does encapsulation improve code maintenance?

Encapsulation hides complex details inside classes, so changes inside do not affect other parts of the program. This makes it easier to update and fix code without breaking things.

intermediate

What is a good practice when designing setter functions?

Setter functions should validate input before changing data to keep the object in a valid state. This prevents bugs caused by invalid or unexpected values.

Which access specifier is best for data members to follow encapsulation?

A friend

B public

C protected

D private

Data members should be private to hide them from outside access and protect the object's state.

What is the main purpose of getter functions?

A Modify private data

B Delete private data

C Provide read access to private data

D Make data public

Getter functions allow safe reading of private data without exposing it directly.

Why should setter functions validate input?

A To prevent invalid data from corrupting the object

B To avoid using constructors

C To make data public

D To speed up the program

Validation ensures the object stays in a valid state and prevents bugs.

Encapsulation helps with which of the following?

A Hiding implementation details

B Writing longer code

C Making all data public

D Avoiding functions

Encapsulation hides internal details and exposes only what is necessary.

Which of these is NOT a benefit of encapsulation?

A Data protection

B Direct access to private data

C Improved code maintenance

D Controlled access to data

Encapsulation prevents direct access to private data to protect it.

Explain how encapsulation protects data in a C++ class.

Think about how you hide your personal information and only share what is necessary.

Describe best practices for designing setter functions in encapsulation.

Consider how you check information before accepting it.

Practice

1. What is the main purpose of encapsulation in C++?

easy

A. To make the program run faster

B. To hide data and protect it from unauthorized access

C. To allow direct access to all class members

D. To increase the size of the program

Solution

1. Step 1: Understand encapsulation concept

   Encapsulation means hiding the internal details of a class to protect data.

2. Step 2: Identify the main goal

   The goal is to prevent wrong or unauthorized changes by restricting direct access.

3. Final Answer:

   To hide data and protect it from unauthorized access -> Option B

4. Quick Check:

   Encapsulation = Data protection [OK]

Hint: Encapsulation means hiding data safely [OK]

Common Mistakes:

• Thinking encapsulation speeds up code
• Believing all data should be public
• Confusing encapsulation with inheritance

2. Which of the following is the correct way to declare a private data member in a C++ class?

easy

A. private: int age;

B. int age; // private by default

C. protected int age;

D. public int age;

Solution

1. Step 1: Recall C++ access specifiers

   Private members must be declared after the keyword 'private:' in a class.

2. Step 2: Check each option

   private: int age; uses 'private:' correctly before 'int age;'. Others are either public, protected, or missing specifier.

3. Final Answer:

   private: int age; -> Option A

4. Quick Check:

   Private members use 'private:' label [OK]

Hint: Use 'private:' label before private members [OK]

Common Mistakes:

• Assuming members are private by default
• Using 'private' without colon
• Declaring private members as public

3. What will be the output of this C++ code?

class Box {
private:
    int length;
public:
    void setLength(int len) { length = len; }
    int getLength() { return length; }
};

int main() {
    Box b;
    b.setLength(10);
    std::cout << b.getLength();
    return 0;
}

medium

A. 0

B. Compilation error

C. 10

D. Garbage value

Solution

1. Step 1: Understand class methods

   The method setLength sets the private member length to 10.

2. Step 2: Check output statement

   getLength returns length, which was set to 10, so output is 10.

3. Final Answer:

   10 -> Option C

4. Quick Check:

   Setter sets 10, getter returns 10 [OK]

Hint: Setter sets value, getter returns it [OK]

Common Mistakes:

• Expecting default 0 without setting
• Thinking private members can't be accessed via methods
• Confusing compilation error due to private member

4. Identify the error in this C++ class related to encapsulation:

class Person {
public:
    int age;
    void setAge(int a) { age = a; }
    int getAge() { return age; }
};

int main() {
    Person p;
    p.age = -5;
    std::cout << p.getAge();
    return 0;
}

medium

A. Age should be private to prevent invalid values

B. setAge method is missing return type

C. getAge should be private

D. No error, code is correct

Solution

1. Step 1: Check data member access

   Age is public, so it can be set directly to invalid value -5.

2. Step 2: Understand encapsulation best practice

   Age should be private and setAge should validate input to prevent invalid values.

3. Final Answer:

   Age should be private to prevent invalid values -> Option A

4. Quick Check:

   Private data prevents invalid direct changes [OK]

Hint: Make data private to control changes [OK]

Common Mistakes:

• Thinking public data is safe
• Believing getters should be private
• Ignoring validation in setters

5. You want to protect a class's data member balance so it cannot be set to a negative value. Which is the best encapsulation practice to achieve this?

hard

A. Make balance public and check value outside the class

B. Make balance protected and allow derived classes to set it freely

C. Remove balance and use a global variable instead

D. Make balance private and provide a setter that validates input

Solution

1. Step 1: Understand data protection need

   To prevent negative values, direct access must be blocked.

2. Step 2: Use private data with validation

   Making balance private and using a setter method to check values ensures safety.

3. Final Answer:

   Make balance private and provide a setter that validates input -> Option D

4. Quick Check:

   Private data + validated setter = safe encapsulation [OK]

Hint: Use private data and validate in setter [OK]

Common Mistakes:

• Leaving data public for easy access
• Using protected without validation
• Using global variables for encapsulation