Loading
Pick a focused question that fits your time, stack, and interview goal.
618 drills fit a 20-minute session. Closest fits first.
Page 20 of 26
Controls nondeterministic inputs without weakening production behavior or hard-coding test-only branches.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Chooses when to keep a sequence lazy and when to create a stable collection with ToList, ToArray, or another deliberate materialization.
Compares merge and rebase in team workflows, including history clarity, conflict handling, and shared branch safety.
Compare middleware and filters by scope, timing, endpoint context, and practical use cases.
Compare request binding and validation responsibilities in ASP.NET Core APIs.
Uses discriminated unions to represent valid UI states and make transitions exhaustive.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains how to monitor external and internal dependencies after a .NET service release.
Separates OAuth authorization from OpenID Connect authentication and explains why modern interactive clients use authorization code with PKCE.
Uses stable extension points for genuinely variable behavior while avoiding speculative abstractions and configuration-driven branching.
Compares OpenTelemetry-based Azure Monitor instrumentation with older Application Insights SDK patterns for .NET services.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
Explains versioning and releasing shared .NET libraries or NuGet packages safely.
Compare Parallel.ForEachAsync and Task.WhenAll for processing collections with async work and controlled concurrency.
Chooses a parallel API based on whether the workload is a data query or an imperative loop and keeps CPU work pure, bounded, and measurable.
Explains how to verify a .NET release after deployment using smoke tests, metrics, logs, and business signals.
Explains what happens when a hot key expires and how request coalescing, TTL jitter, background refresh, and stale serving help.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.
Explains why request DTOs should expose only allowed fields and how server-owned fields stay protected.
Uses RFC 9457 Problem Details as a stable, safe error contract with documented problem types, actionable extensions, and centralized ASP.NET mapping.
Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.
Explains where secrets and tokens should live, what not to log, how rotation works, and how client storage changes risk.