Deferred execution behavior in C Sharp (C#) - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is deferred execution in C#?

Deferred execution means that the evaluation of a query or expression is delayed until its results are actually needed, not when the query is defined.

beginner

Which C# feature commonly uses deferred execution?

LINQ queries use deferred execution, meaning the query runs only when you iterate over the results, like with a foreach loop.

intermediate

How does deferred execution help with performance?

It avoids unnecessary work by only computing results when needed, which can save time and memory if the results are never used or only partially used.

intermediate

What happens if the data source changes after defining a deferred query but before iterating it?

Because execution is deferred, the query reflects the current state of the data source at the time of iteration, not when the query was defined.

intermediate

How can you force immediate execution of a deferred query in C#?

You can force immediate execution by calling methods like ToList(), ToArray(), or Count(), which evaluate the query right away.

What does deferred execution mean in C# LINQ?

A The query runs only when you iterate over its results

B The query runs immediately when defined

C The query runs only once at compile time

D The query runs only when the program starts

Deferred execution means the query is not executed until you actually use its results, such as in a foreach loop.

Which method forces immediate execution of a LINQ query?

A Where()

B OrderBy()

C Select()

D ToList()

ToList() forces the query to run immediately and stores the results in a list.

If the data source changes after defining a deferred query but before iterating it, what happens?

A The query results reflect the updated data source state

B The query results reflect the original data source state

C The query throws an error

D The query results are empty

Deferred execution means the query runs at iteration time, so it uses the current state of the data source.

Why is deferred execution useful?

A It makes the program run slower

B It forces all queries to run at program start

C It avoids unnecessary computation until results are needed

D It caches all query results permanently

Deferred execution delays work until necessary, improving efficiency.

Which of these LINQ methods does NOT cause immediate execution?

A Count()

B Select()

C ToList()

D ToArray()

Select() is a query operator that uses deferred execution; it does not execute immediately.

Explain deferred execution in C# and how it affects when a LINQ query runs.

Think about when the query results are actually created.

Describe how changing the data source after defining a deferred query impacts the query results.

When does the query get evaluated?

Practice

1. What does deferred execution mean in C# LINQ queries?

easy

A. The query runs only when you actually use its results.

B. The query runs immediately when it is defined.

C. The query results are stored permanently in memory.

D. The query runs multiple times automatically without control.

Solution

1. Step 1: Understand when LINQ queries run

   LINQ queries in C# do not run when defined but wait until their results are needed.

2. Step 2: Identify deferred execution meaning

   This means the query is executed only when you iterate over it or call methods like Count().

3. Final Answer:

   The query runs only when you actually use its results. -> Option A

4. Quick Check:

   Deferred execution = run when used [OK]

Hint: Deferred means delay running until results are needed [OK]

Common Mistakes:

• Thinking queries run immediately when defined
• Assuming results are stored permanently
• Believing queries run automatically multiple times

2. Which of the following C# code snippets correctly triggers deferred execution of a LINQ query?

easy

A. var result = numbers.Where(n => n > 5);

B. var filtered = numbers.Where(n => n < 3);

C. var query = numbers.Select(n => n * 2);

D. var count = numbers.Where(n => n > 5).Count();

Solution

1. Step 1: Identify code that triggers execution

   Calling Count() forces the query to run immediately and count matching elements.

2. Step 2: Compare other options

   The other options only define queries but do not execute them until iterated or a method like Count() is called.

3. Final Answer:

   var count = numbers.Where(n => n > 5).Count(); -> Option D

4. Quick Check:

   Calling Count() triggers execution [OK]

Hint: Methods like Count() force query to run immediately [OK]

Common Mistakes:

• Assuming query runs when assigned to a variable
• Confusing query definition with execution
• Not knowing which methods trigger execution

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

var numbers = new List<int> {1, 2, 3};
var query = numbers.Select(n => n * 2);
numbers.Add(4);
foreach(var num in query) Console.Write(num + " ");

medium

A. 2 4 6 8

B. 2 4 6

C. 1 2 3 4

D. 4 6 8

Solution

1. Step 1: Understand deferred execution with Select

   The query uses deferred execution, so it runs when the foreach starts, not when defined.

2. Step 2: Check list changes before execution

   Since numbers.Add(4) happens before foreach, the query sees the updated list including 4.

3. Final Answer:

   2 4 6 8 -> Option A

4. Quick Check:

   Deferred execution includes added item [OK]

Hint: Deferred queries reflect list changes before iteration [OK]

Common Mistakes:

• Thinking query runs at definition ignoring added items
• Confusing output with original list values
• Ignoring that foreach triggers execution

4. Identify the error in this code that prevents deferred execution from working as expected:

var numbers = new List<int> {1, 2, 3};
var query = numbers.Where(n => n > 1).ToList();
numbers.Add(4);
foreach(var num in query) Console.Write(num + " ");

medium

A. foreach loop syntax is invalid.

B. Using ToList() executes query immediately, so added item is ignored.

C. Cannot add items to a list after query definition.

D. The Where clause syntax is incorrect.

Solution

1. Step 1: Check effect of ToList()

   Calling ToList() executes the query immediately and stores results in a new list.

2. Step 2: Analyze list modification after execution

   Adding 4 to numbers after ToList() does not affect query because it is already a fixed list.

3. Final Answer:

   Using ToList() executes query immediately, so added item is ignored. -> Option B

4. Quick Check:

   ToList() disables deferred execution [OK]

Hint: ToList() runs query immediately, no deferred execution [OK]

Common Mistakes:

• Thinking ToList() keeps query deferred
• Believing list changes affect ToList() results
• Misreading Where clause syntax

5. You want to create a LINQ query that filters out numbers less than 5 and then doubles them, but you also want to avoid re-running the query multiple times for performance. Which approach correctly applies deferred execution but avoids repeated execution?

hard

A. Use a foreach loop inside the query to process items.

B. Define the query with var q = numbers.Where(n => n >= 5).Select(n => n * 2); and use it multiple times directly.

C. Define the query and immediately call ToList() to store results: var q = numbers.Where(n => n >= 5).Select(n => n * 2).ToList();

D. Call Count() on the query before using it to force execution.

Solution

1. Step 1: Understand deferred execution and repeated use

   Using the query directly runs it every time you iterate, which can be slow if repeated.

2. Step 2: Use ToList() to cache results

   Calling ToList() runs the query once and stores results, so repeated use is fast without re-executing.

3. Final Answer:

   Define the query and immediately call ToList() to store results. -> Option C

4. Quick Check:

   ToList() caches results, avoids repeated execution [OK]

Hint: Use ToList() to run once and reuse results efficiently [OK]

Common Mistakes:

• Using query directly causing multiple executions
• Misusing foreach inside query definition
• Calling Count() only counts, does not cache results