Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
584 results across 1 active filter
Page 1 of 25
Separates hiding implementation complexity from controlling access to state, with practical examples where both ideas work together.
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
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.
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.
Aggregates log entries into per-minute error counts with deterministic output.
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 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.
Pre-aggregates two one-to-many relationships before joining them to prevent fanout from corrupting financial totals.
Explains when to derive values during render instead of storing duplicate state that can drift.
Explains dynamic filters and SQL injection risk with practical .NET data-access examples and production trade-offs.