Loading
Pick a focused question that fits your time, stack, and interview goal.
618 drills fit a 20-minute session. Closest fits first.
Page 11 of 26
Redesigns read-heavy shared state so readers observe a complete version without coordinating every access through a lock.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
Explains cache memory growth, eviction, size limits, stale data, and why cache design needs explicit bounds.
Diagnoses lost struct mutations and explains how readonly access can trigger defensive copies.
Uses reduction, thread-local state, atomic scalar updates, or indexed output instead of mutating a shared collection from parallel workers.
Explains trusted tenant context, membership checks, tenant-scoped queries, cache keys, and background job propagation.
Explains admin list/edit/delete workflows with capability checks, audit events, confirmation, validation, and recovery.
Explains caching and revalidation choices for static, dynamic, user-specific, and frequently changing data.
Chooses constraints, conditional writes, optimistic conflicts, or stronger isolation to protect a limited-resource reservation without unnecessary blocking.
Explains composite index column order with practical .NET data-access examples and production trade-offs.
Explains EF Core connection resiliency and retries with practical .NET data-access examples and production trade-offs.
Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Builds a race-safe upsert around database-enforced identity, explicit conflict semantics, retries, ordering, and side-effect boundaries.
Explains why message handlers must tolerate duplicate delivery and how idempotency protects side effects.
Protects transactional traffic from reporting load through freshness requirements, bounded asynchronous jobs, tuned summaries, workload isolation, replicas or warehouses, and explicit capacity gates.
Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.
Separates a live blocking chain from a deadlock victim, gathers the right database evidence, stabilizes the incident, and fixes lock duration or access order.
Explains split queries versus single joined queries with practical .NET data-access examples and production trade-offs.
Implements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.
Explains how consumer groups share event-stream work and how offset commits affect duplicate or lost processing.