Loading
Pick a focused question that fits your time, stack, and interview goal.
206 results across 1 active filter
Page 1 of 9
Compare controller ActionResult patterns with minimal API typed results and explicit HTTP outcomes.
Explains how tenant query filters help, where they can be bypassed, and what extra safeguards protect tenant isolation.
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.
Explains rate-limit identity, endpoint cost, login and suggestion throttles, Redis counters, user experience, and observability.
Explains why sensitive admin actions need authorization, reason capture, before/after context, and tamper-resistant audit records.
Explains API keys, client credentials, managed identity, mTLS, scopes, rotation, and per-client observability.
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 trusted tenant context, membership checks, tenant-scoped queries, cache keys, and background job propagation.
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.
Explains composing dynamic LINQ filters while keeping query execution in SQL and index-friendly.
Compares caching response-shaped read models with caching domain entities or raw database objects.
Explains partition key selection for ordering, load distribution, hot keys, and consumer scalability.
Maps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.
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.