Loading
Pick a focused question that fits your time, stack, and interview goal.
281 results across 1 active filter
Page 1 of 12
Separates hiding implementation complexity from controlling access to state, with practical examples where both ideas work together.
Uses public, internal, protected, private, and protected internal deliberately to control API surface and inheritance exposure.
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.
Aggregates log entries into per-minute error counts with deterministic output.
Uses reduction, thread-local state, atomic scalar updates, or indexed output instead of mutating a shared collection from parallel workers.
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.
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 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 when a value is wrapped as an object, why unboxing is exact, and how generic APIs can avoid hidden allocations.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
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.
Implements invoice total calculation with quantity, unit price, percentage discount, and rounding.
Design background jobs that handle cancellation, retries, and duplicate execution without corrupting external state.
Use CancellationToken to stop wasted work when clients disconnect, timeouts expire, or background operations are being shut down.