Loading
Pick a focused question that fits your time, stack, and interview goal.
1345 results
Page 1 of 57
Separates hiding implementation complexity from controlling access to state, with practical examples where both ideas work together.
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
Uses public, internal, protected, private, and protected internal deliberately to control API surface and inheritance exposure.
Debugs matched rules, cascade origin, importance, layers, specificity, source order, inheritance, and computed values.
Compare controller ActionResult patterns with minimal API typed results and explicit HTTP outcomes.
Turns a production-only role and payload failure into the smallest durable API regression test.
Explains how tenant query filters help, where they can be bypassed, and what extra safeguards protect tenant isolation.
Explains physical connection reuse, pool partitioning, short ownership, exhaustion causes, diagnostics, and why increasing the pool is not the first fix.
Aggregates log entries into per-minute error counts with deterministic output.
Uses reduction, thread-local state, atomic scalar updates, or indexed output instead of mutating a shared collection from parallel workers.
Explains call-site-dependent this binding and compares wrapper, bind, and arrow-function fixes.
Uses traces and saturation evidence to locate retry amplification, queue growth, exhausted workers, and failing fallback paths.
Uses traces to separate unclear goals, bad tool interfaces, missing state, contradictory results, poor termination, and retry amplification.
Diagnoses an AI regression by decomposing request stages, configuration changes, token growth, retries, routing, tools, retrieval, caching, and provider behavior.
Reproduces failing cases, compares versioned traces, isolates the first changed component, mitigates impact, and adds regression coverage.
Traces buffering through the production artifact, proxy chain, compression, cache, platform adapter, and version consistency.
Diagnoses forced synchronous layout from interleaved geometry reads and style writes, then batches work and reduces its scope.
Explain API behavior when data and operations cross services with separate data ownership.
Explains attribute routing, binding-source inference, automatic validation responses, and where explicit domain validation still belongs.
Separates deployable artifact identity from client-facing contract compatibility, allowing frequent releases without unnecessary API-version churn.
Separates application composition in AppHost from reusable in-process defaults for telemetry, health, resilience, and service discovery.
Partitions limits by authenticated user or trusted client address and returns useful 429 retry metadata.
Design and debug rate limiting while protecting the API without blocking legitimate users and integrations.
Explains rate-limit identity, endpoint cost, login and suggestion throttles, Redis counters, user experience, and observability.