Loading
Pick a focused question that fits your time, stack, and interview goal.
298 results across 1 active filter
Page 13 of 13
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 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.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
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.