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.
559 results across 1 active filter
Page 22 of 24
Redesigns read-heavy shared state so readers observe a complete version without coordinating every access through a lock.
Explains the different diagnostic roles of logs, metrics, and traces during backend production issues.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Explains read models for complex API screens with practical .NET data-access examples and production trade-offs.
Explains Redis-backed rate-limit counters, atomic increments, windows, identity keys, and fallback behavior.
Explains the risks of Redis-based distributed locks and when database constraints, queues, or idempotency are safer.
Explains middleware continuation, terminal delegates, path branches, short-circuiting, and two-way request and response flow.
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 consumer-side deduplication atomic with the business change while supporting concurrent delivery, retention, replay, and failed processing.
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.
Implements a small validation helper for date ranges with clear error messages.
Explains JWT validation, trusted issuers, audiences, expiration, signing keys, claims, and server-side authorization boundaries.
Explains what is copied when values and object references are assigned or passed, including the explicit effect of ref, out, and in.
Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.
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 useful request, dependency, exception, log, metric, and availability telemetry for a production .NET API.
Covers symptom-based alerting for latency, error rate, availability, dependency failures, queue length, and resource pressure.
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Explains production ownership beyond writing code, including monitoring, alerts, support, and recovery.
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.