Why understanding memory matters in C# - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this C# code related to memory allocation?

Consider this C# code snippet that uses value and reference types. What will be printed?

C Sharp (C#)

int a = 5;
int b = a;
b = 10;
Console.WriteLine(a);

A 5

B 10

C 0

D Compilation error

💡 Hint

Think about how value types are copied in memory.

In C#, integers are value types. When you assign b = a, it copies the value. Changing b does not affect a. So a remains 5.

❓ Predict Output

intermediate

What is the output when modifying a reference type in C#?

Look at this code that uses a class instance. What will be printed?

C Sharp (C#)

class Box { public int Size; }

Box box1 = new Box() { Size = 5 };
Box box2 = box1;
box2.Size = 10;
Console.WriteLine(box1.Size);

A Compilation error

B 0

C 5

D 10

💡 Hint

Remember how reference types share the same memory location.

Classes are reference types. Both box1 and box2 point to the same object. Changing box2.Size changes box1.Size too.

🔧 Debug

advanced

What error does this C# code raise related to memory usage?

Examine this code snippet. What error will it cause when run?

C Sharp (C#)

int[] numbers = new int[3];
numbers[3] = 10;
Console.WriteLine(numbers[3]);

A NullReferenceException

B Compilation error

C IndexOutOfRangeException

D No error, prints 10

💡 Hint

Check the array size and the index used.

The array has size 3, so valid indices are 0, 1, 2. Accessing index 3 is out of bounds and throws IndexOutOfRangeException.

🧠 Conceptual

advanced

Why is understanding stack vs heap important in C#?

Which statement best explains why knowing the difference between stack and heap memory matters in C#?

A Because stack memory is used for reference types and heap for value types

B Because value types are stored on the stack and reference types on the heap, affecting performance and lifetime

C Because both stack and heap store data permanently until program ends

D Because only heap memory is managed by the garbage collector

💡 Hint

Think about where value and reference types live and how that affects speed and memory cleanup.

Value types are stored on the stack which is fast and short-lived. Reference types are stored on the heap which is slower but allows dynamic memory and is managed by the garbage collector.

🚀 Application

expert

How many objects are created in this C# code snippet?

Analyze this code and determine how many objects are created in memory.

C Sharp (C#)

class Person { public string Name; }

Person p1 = new Person() { Name = "Alice" };
Person p2 = new Person() { Name = "Alice" };
string s = "Alice";

A 3

B 4

C 1

D 2

💡 Hint

Consider how string literals are interned and how many class instances are created.

Two Person objects are created with new. The string "Alice" is interned, so only one string object exists despite multiple references. Total objects created in memory: 3.