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.
473 results across 1 active filter
Page 3 of 20
Chooses database test infrastructure by the provider behavior a test must prove.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Chooses between sequence, counted, indexed, set, and dictionary contracts based on required operations and complexity.
Chooses counters, traces, stack snapshots, GC dumps, full dumps, or a profiler from the production symptom and investigation cost.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Implements chunking for batch processing without dropping final partial batches.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Explains what a lambda captures, how captured state is shared, and why a long-lived callback can retain more memory than expected.
Uses complexity as a first filter while accounting for constants, locality, allocations, data size, and the complete operation sequence.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
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.
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.
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.