C# Interview

Design Patterns & Production Architecture

C# interview questions covering design patterns & production architecture.

10 Questions Filter by level

Interview questions

Open a question for the full answer, code and interview guidance.

10 Results
151
SeniorAdvanced

What is a design pattern?

A design pattern is a reusable conceptual solution to a recurring software-design problem. It describes relationships and responsibilities rather than providing code that must be copied exactly.

152
SeniorAdvanced

What is the Factory Pattern?

The Factory Pattern centralizes object creation and hides the decision about which concrete implementation should be instantiated.

153
SeniorAdvanced

What is the Strategy Pattern?

The Strategy Pattern defines interchangeable implementations of an algorithm or business rule behind a common contract.

154
SeniorAdvanced

What is the Repository Pattern?

The Repository Pattern provides an abstraction over data access and presents collection-like operations for domain or application code.

155
SeniorAdvanced

What is the Unit of Work Pattern?

Unit of Work coordinates multiple data changes so they can be committed as one logical transaction.

156
SeniorAdvanced

What is the Singleton Pattern, and how is it different from a DI singleton?

The traditional Singleton Pattern ensures that a class controls creation of a single instance and exposes global access to it.

157
SeniorAdvanced

What is the Decorator Pattern?

The Decorator Pattern wraps an existing implementation of an interface to add behavior without modifying the original implementation.

158
SeniorAdvanced

What is Clean Architecture?

Clean Architecture organizes software so core business rules do not depend directly on frameworks, databases, UI technology, or external infrastructure.

159
SeniorAdvanced

What is separation of concerns?

Separation of concerns means dividing software so different responsibilities are handled by appropriate components.

160
SeniorAdvanced

How would you structure a production ASP.NET Core application using C#?

A production ASP.NET Core application should have clear boundaries while remaining proportional to the application's complexity.