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 10 of 25
Implements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.
Improves architecture through protected behavior, incremental boundaries, and measurable delivery instead of a risky all-at-once rewrite.
Treats JSON serialization settings and DTO shape as a public contract, including naming, enums, nulls, converters, compatibility, and tests.
Preserves failure context, catches only where recovery or translation is possible, and uses filters without hiding unrelated faults.
Performs a set-based bulk update without loading session entities into the change tracker.
Explain async/await as C# syntax over Task-based asynchronous work, with attention to non-blocking I/O and request throughput.
Explains why list keys matter for reconciliation, state preservation, reordering, and predictable UI behavior.
Explains how React components render from props and state, and how updates flow through a component tree.
Explains when stale cache reads are acceptable, when they are dangerous, and how to make freshness visible.
Explains how an HTTP request flows through ASP.NET Core middleware, routing, endpoint execution, and response generation.
Connects JavaScript tasks and microtasks to rendering, responsiveness, and practical performance fixes.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Explains what useEffect is for, how dependencies work, and how to avoid stale or runaway effects.
Explains what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Explains static extension binding, instance-member precedence, namespace ambiguity, null receivers, and compatibility when APIs evolve.
Manages feature flags as temporary production controls with ownership, safe defaults, targeted rollout, telemetry, audit, failure behavior, and planned removal.
Explains filtered Include in EF Core with practical .NET data-access examples and production trade-offs.
Uses EXISTS instead of a row-multiplying join when the related table is only a filter.
Groups normalized email values to identify duplicates before adding or repairing a uniqueness rule.
Uses the gaps-and-islands pattern to find consecutive login-day streaks after deduplicating same-day activity.
Solves a many-to-many all-match filter with grouping and a deliberate empty-selection rule.
Implements a stable first-unique-character search using counts and original order.
Uses NOT EXISTS to express an anti-join without null traps or duplicate parent rows.
Explain why starting background work without awaiting or tracking it is risky in ASP.NET Core applications.