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.
491 results across 1 active filter
Page 20 of 21
Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.
Explains event schema evolution, backward compatibility, additive changes, consumer rollout, and contract ownership.
Chooses code organization from change locality, shared policy, and cross-cutting needs rather than adopting one folder structure universally.
Compares App Service WebJobs and Azure Functions for queue processing, scheduled tasks, scaling, deployment ownership, and operational isolation.
Covers useful request, dependency, exception, log, metric, and availability telemetry for a production .NET API.
Covers configuration that must stay with a slot, such as connection strings, secrets, callback URLs, and staging-only settings.
Covers symptom-based alerting for latency, error rate, availability, dependency failures, queue length, and resource pressure.
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Explains practical pull request review signals for .NET services, including tests, API contracts, migrations, configuration, and operational impact.
Explain the async state machine, continuation scheduling, and exception flow when a C# method awaits a Task.
Explains LINQ deferred execution with EF Core with practical .NET data-access examples and production trade-offs.
Explains how route values, query strings, headers, and request bodies become typed endpoint input.
Clarifies the difference between objects being retained accidentally and code simply allocating too much temporary memory.
Explains N+1 queries in EF Core with practical .NET data-access examples and production trade-offs.
Explains how GC roots retain reachable object graphs and turns heap evidence into a concrete ownership fix for static state, events, closures, queues, and caches.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.
Explains Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Explains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.
Explains a practical CI/CD pipeline for .NET applications from code change to deployment verification.
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.
Distinguishes deterministic cleanup from finalization and explains resource ownership in normal application code.
Explains asynchronous cleanup for resources whose shutdown path needs async work, such as flushing or closing remote connections.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.