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.
579 results across 1 active filter
Page 23 of 25
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 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.
Explains how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.
Makes consumer-side deduplication atomic with the business change while supporting concurrent delivery, retention, replay, and failed processing.
Explains why external data needs runtime validation even when the application uses TypeScript.
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.
Explains event schema evolution, backward compatibility, additive changes, consumer rollout, and contract ownership.
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.
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.
Defines abstraction as a deliberate contract over essential behavior, then explains practical C# boundaries and the cost of weak abstractions.