Understanding SOLID PrinciplesC#

What does the 'S' in SOLID stand for?

• Singleton

• Static

• Single Responsibility

• Simple Rule

Why are SOLID principles important in software design?

• To make apps faster

• To create beautiful UIs

• To ensure maintainability and flexibility

• To avoid using classes

Which of the following is NOT one of the SOLID principles?

• Interface Segregation

• Inheritance Restriction

• Liskov Substitution

• Dependency Inversion

Which design principle is about separating concerns in your classes?

• Open/Closed

• Interface Segregation

• Single Responsibility

• Liskov Substitution

Which principle encourages using interfaces instead of concrete classes?

• DIP

• SRP

• LSP

• ISP

What’s the main benefit of using the Open/Closed Principle?

• Less code duplication

• Performance improvement

• Code that’s easy to modify directly

• Code that can be extended without modifying existing logic

Which principle helps avoid “fat” or bloated interfaces?

• LSP

• ISP

• OCP

• DIP

If a subclass changes the behavior of a base class and breaks functionality, which principle is violated?

• SRP

• DIP

• LSP

• OCP

How many responsibilities should a class ideally have according to SRP?

• One

• Two

• Unlimited

• Depends on the project

What’s a common way to enforce DIP in C#?

• Using static methods

• Using constructors or dependency injection containers

• Making fields public

• Using reflection