Loading
Pick a focused question that fits your time, stack, and interview goal.
167 results across 1 active filter
Page 6 of 7
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.
Evaluates repositories by domain language, query ownership, and substitutability instead of treating them as a mandatory wrapper around DbSet.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Handles the request body as a forward-only resource, buffers only when necessary, and enforces limits before large input consumes the service.
Explains how Aspire references inject resource configuration, how logical service names resolve, and why dependency wiring differs from startup readiness.
Explains why committed headers cannot be replaced, how streaming failures behave, and how middleware preserves response ownership.
Coordinates server retry signals with client backoff, deadlines, idempotency, overload protection, and bounded retry budgets.
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.
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.
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.
Uses separate models where they protect contracts, invariants, or storage evolution while avoiding repetitive mapping with no boundary value.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Explains EF Core shadow properties for audit or infrastructure columns with practical .NET data-access examples and production trade-offs.
Applies single responsibility to reasons for change, cohesive behavior, and maintainable service boundaries instead of counting methods.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Designs cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.
Expresses allowed and denied capability combinations as one parameterized API integration test.
Proves repeated requests with one idempotency key create one resource and return a consistent result.