Encapsulation and information hiding in LLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Encapsulation in System Design

Which of the following best describes the main purpose of encapsulation in system design?

A To hide internal details and expose only necessary parts of a component

B To duplicate data across multiple components for redundancy

C To allow unrestricted access to all parts of a system for flexibility

D To increase the speed of data processing by exposing all internal data

💡 Hint

Think about protecting the inner workings of a system from outside interference.

Encapsulation means hiding internal details and exposing only what is necessary to use the component. This helps reduce complexity and improve security.

❓ Architecture

intermediate

Encapsulation in Microservices Architecture

In a microservices architecture, how is encapsulation typically achieved?

A By sharing the same codebase across all services to ensure consistency

B By exposing all internal databases to other services for direct access

C By storing all data in a single monolithic database accessible by all services

D By using APIs to expose only specific functionalities while hiding internal logic

💡 Hint

Consider how services communicate without revealing their internal workings.

Microservices encapsulate their internal logic and data by exposing only APIs. This hides complexity and allows independent development.

❓ scaling

advanced

Scaling Encapsulated Components

When scaling a system with encapsulated components, which approach best maintains information hiding?

A Allowing direct access to internal states of components to synchronize data

B Scaling components independently and communicating only through defined interfaces

C Merging components into a single large module to reduce communication overhead

D Replicating internal databases of components across all nodes for faster access

💡 Hint

Think about how components should interact when the system grows.

Scaling components independently while communicating only through interfaces preserves encapsulation and allows flexible scaling.

❓ tradeoff

advanced

Tradeoffs of Strict Information Hiding

What is a common tradeoff when applying strict information hiding in system design?

A Better security but potential performance overhead due to indirect access

B Simpler debugging but reduced modularity

C Improved flexibility but increased risk of data leaks

D Faster development but harder to maintain code

💡 Hint

Consider how hiding details might affect system speed.

Strict information hiding improves security and modularity but can add overhead because components access data indirectly through interfaces.

❓ component

expert

Identifying Encapsulation Violation in Component Design

Given a component that exposes its internal data structures directly to other components, what is the main issue?

A It improves encapsulation by sharing data openly for better collaboration

B It reduces coupling by allowing components to access data directly

C It violates encapsulation by exposing internal details, risking unintended modifications

D It enhances security by making data visible to all components

💡 Hint

Think about what happens when internal data is not hidden.

Exposing internal data structures breaks encapsulation, making the system fragile and prone to errors from unintended changes.

Practice

1. What is the main purpose of encapsulation in system design?

easy

A. To hide internal details and protect data from outside access

B. To make all data publicly accessible for easy modification

C. To increase the size of the system components

D. To allow direct access to all internal variables

Solution

1. Step 1: Understand encapsulation concept

   Encapsulation means hiding the internal details of a system or component so that outside code cannot directly access or change them.

2. Step 2: Identify the main goal

   The main goal is to protect data and control how it is accessed or modified, improving security and reducing errors.

3. Final Answer:

   To hide internal details and protect data from outside access -> Option A

4. Quick Check:

   Encapsulation = Hide details and protect data [OK]

Hint: Encapsulation means hiding details, not exposing them [OK]

Common Mistakes:

• Thinking encapsulation means making data public
• Confusing encapsulation with system size
• Believing encapsulation allows direct variable access

2. Which of the following is the correct way to implement encapsulation in a class?

easy

A. Make all variables public and access them directly

B. Avoid using any methods to access data

C. Use private variables and provide public getter and setter methods

D. Use global variables for all data

Solution

1. Step 1: Recall encapsulation implementation

   Encapsulation is done by making variables private so they cannot be accessed directly from outside the class.

2. Step 2: Use public methods for controlled access

   Public getter and setter methods allow controlled reading and updating of private data.

3. Final Answer:

   Use private variables and provide public getter and setter methods -> Option C

4. Quick Check:

   Private variables + public methods = Encapsulation [OK]

Hint: Private variables + public getters/setters = encapsulation [OK]

Common Mistakes:

• Making variables public defeats encapsulation
• Using global variables breaks encapsulation
• Not providing any access methods causes usability issues

3. Consider this code snippet in a system design context:

class Account {
  private balance = 1000;
  public getBalance() { return this.balance; }
  public setBalance(amount) { if(amount >= 0) this.balance = amount; }
}

const acc = new Account();
acc.setBalance(-500);
console.log(acc.getBalance());

What will be the output?

medium

A. -500

B. 1000

C. 0

D. Error

Solution

1. Step 1: Analyze setBalance method behavior

   The method only updates balance if the amount is greater than or equal to zero.

2. Step 2: Check the call with -500

   Since -500 is less than zero, the balance is not updated and remains 1000.

3. Final Answer:

   1000 -> Option B

4. Quick Check:

   Negative amount ignored, balance stays 1000 [OK]

Hint: Setter blocks negative values, so balance stays unchanged [OK]

Common Mistakes:

• Assuming balance changes to -500
• Expecting zero as default
• Thinking code throws an error

4. A developer wrote this code:

class User {
  public name;
  public setName(newName) { this.name = newName; }
}

const user = new User();
user.name = null;
console.log(user.name);

What is the problem related to encapsulation here?

medium

A. The name variable is public and can be set to invalid values directly

B. The setName method is missing

C. The class should not have any variables

D. The console.log statement is incorrect

Solution

1. Step 1: Identify variable access level

   The variable name is public, so it can be changed directly without validation.

2. Step 2: Understand encapsulation violation

   Direct access allows setting invalid values like null, bypassing any checks in setName.

3. Final Answer:

   The name variable is public and can be set to invalid values directly -> Option A

4. Quick Check:

   Public variable allows invalid direct access [OK]

Hint: Public variables can be changed without checks, breaking encapsulation [OK]

Common Mistakes:

• Thinking setName method is missing
• Believing variables should be removed
• Blaming console.log for output

5. You are designing a banking system where account balance must never be negative. Which approach best uses encapsulation and information hiding to enforce this rule?

hard

A. Make balance public and rely on users to not set negative values

B. Store balance as a global variable accessible everywhere

C. Do not provide any methods to access balance

D. Make balance private and provide a setter that only updates if amount ≥ 0

Solution

1. Step 1: Protect balance data

   Making balance private hides it from direct external changes, preventing accidental or malicious updates.

2. Step 2: Control updates via setter method

   The setter method enforces the rule by allowing updates only if the new amount is zero or positive.

3. Step 3: Avoid unsafe alternatives

   Public or global variables allow uncontrolled changes, risking negative balances and errors.

4. Final Answer:

   Make balance private and provide a setter that only updates if amount ≥ 0 -> Option D

5. Quick Check:

   Private balance + validated setter = safe encapsulation [OK]

Hint: Private data + validated setter enforces rules safely [OK]

Common Mistakes:

• Making balance public and trusting users
• Not providing access methods causes usability issues
• Using global variables breaks encapsulation