Loading
Pick a focused question that fits your time, stack, and interview goal.
167 results across 1 active filter
Page 1 of 7
Compare controller ActionResult patterns with minimal API typed results and explicit HTTP outcomes.
Explain API behavior when data and operations cross services with separate data ownership.
Explains attribute routing, binding-source inference, automatic validation responses, and where explicit domain validation still belongs.
Partitions limits by authenticated user or trusted client address and returns useful 429 retry metadata.
Design and debug rate limiting while protecting the API without blocking legitimate users and integrations.
Explains how ASP.NET Core schemes select handlers and why authenticate, challenge, and forbid produce different security behavior.
Compares server-controlled output caching with HTTP cache semantics and defines safe keys, variation, invalidation, identity, and multi-instance behavior.
Explains audit fields and data change tracking with practical .NET data-access examples and production trade-offs.
Separates identity establishment from permission decisions and applies ASP.NET Core schemes, policies, tenant boundaries, ownership checks, and correct challenge or forbid behavior.
Loads a resource once, evaluates owner-or-capability authorization, and avoids trusting route ownership claims.
Explains dynamic filters and SQL injection risk with practical .NET data-access examples and production trade-offs.
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Explains admin list/edit/delete workflows with capability checks, audit events, confirmation, validation, and recovery.
Implements a safe in-memory paging helper with metadata and boundary handling.
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.
Explains permission-aware navigation, guarded routes, server authorization, stale capabilities, and safe 401/403 handling.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Explains composite index column order with practical .NET data-access examples and production trade-offs.
Explains how later configuration providers override earlier values and keeps secrets, environment overrides, and diagnostics within explicit boundaries.
Explains EF Core connection resiliency and retries with practical .NET data-access examples and production trade-offs.