Why interfaces are needed in C Sharp (C#) - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare an interface named IAnimal.

C Sharp (C#)

public interface [1] { string Speak(); }

Drag options to blanks, or click blank then click option'

AAnimalInterface

BAnimal

CIAnimal

DInterfaceAnimal

Attempts:

3 left

💡 Hint

Common Mistakes

Using class names instead of interface names

Not starting interface name with 'I'

The interface name should start with 'I' by convention, so IAnimal is correct.

2fill in blank

medium

Complete the code to make the Dog class implement the IAnimal interface.

C Sharp (C#)

public class Dog : [1] { public string Speak() { return "Woof!"; } }

Drag options to blanks, or click blank then click option'

ASpeakable

BDogInterface

CAnimal

DIAnimal

Attempts:

3 left

💡 Hint

Common Mistakes

Using a class name instead of interface

Forgetting to implement the interface

The class Dog implements the interface IAnimal using a colon.

3fill in blank

hard

Fix the error in the code by completing the interface method declaration.

C Sharp (C#)

public interface IAnimal { string [1](); }

Drag options to blanks, or click blank then click option'

ASpeak

BRun

CSleep

DEat

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different method name than in the class

Omitting the method name

The interface requires a method named Speak to be implemented by classes.

4fill in blank

hard

Fill both blanks to create a dictionary that maps animal names to their sounds using interface methods.

C Sharp (C#)

var sounds = new Dictionary<string, string> { {"Dog", dog.[1]()}, {"Cat", cat.[2]()} };

Drag options to blanks, or click blank then click option'

ASpeak

BMeow

DBark

Attempts:

3 left

💡 Hint

Common Mistakes

Using different method names for dog and cat

Using animal sounds as method names

Both dog and cat objects implement the Speak method from the interface.

5fill in blank

hard

Fill all three blanks to define an interface, implement it in a class, and call its method.

C Sharp (C#)

public interface [1] { string [2](); } public class Bird : [3] { public string Speak() { return "Chirp!"; } }

Drag options to blanks, or click blank then click option'

AIAnimal

BSpeak

DIBird

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching interface and class names

Using method names not declared in the interface

The interface is named IAnimal, the method is Speak, and the class Bird implements IAnimal.

Practice

1. Why do we use interfaces in C# programming?

easy

A. To define a contract that classes must follow

B. To store data like variables

C. To create graphical user interfaces

D. To write comments in code

Solution

1. Step 1: Understand the purpose of interfaces

   Interfaces specify methods that a class must implement, acting like a contract.

2. Step 2: Compare other options

   Options B, C, and D describe unrelated concepts: data storage, UI design, and comments.

3. Final Answer:

   To define a contract that classes must follow -> Option A

4. Quick Check:

   Interface purpose = contract [OK]

Hint: Interfaces define required methods, not data or UI [OK]

Common Mistakes:

• Confusing interfaces with classes
• Thinking interfaces store data
• Mixing interfaces with UI design

2. Which of the following is the correct way to declare an interface in C#?

easy

A. enum IExample { DoWork };

B. class IExample { void DoWork(); }

C. interface IExample { void DoWork(); }

D. struct IExample { void DoWork(); }

Solution

1. Step 1: Identify interface syntax

   In C#, interfaces are declared using the keyword interface followed by the name and method signatures.

2. Step 2: Check other options

   Options A, B, and C use enum, class, and struct keywords, which are not for interfaces.

3. Final Answer:

   interface IExample { void DoWork(); } -> Option C

4. Quick Check:

   Interface keyword = interface declaration [OK]

Hint: Look for 'interface' keyword to declare interfaces [OK]

Common Mistakes:

• Using class or struct instead of interface
• Missing method signature semicolon
• Confusing enums with interfaces

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

interface IAnimal { void Speak(); }
class Dog : IAnimal { public void Speak() { Console.WriteLine("Woof"); } }
class Cat : IAnimal { public void Speak() { Console.WriteLine("Meow"); } }
static void Main() {
  IAnimal animal = new Dog();
  animal.Speak();
  animal = new Cat();
  animal.Speak();
}

medium

A. Meow Woof

B. Woof Meow

C. Woof Woof

D. Meow Meow

Solution

1. Step 1: Understand interface usage

   The variable animal is of type IAnimal and first assigned a Dog object, so calling Speak() prints "Woof".

2. Step 2: Change object and call method again

   animal is then assigned a Cat object, so calling Speak() prints "Meow".

3. Final Answer:

   Woof Meow -> Option B

4. Quick Check:

   Interface variable calls method of assigned object [OK]

Hint: Interface variable calls method of current object type [OK]

Common Mistakes:

• Assuming interface variable fixes method output
• Mixing order of outputs
• Forgetting to implement interface methods

4. Identify the error in this code snippet:

interface IVehicle { void Drive(); }
class Car : IVehicle { }

medium

A. Car class should be abstract

B. Interface IVehicle cannot be empty

C. Drive() method should have a body in interface

D. Car class must implement Drive() method

Solution

1. Step 1: Check interface implementation rules

   A class implementing an interface must provide bodies for all interface methods.

2. Step 2: Analyze given code

   Car class implements IVehicle but does not define Drive(), causing a compile error.

3. Final Answer:

   Car class must implement Drive() method -> Option D

4. Quick Check:

   Implement all interface methods [OK]

Hint: Implement all interface methods in the class [OK]

Common Mistakes:

• Thinking interface methods have bodies
• Assuming empty class is valid implementation
• Confusing abstract class requirement

5. You want to write a method that accepts any object that can be saved to a database. Which approach best uses interfaces to achieve this?

hard

A. Define an interface ISaveable with method Save(), then accept ISaveable parameter

B. Use object type parameter and check type inside method

C. Create a base class Saveable and inherit from it

D. Write separate methods for each class type

Solution

1. Step 1: Understand interface benefits

   Interfaces allow different classes to share a common method signature, enabling polymorphism.

2. Step 2: Analyze options for flexibility and maintainability

   Define an interface ISaveable with method Save(), then accept ISaveable parameter uses an interface ISaveable with Save() method, allowing any class implementing it to be passed in.

3. Step 3: Compare other options

   Use object type parameter and check type inside method uses object and type checks, which is less clean. Create a base class Saveable and inherit from it uses inheritance, which is less flexible. Write separate methods for each class type duplicates code.

4. Final Answer:

   Define an interface ISaveable with method Save(), then accept ISaveable parameter -> Option A

5. Quick Check:

   Interfaces enable flexible method parameters [OK]

Hint: Use interface parameters for flexible method inputs [OK]

Common Mistakes:

• Using object and type checks instead of interfaces
• Relying only on inheritance
• Writing duplicate methods for each type