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.
167 results across 1 active filter
Page 5 of 7
Explains transaction isolation levels with practical .NET data-access examples and production trade-offs.
Treats serializer naming, nulls, enums, converters, dates, references, and polymorphism as versioned client-facing behavior.
Separates the ASP.NET Core HTTP server from proxy, TLS, load-balancing, process-management, and forwarded-header responsibilities.
Explains LINQ translation boundaries with practical .NET data-access examples and production trade-offs.
Explains substitutability through inputs, outputs, side effects, and failure behavior rather than inheritance syntax alone.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Compare middleware and filters by scope, timing, endpoint context, and practical use cases.
Compare request binding and validation responsibilities in ASP.NET Core APIs.
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.
Separates OAuth authorization from OpenID Connect authentication and explains why modern interactive clients use authorization code with PKCE.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Uses stable extension points for genuinely variable behavior while avoiding speculative abstractions and configuration-driven branching.
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.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
Parses a simple filter expression into a validated dictionary without accepting arbitrary keys.
Places invariants and state transitions near the data they protect while keeping orchestration and infrastructure out of domain entities.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Secures webhooks, previews, imports, and remote-file fetches with destination policy, DNS and redirect defenses, egress controls, limits, and observability.
Uses RFC 9457 Problem Details as a stable, safe error contract with documented problem types, actionable extensions, and centralized ASP.NET mapping.
Explain why request cancellation should flow into EF Core queries and where it does or does not help.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.