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 4 of 25
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Builds a story about explaining engineering risk in business terms without hiding uncertainty.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
Compares cache-aside, read-through, and write-through by read and write ownership, freshness, failure behavior, invalidation, fallback, stampede control, and operational complexity.
Explains when CSRF matters, how cookies change browser behavior, and what mitigations fit API clients.
Explains when local process memory is enough and when shared Redis-style caching is worth the extra dependency.
Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.
Compares point-to-point queues with publish-subscribe topics and explains when each model fits.
Compares Redis pub/sub with durable queues when broadcasting cache invalidation or refresh events.
Explains how roles group permissions while API policies enforce specific capabilities and resource rules.
Implements comparison for simple semantic version strings with missing patch parts treated as zero.
Builds optional EF Core predicates while preserving server translation, stable ordering, and a bounded result.
Explains composite index column order with practical .NET data-access examples and production trade-offs.
Combines focused collaborators for independent behavior while recognizing cases where a genuine stable hierarchy remains simpler.
Choose between ConcurrentDictionary and explicit locks when managing concurrent in-memory data.
Explains how environment configuration drift causes deployment bugs and how to reduce it.
Explains how later configuration providers override earlier values and keeps secrets, environment overrides, and diagnostics within explicit boundaries.
Explain what ConfigureAwait(false) does, why it mattered historically, and how to reason about it in ASP.NET Core and library code.
Explains EF Core connection resiliency and retries with practical .NET data-access examples and production trade-offs.
Keeps images environment-neutral while handling configuration precedence, secret delivery, rotation, and startup validation safely.
Connects orchestrator requests and limits to .NET GC, thread-pool behavior, throttling, OOM termination, and capacity planning.
Separates ephemeral instance files from durable data and sends logs, uploads, caches, and diagnostics to storage with explicit lifecycle ownership.
Uses immutable image identity, controlled promotion, registry security, and deliberate base-image rebuilding instead of mutable latest tags.
Designs useful local database and cache resources without confusing container lifetime, durable data, bind mounts, parameters, and production secrets.