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.
277 results across 1 active filter
Page 8 of 12
Compare request binding and validation responsibilities in ASP.NET Core APIs.
Starts object-oriented design from cohesive state and behavior instead of creating classes for every noun in a requirement.
Predicts how the built-in container resolves repeated service registrations and chooses explicit selection without service-location logic.
Explains multi-tenant data filtering with practical .NET data-access examples and production trade-offs.
Uses nullable annotations as a compile-time contract while still validating untrusted and legacy runtime inputs.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Designs an EF Core optimistic-concurrency contract around tokens, conflict policy, HTTP semantics, merge behavior, and real relational tests.
Uses a transactional outbox to make a local state change durably publishable while accepting at-least-once delivery and operating the backlog safely.
Separates compile-time overload selection from runtime virtual dispatch and diagnoses method hiding through a base reference.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
Compare Parallel.ForEachAsync and Task.WhenAll for processing collections with async work and controlled concurrency.
Parses a simple filter expression into a validated dictionary without accepting arbitrary keys.
Uses type, property, relational, and list patterns to express decisions while keeping null and unhandled cases explicit.
Chooses a parallel API based on whether the workload is a data query or an imperative loop and keeps CPU work pure, bounded, and measurable.
Finds circular lock acquisition and replaces timing-dependent nested locking with a stable order or a simpler ownership boundary.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Builds a read-only EF Core projection with aggregates, stable ordering, and bounded results instead of loading an entity graph.
Explain why request cancellation should flow into EF Core queries and where it does or does not help.
Carries the ASP.NET Core request token into a bounded EF Core query while keeping cancellation separate from business rollback guarantees.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.
Investigate and fix a race condition caused by shared mutable state in a .NET service.
Separates restricted mutation access from a stable immutable value and chooses snapshots or structural sharing deliberately.