Why encapsulation matters in C Sharp (C#) - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of accessing private field directly

What will be the output of this C# code when trying to access a private field directly?

C Sharp (C#)

using System;
class BankAccount {
    private decimal balance = 1000m;
}

class Program {
    static void Main() {
        BankAccount account = new BankAccount();
        Console.WriteLine(account.balance);
        Console.WriteLine("Accessing balance directly");
    }
}

A 1000

B 0

C Compilation error: 'BankAccount.balance' is inaccessible due to its protection level

D Runtime error: NullReferenceException

💡 Hint

Private fields cannot be accessed outside their class.

The private field 'balance' is not accessible outside the BankAccount class, so trying to access it directly causes a compilation error.

❓ Predict Output

intermediate

Output of using public property to access private field

What will be the output of this C# code that uses a public property to access a private field?

C Sharp (C#)

using System;
class BankAccount {
    private decimal balance = 1000m;
    public decimal Balance {
        get { return balance; }
    }
}

class Program {
    static void Main() {
        BankAccount account = new BankAccount();
        Console.WriteLine(account.Balance);
    }
}

A Compilation error: Cannot access private field

B 1000

C 0

D Runtime error: NullReferenceException

💡 Hint

Public properties can expose private fields safely.

The public property Balance allows read-only access to the private field balance, so the output is 1000.

🧠 Conceptual

advanced

Why encapsulation improves code safety

Which of the following best explains why encapsulation improves code safety in object-oriented programming?

A It hides internal data and only exposes controlled access, preventing unintended changes.

B It forces the program to run faster by removing all checks on data.

C It makes all data public so any part of the program can modify it freely.

D It allows direct access to all variables to simplify debugging.

💡 Hint

Think about how hiding details helps protect data.

Encapsulation hides internal details and exposes only what is necessary, which prevents accidental or harmful changes to data.

🔧 Debug

advanced

Identify the encapsulation violation

Which option shows a violation of encapsulation principles in C#?

C Sharp (C#)

class Person {
    public string name;
    private int age;
}

A Making 'name' public allows external code to change it directly.

B Making 'age' private hides it from external access.

C Using a private field for 'age' protects it from unintended changes.

D Using properties to access 'age' is a violation of encapsulation.

💡 Hint

Encapsulation means hiding data from outside code.

Making 'name' public breaks encapsulation because external code can change it without control.

🚀 Application

expert

Result of modifying private field via method

What will be the output of this C# program that modifies a private field using a public method?

C Sharp (C#)

using System;
class Counter {
    private int count = 0;
    public void Increment() {
        count++;
    }
    public int GetCount() {
        return count;
    }
}

class Program {
    static void Main() {
        Counter c = new Counter();
        c.Increment();
        c.Increment();
        Console.WriteLine(c.GetCount());
    }
}

A 0

B Runtime error: NullReferenceException

C Compilation error: Cannot access private field

D 2

💡 Hint

Methods can safely modify private data inside the class.

The Increment method increases the private count field twice, so GetCount returns 2.

Practice

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

easy

A. To allow direct modification of class fields from anywhere

B. To hide the internal data of a class and protect it from outside access

C. To make all class data public for easy access

D. To increase the size of the program

Solution

1. Step 1: Understand encapsulation concept

   Encapsulation means hiding data inside a class to protect it from outside interference.

2. Step 2: Identify the purpose of encapsulation

   It prevents direct access to data, allowing control through methods or properties.

3. Final Answer:

   To hide the internal data of a class and protect it from outside access -> Option B

4. Quick Check:

   Encapsulation = Data protection [OK]

Hint: Encapsulation means hiding data inside classes [OK]

Common Mistakes:

• Thinking encapsulation makes all data public
• Confusing encapsulation with inheritance
• Believing encapsulation increases program size

2. Which of the following is the correct way to declare a private field in a C# class?

easy

A. private int age;

B. public int age;

C. int private age;

D. private: int age;

Solution

1. Step 1: Recall C# syntax for access modifiers

   In C#, the keyword private comes before the type and variable name.

2. Step 2: Check each option

   private int age; uses private int age; which is correct syntax for a private field.

3. Final Answer:

   private int age; -> Option A

4. Quick Check:

   Private field syntax = private int age; [OK]

Hint: Private fields start with 'private' keyword before type [OK]

Common Mistakes:

• Using 'public' instead of 'private' for private fields
• Placing 'private' after the type
• Using C++ style 'private:' which is invalid in C#

3. What will be the output of the following C# code?

class Person {
  private string name = "Alice";
  public string GetName() {
    return name;
  }
}

var p = new Person();
Console.WriteLine(p.GetName());

medium

A. Alice

B. name

C. Compilation error

D. null

Solution

1. Step 1: Understand private field and public method

   The field name is private but accessible inside the class. The method GetName() returns the value of name.

2. Step 2: Check the output of calling GetName()

   Calling p.GetName() returns "Alice", which is printed.

3. Final Answer:

   Alice -> Option A

4. Quick Check:

   Private field accessed via public method = Alice [OK]

Hint: Private data accessed through public method returns actual value [OK]

Common Mistakes:

• Expecting a compilation error due to private field
• Thinking it prints the field name 'name'
• Assuming null because field is private

4. Identify the error in this C# class that tries to encapsulate a field:

class BankAccount {
  private double balance;
  public double GetBalance() {
    return balance;
  }
  public void SetBalance(double amount) {
    balance = amount;
  }
}

var account = new BankAccount();
account.balance = 1000;

medium

A. Method SetBalance should return a value

B. GetBalance method should be private

C. Cannot access private field 'balance' directly outside the class

D. balance should be public to allow direct access

Solution

1. Step 1: Check access to private field outside class

   The code tries to assign account.balance = 1000; but balance is private, so this causes an error.

2. Step 2: Understand encapsulation rules

   Private fields cannot be accessed directly outside the class; access must be through methods like SetBalance.

3. Final Answer:

   Cannot access private field 'balance' directly outside the class -> Option C

4. Quick Check:

   Private fields block direct outside access [OK]

Hint: Private fields can't be accessed directly outside class [OK]

Common Mistakes:

• Thinking private fields can be accessed directly
• Believing setter methods must return values
• Assuming getters should be private

5. You want to protect a class field so it can only be set to positive values. Which encapsulation approach is best in C#?

hard

A. Make the field protected and allow subclasses to set any value

B. Make the field public and check values outside the class

C. Make the field private and provide a public getter only

D. Make the field private and provide a public setter method that validates the value

Solution

1. Step 1: Understand the need for validation

   To ensure only positive values are set, validation must happen inside the class.

2. Step 2: Choose encapsulation method

   Making the field private and using a public setter method with validation allows control over allowed values.

3. Final Answer:

   Make the field private and provide a public setter method that validates the value -> Option D

4. Quick Check:

   Private field + validated setter = safe data [OK]

Hint: Use private field with validated public setter method [OK]

Common Mistakes:

• Making field public and trusting external code
• Providing only a getter without setter
• Using protected without validation