Loading
Pick a focused question that fits your time, stack, and interview goal.
206 results across 1 active filter
Page 7 of 9
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Uses RFC 9457 Problem Details as a stable, safe error contract with documented problem types, actionable extensions, and centralized ASP.NET mapping.
Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.
Builds a read-only EF Core projection with aggregates, stable ordering, and bounded results instead of loading an entity graph.
Explain why request cancellation should flow into EF Core queries and where it does or does not help.
Carries the ASP.NET Core request token into a bounded EF Core query while keeping cancellation separate from business rollback guarantees.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Explains where secrets and tokens should live, what not to log, how rotation works, and how client storage changes risk.
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Compares replacement and partial-update semantics, including omitted fields, patch formats, validation, and concurrency.
Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.
Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Explains why committed headers cannot be replaced, how streaming failures behave, and how middleware preserves response ownership.
Classifies retryable outcomes and applies bounded attempts, exponential backoff, jitter, deadlines, and idempotency.
Persists a job and outbox command before returning a status URL for long-running work.
Produces field-keyed validation errors through one reusable endpoint boundary.
Explains safe error responses for auth failures, validation failures, server errors, and sensitive resource access.
Reviews a proposed response-field rename by finding consumers, classifying the break, choosing a migration path, and proving rollout and removal are safe.
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
Explains how multiple worker instances share queue work and what limits safe scaling.
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.