Loading
Pick a focused question that fits your time, stack, and interview goal.
618 drills fit a 20-minute session. Closest fits first.
Page 23 of 26
Explains referential integrity, cascade delete trade-offs, restrict behavior, soft deletes, and operational safety.
Explains route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.
Prevents lost updates with an original rowversion predicate, maps zero affected rows to an explicit conflict, and defines user, retry, aggregate, and API precondition behavior.
Explains Redis-backed rate-limit counters, atomic increments, windows, identity keys, and fallback behavior.
Explains HTTPS, HSTS, secure cookies, HttpOnly, SameSite, no-store, and practical API/browser security hardening.
Explains structured logging fields, safe context, redaction, event naming, and avoiding secret or personal-data leaks.
Makes business uniqueness race-safe with the exact database key, while handling normalization, tenant scope, nulls, soft deletion, rollout cleanup, and stable API conflicts.
Explains why external data needs runtime validation even when the application uses TypeScript.
Uses ROW_NUMBER with deterministic partition ordering to return one complete latest row per group, then evaluates index support, tie semantics, scale, and read-model alternatives.
Use SemaphoreSlim to bound concurrent asynchronous work without blocking threads unnecessarily.
Use Task.WhenAll to run independent asynchronous I/O operations concurrently while handling exceptions, cancellation, and dependency limits.
Explains JWT validation, trusted issuers, audiences, expiration, signing keys, claims, and server-side authorization boundaries.
Chooses code organization from change locality, shared policy, and cross-cutting needs rather than adopting one folder structure universally.
Compares App Service WebJobs and Azure Functions for queue processing, scheduled tasks, scaling, deployment ownership, and operational isolation.
Covers configuration that must stay with a slot, such as connection strings, secrets, callback URLs, and staging-only settings.
Covers symptom-based alerting for latency, error rate, availability, dependency failures, queue length, and resource pressure.
Explains practical pull request review signals for .NET services, including tests, API contracts, migrations, configuration, and operational impact.
Explain the async state machine, continuation scheduling, and exception flow when a C# method awaits a Task.
Explains N+1 queries in EF Core with practical .NET data-access examples and production trade-offs.
Explains how GC roots retain reachable object graphs and turns heap evidence into a concrete ownership fix for static state, events, closures, queues, and caches.
Explains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.
Distinguishes deterministic cleanup from finalization and explains resource ownership in normal application code.
Explains asynchronous cleanup for resources whose shutdown path needs async work, such as flushing or closing remote connections.