Loading
Pick a focused question that fits your time, stack, and interview goal.
65 results across 1 active filter
Page 3 of 3
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains when to store large payloads outside the broker and pass references through messages.
Uses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.
Explains cache observability across hit rate, latency, source load, memory, evictions, stale data, and fallback behavior.
Compares OpenTelemetry-based Azure Monitor instrumentation with older Application Insights SDK patterns for .NET services.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.
Explains how to choose rollback, swap-back, hotfix, or roll-forward after a failed Azure App Service deployment.
Explains session state choices for scaled-out ASP.NET Core APIs and when Redis-backed state is appropriate.
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.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Explains local filesystem limits, multiple instances, in-memory state, distributed cache, durable storage, and scale-out-safe API design.