Loading
Pick a focused question that fits your time, stack, and interview goal.
439 results across 1 active filter
Page 9 of 19
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.
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.
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.
Builds a story about making competing work visible and helping the team choose intentionally.
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.
Explains optimistic concurrency with EF Core rowversion tokens, API conflict responses, and safe retry boundaries.
Defines what happens when several operations fail, cancellation arrives, or only part of a parallel batch completes, without orphaning work or hiding errors.
Explains logout semantics for token-based APIs, revoking refresh tokens, device/session records, and short-lived access-token limits.
Explains Redis memory pressure, eviction policies, key sizing, TTL discipline, and what happens when the cache is full.
Explains how an API behaves when Redis is unavailable and which cache usages can safely fall back.
Explains stale edit detection, row versioning, conflict UI, refresh behavior, and safe update contracts.
Explains what happens when roles or tenant membership change while access tokens still contain old claims.
Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.
Explains why application-level duplicate checks are not enough and how EF Core APIs map database constraints to friendly errors.