Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 17 of 29
Explains upload UX, API boundaries, validation, progress, storage, scanning, failure handling, and safe download behavior.
Validates a bounded command set completely before applying all updates in one SaveChanges transaction.
Builds a bounded readiness check for one required dependency while keeping liveness independent and responses non-sensitive.
Applies an immediate reversible mutation, blocks overlapping writes, and restores the previous state on failure.
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Implements a small in-memory fixed-window rate limiter with per-key counters.
Implements a small LRU cache using a dictionary plus linked list for O(1) get and put.
Implements descending keyset pagination in LINQ using a compound timestamp-and-id cursor.
Explains debounce, cancellation, stale-response protection, loading indicators, and backend query safety for search UI.
Explains stable EF Core pagination using cursor predicates, deterministic ordering, and index-aligned queries.
Processes a large import in chunks with fresh DbContexts, idempotent keys, cancellation, and bounded tracker growth.
Builds a story about improving code quality incrementally while still delivering product value.
Builds a story about improving team workflow with lightweight, useful process changes.
Explains how to respond to a production incident caused by a bad release.
Explains `Include` versus `Select` in EF Core with practical .NET data-access examples and production trade-offs.
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
Uses inheritance only for stable behavioral subtyping and tests whether derived objects preserve the promises callers rely on.
Explains how to inspect EF Core generated SQL and connect LINQ shape to database execution behavior.
Uses WebApplicationFactory with test-only authentication and isolated dependencies to exercise the real ASP.NET Core pipeline.
Uses the real ASP.NET Core pipeline while replacing only environment-specific boundaries deliberately.
Designs consumer-focused contracts that reduce accidental authority and coupling without producing meaningless one-method wrappers.
Chooses between atomic operations and a critical section based on whether one value or a multi-step invariant must change safely.
Explains delete-on-write, versioned keys, event-driven invalidation, and the race conditions around cache freshness.
Explains refetching, targeted invalidation, stale data, optimistic updates, server truth, and user feedback after mutations.