Loading
Pick a focused question that fits your time, stack, and interview goal.
57 drills fit a 5-minute session. Closest fits first.
Page 1 of 3
Separates hiding implementation complexity from controlling access to state, with practical examples where both ideas work together.
Uses public, internal, protected, private, and protected internal deliberately to control API surface and inheritance exposure.
Clarify the common misconception that await starts work on a new thread, and explain what actually happens for I/O-bound operations.
Separates identity establishment from permission decisions and applies ASP.NET Core schemes, policies, tenant boundaries, ownership checks, and correct challenge or forbid behavior.
Explains how TTL choices balance freshness, load reduction, user expectations, and operational safety.
Chooses a sequential collection from size, mutation, access pattern, memory locality, and the behavior callers actually need.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Explains when local process memory is enough and when shared Redis-style caching is worth the extra dependency.
Compares point-to-point queues with publish-subscribe topics and explains when each model fits.
Explains process isolation, shared kernels, image-based deployment, and where containers differ operationally from virtual machines.
Explains controlled inputs, uncontrolled inputs, validation, refs, and when each form approach fits.
Explains what belongs in runbooks, how on-call handoff preserves context, and how operational docs stay useful.
Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.
Explains dashboard panels that help an API owner see user impact, dependency health, releases, and current incidents.
Explains practical UI states for data fetching, empty results, partial failure, retry, and accessible recovery.
Explains how hash-based collections use hash codes and equality, then chooses Dictionary or HashSet from the value the program needs to store.
Uses controlled state transitions and intention-revealing APIs to keep objects valid rather than treating encapsulation as private fields alone.
Explain async/await as C# syntax over Task-based asynchronous work, with attention to non-blocking I/O and request throughput.
Explains join behavior using API-shaped data, missing related rows, and result-cardinality trade-offs.
Explains how React components render from props and state, and how updates flow through a component tree.
Explains how an HTTP request flows through ASP.NET Core middleware, routing, endpoint execution, and response generation.
Explains what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.
Explains controller actions, result types, status codes, thin controllers, and HTTP response generation.