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.
690 results
Page 13 of 29
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.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.
Moves non-deterministic browser-only rendering behind a stable server snapshot and post-hydration update.
Flattens a tree into display paths while preserving order and preventing simple cycles.
Uses a recursive CTE to return hierarchy depth and a readable root-to-node path.
Builds a story about turning an incident into regression guards, observability, and process improvement.
Restores client scheme, host, and address behind trusted proxies without accepting spoofed forwarding data from arbitrary callers.
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.
Explains client cache keys, freshness, invalidation, refetching, optimistic updates, and server truth.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.