Loading
Pick a focused question that fits your time, stack, and interview goal.
439 results across 1 active filter
Page 1 of 19
Compare controller ActionResult patterns with minimal API typed results and explicit HTTP outcomes.
Turns a production-only role and payload failure into the smallest durable API regression test.
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.
Separates deployable artifact identity from client-facing contract compatibility, allowing frequent releases without unnecessary API-version churn.
Separates application composition in AppHost from reusable in-process defaults for telemetry, health, resilience, and service discovery.
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 rate-limit identity, endpoint cost, login and suggestion throttles, Redis counters, user experience, and observability.
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.
Clarify the common misconception that await starts work on a new thread, and explain what actually happens for I/O-bound operations.
Explains when cleanup needs asynchronous I/O, how await using guarantees disposal, and how ownership, exceptions, DI lifetimes, and shutdown affect the design.
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.
Builds a story about protecting quality while still making practical delivery decisions.
Designs a pragmatic branching strategy for normal releases, hotfixes, and production traceability.
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.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.