Loading
Pick a focused question that fits your time, stack, and interview goal.
13 results across 1 active filter
Page 1 of 1
Compares server-controlled output caching with HTTP cache semantics and defines safe keys, variation, invalidation, identity, and multi-instance behavior.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Distinguishes request and response media types and designs predictable negotiation, rejection, documentation, and caching behavior.
Explains browser same-origin enforcement, preflight requests, credentials, middleware behavior, and why CORS is not authorization.
Chooses response cache directives for public, private, sensitive, and revalidated API data without leaking user-specific content.
Implements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.
Treats JSON serialization settings and DTO shape as a public contract, including naming, enums, nulls, converters, compatibility, and tests.
Explains how IHttpClientFactory separates short-lived clients from pooled handlers and how concurrency, DNS, resilience, and DI lifetimes still require judgment.
Compares replacement and partial-update semantics, including omitted fields, patch formats, validation, and concurrency.
Coordinates server retry signals with client backoff, deadlines, idempotency, overload protection, and bounded retry budgets.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
Designs cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.
Connects HTTP preconditions to atomic database concurrency checks and honest 412 or 428 API behavior.