Loading
Pick a focused question that fits your time, stack, and interview goal.
584 results across 1 active filter
Page 11 of 25
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.
Uses constraints to express required operations and explains safe assignment direction for generic producers and consumers.
Compares GitHub Actions and Azure DevOps at a practical .NET team level.
Explains how tags and release branches support traceability, hotfixes, and production versioning.
Explains global query filters in EF Core with practical .NET data-access examples and production trade-offs.
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Explain how a .NET BackgroundService should handle cancellation, in-flight work, and application shutdown.
Builds customer summaries from order rows using grouping, aggregation, and deterministic ordering.
Uses a test-only DbCommandInterceptor to fail a regression when database command count grows with page size.
Uses the client's original rowversion to detect a lost update and return a deliberate conflict response.
Builds a story about making competing work visible and helping the team choose intentionally.
Investigate and mitigate API failures caused by a slow or failing downstream dependency.
Separates caller cancellation from a dependency timeout and maps expected downstream outcomes safely.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.
Explains optimistic concurrency with EF Core rowversion tokens, API conflict responses, and safe retry boundaries.
Explains logout semantics for token-based APIs, revoking refresh tokens, device/session records, and short-lived access-token limits.