Loading
Pick a focused question that fits your time, stack, and interview goal.
584 results across 1 active filter
Page 5 of 25
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.
Explains controlled inputs, uncontrolled inputs, validation, refs, and when each form approach fits.
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.
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.
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.
Uses deadlock evidence to correct EF Core transaction scope, query plans, and resource order, with bounded retries only for repeat-safe victims.
Combines debounce cleanup, AbortController, and request identity to prevent stale search results.
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.
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.
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.