Loading
Pick a focused question that fits your time, stack, and interview goal.
1345 results
Page 2 of 57
Traces a missed answer through source ingestion, parsing, chunking, filtering, query construction, retrieval, fusion, and ranking.
Traces synchronous throws and promise rejections through chains, awaits, missing returns, and detached work.
Separates container instance reuse from concurrency guarantees and designs singleton services around stateless or safely coordinated state.
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 audit fields and data change tracking with practical .NET data-access examples and production trade-offs.
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.
Separates optional, undefined, null, and invalid external data, then narrows values at the correct boundary.
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.
Builds a story about protecting quality while still making practical delivery decisions.
Explains when a value is wrapped as an object, why unboxing is exact, and how generic APIs can avoid hidden allocations.
Designs a pragmatic branching strategy for normal releases, hotfixes, and production traceability.
Builds a debounced typeahead with latest-request semantics, local error recovery, explicit states, and lifecycle-safe subscription ownership.
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Builds a bounded dynamic query that returns a read model, applies only supplied predicates, and uses deterministic ordering.
Implements labeled fields, client validation, error summaries, focus recovery, and pending submission state.