Loading
Pick a focused question that fits your time, stack, and interview goal.
140 results across 1 active filter
Page 1 of 6
Explains how tenant query filters help, where they can be bypassed, and what extra safeguards protect tenant isolation.
Explains physical connection reuse, pool partitioning, short ownership, exhaustion causes, diagnostics, and why increasing the pool is not the first fix.
Partitions limits by authenticated user or trusted client address and returns useful 429 retry metadata.
Loads a resource once, evaluates owner-or-capability authorization, and avoids trusting route ownership claims.
Pre-aggregates two one-to-many relationships before joining them to prevent fanout from corrupting financial totals.
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Implements bounded filtering and deterministic keyset pagination without accepting arbitrary query expressions.
Creates a resource through an explicit request DTO and returns typed 201, 409, and validation outcomes.
Builds several daily business metrics in one grouped query while keeping each metric definition explicit.
Explains composing dynamic LINQ filters while keeping query execution in SQL and index-friendly.
Uses an ordered window aggregate to calculate a deterministic running balance per account.
Combines daily aggregation, a calendar table, and a window frame to calculate true seven-calendar-day revenue.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Maps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.
Chooses constraints, conditional writes, optimistic conflicts, or stronger isolation to protect a limited-resource reservation without unnecessary blocking.
Designs a narrow covering index from predicates and ordering, then weighs eliminated lookups against storage, write overhead, cache efficiency, overlap, and maintenance cost.
Builds optional EF Core predicates while preserving server translation, stable ordering, and a bounded result.
Distinguishes instants, local calendar values, offsets, and named time zones so APIs and persistence survive daylight-saving and locale boundaries.
Investigate SQL timeouts that appear after a new .NET API release.
Traces duplicate side effects across message delivery, lock ownership, settlement, durable job state, and external idempotency, then repairs affected users safely.
Diagnose a .NET API that cannot connect to Azure SQL using managed identity.
Explains how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
Designs an async export flow for large reports without blocking API requests or exhausting database and memory resources.
Designs dashboard APIs with precomputed metrics, freshness rules, query cost control, and drill-down support.