Loading
Pick a focused question that fits your time, stack, and interview goal.
237 results across 1 active filter
Page 1 of 10
Separates deployable artifact identity from client-facing contract compatibility, allowing frequent releases without unnecessary API-version churn.
Explains trusted tenant context, membership checks, tenant-scoped queries, cache keys, and background job propagation.
Compares build artifacts and deployment packages in a .NET release pipeline.
Builds a FastAPI POST boundary with separate input/output models, forbidden extra fields, domain mapping, and a 201 response.
Shows how task interleaving across await points can violate a multi-step invariant.
Explains how TTL choices balance freshness, load reduction, user expectations, and operational safety.
Compares test doubles by purpose and explains when a real dependency provides a more trustworthy test.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
Explains when CSRF matters, how cookies change browser behavior, and what mitigations fit API clients.
Explains how roles group permissions while API policies enforce specific capabilities and resource rules.
Explains how environment configuration drift causes deployment bugs and how to reduce it.
Separates ephemeral instance files from durable data and sends logs, uploads, caches, and diagnostics to storage with explicit lifecycle ownership.
Uses immutable image identity, controlled promotion, registry security, and deliberate base-image rebuilding instead of mutable latest tags.
Distinguishes request and response media types and designs predictable negotiation, rejection, documentation, and caching behavior.
Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.
Explains browser same-origin enforcement, preflight requests, credentials, middleware behavior, and why CORS is not authorization.
Explains database constraints versus application validation with practical .NET data-access examples and production trade-offs.
Explains the difference between deploying code and releasing functionality to users using feature flags.
Makes POST retries return one durable business outcome by combining scoped keys, request identity, atomic ownership, response replay, and reconciliation.
Explains password verification, hashing, throttling, generic errors, lockout, and safe login telemetry.
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Explains why message handlers must tolerate duplicate delivery and how idempotency protects side effects.