Pick a focused question that fits your time, stack, and interview goal.
439 results across 1 active filter
Page 4 of 19
Explains deployment markers, version telemetry, feature-flag state, commit traceability, and incident diagnosis after releases.
Explains browser same-origin enforcement, preflight requests, credentials, middleware behavior, and why CORS is not authorization.
Decide how to handle CPU-heavy work in an API without damaging request throughput or making the system unreliable.
Applies CQRS proportionally, separating model responsibilities without assuming separate databases, messaging, or event sourcing.
Creates and disposes explicit service scopes for hosted, queued, and parallel work without sharing scoped dependencies across operations.
Explains what belongs in runbooks, how on-call handoff preserves context, and how operational docs stay useful.
Explain why awaiting while holding synchronization resources can create deadlocks, contention, or stalled workflows.
Debugs ASP.NET Core authentication challenges and authorization forbids across schemes, token validation, policies, claims, tenants, and resource checks.
Handle a production support case where logs exist but related request events cannot be connected.
Diagnose a .NET API that fails to start on Azure App Service after a deployment.
Improve diagnosis when App Service log stream does not show enough information during an incident.
Diagnose App Service app settings that reference Key Vault secrets but fail at runtime.
Diagnose a deployment slot swap that fails because the target app does not warm up successfully.
Diagnose a growing queue backlog in an Azure-based background processing system.
Identify a failed App Service deployment caused by a mismatched .NET runtime or publish target.
Builds a story about collaborating during an incident without chaos or duplicated work.
Diagnose and recover from a production failure caused by rotated secrets or stale secret references.
Investigate production failures caused by custom domain, DNS, TLS certificate, or HTTPS binding problems.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Investigate SQL timeouts that appear after a new .NET API release.
Diagnose authentication redirect or callback failures after a slot swap or domain change.
Investigate an endpoint accepting invalid data or returning inconsistent validation errors.
Investigate a production issue caused by staging and production slot configuration drifting apart.
Diagnose browser CORS errors after moving an Azure-hosted API or frontend to a new custom domain.