Loading
Pick a focused question that fits your time, stack, and interview goal.
96 results across 1 active filter
Page 4 of 4
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.
Writes a left-join aggregate that keeps active customers with no paid orders and applies date filters without changing join semantics.
Uses ROW_NUMBER with a deterministic tie-breaker to return the complete latest status row per order.
Implements top-K frequency selection with deterministic tie-breaking.
Aggregates product sales and ranks independently inside each category with a deterministic top-N rule.
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.
Keeps data and secrets on the server while sending a small serializable model to an interactive client component.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Adds a stable query tag and inspects generated SQL without embedding user data or enabling unsafe global logging.
Tests validation, focus, pending state, and the save contract through accessible user interactions rather than component internals.
Tests one browser-to-database practice workflow with isolated fixtures, resilient locators, durable assertions, and reliable cleanup.
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.
Proves that one authenticated user cannot read or modify another user's private resource.
Uses a controllable fake HTTP handler to prove request cancellation reaches a downstream dependency.
Walks API pages through equal sort values and verifies no duplicate or missing resource ids.
Verifies status, content type, stable error extensions, and field errors for an invalid API request.
Tests that an unexpected failure returns a safe correlation identifier and records the same value in structured logs.
Attaches a key-only stub and marks one property modified for a narrow update while naming the rules this pattern bypasses.
Implements a small validation helper for date ranges with clear error messages.
Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.