Loading
Pick a focused question that fits your time, stack, and interview goal.
439 results across 1 active filter
Page 15 of 19
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.
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.
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.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.
Compares revert and reset, especially for shared branches and production-safe history.
Reviews a proposed response-field rename by finding consumers, classifying the break, choosing a migration path, and proving rollout and removal are safe.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Compares rollback and roll-forward decisions after a failed production deployment.
Coordinates old and new application versions, expand-and-contract schema changes, migration ownership, readiness, and rollback during rolling releases.
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Explains safe handling of secrets and environment-specific configuration in CI/CD pipelines.
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.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Explains cached value serialization, schema versioning, deploy compatibility, and safe handling of old payloads.