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.
405 results across 1 active filter
Page 17 of 17
Chooses code organization from change locality, shared policy, and cross-cutting needs rather than adopting one folder structure universally.
Covers useful request, dependency, exception, log, metric, and availability telemetry for a production .NET API.
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Explains production ownership beyond writing code, including monitoring, alerts, support, and recovery.
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 how route values, query strings, headers, and request bodies become typed endpoint input.
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.
Explains string immutability, concatenation behavior, and pragmatic use of StringBuilder in .NET.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Explains minimal APIs, endpoint groups, dependency injection, typed results, filters, and when they fit real services.
Introduces lower-level allocation tools while emphasizing measurement, ownership, and safe usage.
Identifies useful memory and GC signals for alerting without overwhelming the team with noisy telemetry.
Explain why async void is usually dangerous outside event handlers and how exceptions behave differently.
Explains how middleware order affects authentication, authorization, error handling, routing, CORS, and response behavior.
Explains cache memory growth, eviction, size limits, stale data, and why cache design needs explicit bounds.
Explains local filesystem limits, multiple instances, in-memory state, distributed cache, durable storage, and scale-out-safe API design.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.