Loading
Pick a focused question that fits your time, stack, and interview goal.
206 results across 1 active filter
Page 6 of 9
Explains `Include` versus `Select` in EF Core with practical .NET data-access examples and production trade-offs.
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
Uses WebApplicationFactory with test-only authentication and isolated dependencies to exercise the real ASP.NET Core pipeline.
Explains refetching, targeted invalidation, stale data, optimistic updates, server truth, and user feedback after mutations.
Explains `IQueryable` versus `IEnumerable` in EF Core with practical .NET data-access examples and production trade-offs.
Uses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.
Treats serializer naming, nulls, enums, converters, dates, references, and polymorphism as versioned client-facing behavior.
Explains when to store large payloads outside the broker and pass references through messages.
Explains when LINQ is enough, when raw SQL is clearer, and how to keep raw SQL safe and maintainable.
Explains LINQ translation boundaries with practical .NET data-access examples and production trade-offs.
Uses `AsSplitQuery` deliberately for a tracked aggregate with multiple collections and explains its consistency boundary.
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.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains when backend work belongs in a queue instead of slow or unreliable inline request handling.
Explains multi-tenant data filtering with practical .NET data-access examples and production trade-offs.
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.
Parses a simple filter expression into a validated dictionary without accepting arbitrary keys.
Preserves order only within the business key that requires it, while handling hot keys, gaps, stale events, replay, and poison messages explicitly.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.
Explains why request DTOs should expose only allowed fields and how server-owned fields stay protected.