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.
591 results across 1 active filter
Page 11 of 25
Treats JSON serialization settings and DTO shape as a public contract, including naming, enums, nulls, converters, compatibility, and tests.
Preserves failure context, catches only where recovery or translation is possible, and uses filters without hiding unrelated faults.
Performs a set-based bulk update without loading session entities into the change tracker.
Explain async/await as C# syntax over Task-based asynchronous work, with attention to non-blocking I/O and request throughput.
Explains when stale cache reads are acceptable, when they are dangerous, and how to make freshness visible.
Explains how an HTTP request flows through ASP.NET Core middleware, routing, endpoint execution, and response generation.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Explains what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Explains static extension binding, instance-member precedence, namespace ambiguity, null receivers, and compatibility when APIs evolve.
Manages feature flags as temporary production controls with ownership, safe defaults, targeted rollout, telemetry, audit, failure behavior, and planned removal.
Explains filtered Include in EF Core with practical .NET data-access examples and production trade-offs.
Implements a stable first-unique-character search using counts and original order.
Explain why starting background work without awaiting or tracking it is risky in ASP.NET Core applications.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.
Flattens a tree into display paths while preserving order and preventing simple cycles.
Builds a story about turning an incident into regression guards, observability, and process improvement.
Restores client scheme, host, and address behind trusted proxies without accepting spoofed forwarding data from arbitrary callers.
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.
Uses constraints to express required operations and explains safe assignment direction for generic producers and consumers.
Compares GitHub Actions and Azure DevOps at a practical .NET team level.
Explains how tags and release branches support traceability, hotfixes, and production versioning.
Explains global query filters in EF Core with practical .NET data-access examples and production trade-offs.
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Explain how a .NET BackgroundService should handle cancellation, in-flight work, and application shutdown.