Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 18 of 29
Investigates a growing-data EF Core slowdown through one correlated request, generated SQL, representative parameters, execution plan, waits, query shape, measured repair, and guarded rollout.
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.
Chooses the correct typed-options lifetime, validates required configuration early, and handles runtime changes deliberately.
Explains `IQueryable` versus `IEnumerable` in EF Core with practical .NET data-access examples and production trade-offs.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Uses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.
Explains transaction isolation levels with practical .NET data-access examples and production trade-offs.
Treats serializer naming, nulls, enums, converters, dates, references, and polymorphism as versioned client-facing behavior.
Designs a reliable CI test system with fast feedback, deliberate test stages, bounded parallelism, visible flakiness, useful diagnostics, and clear ownership.
Explains when to store large payloads outside the broker and pass references through messages.
Separates the ASP.NET Core HTTP server from proxy, TLS, load-balancing, process-management, and forwarded-header responsibilities.
Balances declarative transformations with explicit control flow when allocation, early exit, mutation, diagnostics, or complex state matters.
Explains when LINQ is enough, when raw SQL is clearer, and how to keep raw SQL safe and maintainable.
Explains the small set of Kubernetes resources needed to run and expose a replicated stateless API without drowning the answer in platform vocabulary.
Builds a story about learning a new technology in a structured way and applying it safely.
Design a bounded-concurrency approach for calling an external API safely from .NET code.
Predicts when an in-memory LINQ pipeline runs and prevents repeated work, changed results, and hidden side effects.
Explains LINQ translation boundaries with practical .NET data-access examples and production trade-offs.
Explains substitutability through inputs, outputs, side effects, and failure behavior rather than inheritance syntax alone.
Uses `AsSplitQuery` deliberately for a tracked aggregate with multiple collections and explains its consistency boundary.
Compare lock and SemaphoreSlim for protecting shared state and coordinating async workflows.
Designs logs, metrics, traces, dashboards, and alerts around user outcomes, service objectives, dependencies, saturation, privacy, cardinality, and actionable incident response.
Builds a story about choosing a pragmatic technical path under time pressure while preserving future safety.