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.
405 results across 1 active filter
Page 8 of 17
Maps an HTTP ETag precondition to EF Core rowversion and returns 412 when the representation is stale.
Explains promoting artifacts through dev, staging, and production while managing configuration differences safely.
Implements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.
Improves architecture through protected behavior, incremental boundaries, and measurable delivery instead of a risky all-at-once rewrite.
Treats JSON serialization settings and DTO shape as a public contract, including naming, enums, nulls, converters, compatibility, and tests.
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 what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Manages feature flags as temporary production controls with ownership, safe defaults, targeted rollout, telemetry, audit, failure behavior, and planned removal.
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.
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.
Compares GitHub Actions and Azure DevOps at a practical .NET team level.
Explains how tags and release branches support traceability, hotfixes, and production versioning.
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.
Uses a test-only DbCommandInterceptor to fail a regression when database command count grows with page size.
Uses the client's original rowversion to detect a lost update and return a deliberate conflict response.
Investigate and mitigate API failures caused by a slow or failing downstream dependency.
Separates caller cancellation from a dependency timeout and maps expected downstream outcomes safely.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.