Loading
Pick a focused question that fits your time, stack, and interview goal.
618 drills fit a 20-minute session. Closest fits first.
Page 8 of 26
Debugs ASP.NET Core authentication challenges and authorization forbids across schemes, token validation, policies, claims, tenants, and resource checks.
Uses resource state, structured logs, traces, metrics, health, and configuration evidence to isolate a cross-service failure.
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.
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.
Builds a story about collaborating during an incident without chaos or duplicated work.
Investigate production failures caused by custom domain, DNS, TLS certificate, or HTTPS binding problems.
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.
Investigate resource spikes on App Service after a new .NET API release.
Investigate production HTTP 500 errors that start immediately after a deployment slot swap.
Diagnose missing trace continuity when an API enqueues work processed by an Azure worker.
Diagnose a .NET API that cannot connect to Azure SQL using managed identity.
Investigate a .NET API that appears to run but sends little or no telemetry to Application Insights.
Explains how to troubleshoot absent logs or telemetry by checking configuration, sampling, sinks, levels, deployment, and correlation.
Investigate messages that repeatedly fail and move to a poison queue or dead-letter queue.
Explains a constraint-first approach to responsive layout, intrinsic sizing, overflow, and content resilience.
Introduces API versions only for unavoidable breaks, with explicit routing, versioned documentation, migration support, telemetry, deprecation, and removal criteria.
Builds a risk-based frontend test strategy across unit, component, integration, contract, and end-to-end boundaries.
Explains soft delete in EF Core APIs with practical .NET data-access examples and production trade-offs.