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.
591 results across 1 active filter
Page 5 of 25
Explains bind addresses, published ports, internal DNS, service identity, and why localhost changes meaning across container boundaries.
Explains process isolation, shared kernels, image-based deployment, and where containers differ operationally from virtual machines.
Distinguishes request and response media types and designs predictable negotiation, rejection, documentation, and caching behavior.
Sets concurrency from the constrained resource and verifies throughput, latency, and downstream safety instead of maximizing active work.
Compare endpoint styles in real services, including organization, conventions, testing, filters, and OpenAPI behavior.
Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.
Serializes work for the same resource while preserving concurrency across independent keys and managing keyed-lock lifetime safely.
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.
Implements a word-frequency counter with normalization, punctuation handling, and stable ordering.
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.
Explains database constraints versus application validation with practical .NET data-access examples and production trade-offs.
Distinguishes instants, local calendar values, offsets, and named time zones so APIs and persistence survive daylight-saving and locale boundaries.
Explain why awaiting while holding synchronization resources can create deadlocks, contention, or stalled workflows.
Uses deadlock evidence to correct EF Core transaction scope, query plans, and resource order, with bounded retries only for repeat-safe victims.
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.
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.