Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
559 results across 1 active filter
Page 10 of 24
Explains split queries versus single joined queries with practical .NET data-access examples and production trade-offs.
Explains EF Core tracking versus no-tracking queries with practical .NET data-access examples and production trade-offs.
Uses controlled state transitions and intention-revealing APIs to keep objects valid rather than treating encapsulation as private fields alone.
Compare minimal API endpoint filters and MVC filters by context, scope, and use case.
Turns a modular-monolith choice into enforceable code and data ownership rather than relying on folders and team discipline alone.
Maps an HTTP ETag precondition to EF Core rowversion and returns 412 when the representation is stale.
Explains promoting artifacts through dev, staging, and production while managing configuration differences safely.
Connects equality semantics to hash-based collections and chooses identity or value equality deliberately.
Implements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.
Improves architecture through protected behavior, incremental boundaries, and measurable delivery instead of a risky all-at-once rewrite.
Treats JSON serialization settings and DTO shape as a public contract, including naming, enums, nulls, converters, compatibility, and tests.
Preserves failure context, catches only where recovery or translation is possible, and uses filters without hiding unrelated faults.
Performs a set-based bulk update without loading session entities into the change tracker.
Explain async/await as C# syntax over Task-based asynchronous work, with attention to non-blocking I/O and request throughput.
Explains when stale cache reads are acceptable, when they are dangerous, and how to make freshness visible.
Explains how an HTTP request flows through ASP.NET Core middleware, routing, endpoint execution, and response generation.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Explains what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Explains static extension binding, instance-member precedence, namespace ambiguity, null receivers, and compatibility when APIs evolve.
Manages feature flags as temporary production controls with ownership, safe defaults, targeted rollout, telemetry, audit, failure behavior, and planned removal.
Explains filtered Include in EF Core with practical .NET data-access examples and production trade-offs.
Implements a stable first-unique-character search using counts and original order.
Explain why starting background work without awaiting or tracking it is risky in ASP.NET Core applications.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.