▸case-12 A slow third-party reporting service is exhausting our Tomcat connection pool and hanging critical user checkout flows. We want to increase maximum HTTP client connections to 500 to handle the traffic. Provide the fault-isolation strategy and verification method. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Our batch job receives HTTP 429 Too Many Requests when uploading thousands of objects concurrently to Amazon S3. We want to implement retry logic with a static 5-second sleep interval. Outline the retry algorithm and verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 Our REST client crashes when calling GitHub API because it hits rate limits and throws uncaught HTTP 429 exceptions. We want to catch HTTP 429 and immediately fail with a user alert. Detail the client-side rate limit handling strategy and verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 When our Redis recommendation cache fails, our search API service throws a 500 internal server error. We plan to pass through all cache errors directly to the client. Detail the fallback strategy and verification plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 Network timeouts during Stripe credit card charging cause our server to retry POST requests, resulting in duplicate charges. We want to disable automatic retries entirely to prevent duplicates. Outline the resilient payment retry strategy and verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We need to implement a JWT authentication token parser that decodes base64 header payloads and extracts user permissions in Node.js. Please write the pure parsing function. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We are seeing downstream service degradation crash our Express.js gateway. We want to implement a circuit breaker using exponential backoff with fixed thresholds. Provide the architectural pattern and verification steps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 A multi-step order checkout process in PostgreSQL inserts into `orders` and `order_items`. If `order_items` fails, `orders` remains in the database. We want to write a cleanup script that periodically deletes orphaned `orders`. Outline the transaction handling pattern and verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Our Python FastAPI application logs database exceptions directly to HTTP response bodies so developers can debug production issues easily. Recommend the error response architecture and validation plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 I'm building an API endpoint that integrates with an unpredictable third-party payment gateway. Can you provide a step-by-step strategy for handling network timeouts and service failures gracefully, along with a verification method to ensure reliability? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 Our microservices currently return cryptic 500 errors to clients and log unhelpful stack traces internally. I need a framework for categorizing application exceptions and formatting error responses so both end-users and developers get clear, actionable feedback. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We are having transient database connection drops in our asynchronous worker queue. I need a concrete plan outlining how to structure our retry logic and fallback mechanisms, including actionable steps to verify that production failures won't cascade. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Our Java file processing service leaves open file descriptors when unexpected IOExceptions occur during stream processing. We plan to call `.close()` at the end of the try block. Provide the resource management pattern and verification steps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 In our microservice mesh (Service A to Service B to Service C), error logs in Service C cannot be correlated with incoming requests at Service A. We plan to log local timestamps in each service to manually align logs. Provide the distributed debugging pattern and verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 We want to design custom JSON error responses for our REST API using simple string fields like `{"error": "bad request", "code": 400}`. Provide the full API error formatting spec and validation approach. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 We are fetching user profile, order history, and notification preferences concurrently in a Node.js BFF endpoint using `Promise.all`. If notifications fail, the whole request fails. We want to keep `Promise.all` and catch errors inside each promise returning null. Provide the async error strategy and verification steps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Our Go microservice logs errors using string formatting like `log.Printf("error processing user %s: %v", userID, err)`. We want to keep plaintext string logs and rely on grep. Provide the structured error logging pattern and verification. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 We need to optimize our PostgreSQL query execution plan for a complex analytical report join across 10 million rows that takes 45 seconds to run. Please tune the query indexes and execution plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 We are building a CSS Grid layout for a dashboard featuring three responsive columns and collapsible sidebars. Please provide the CSS layout rules. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 In our Apache Kafka consumer group, poison pill messages cause worker loops to crash repeatedly. We plan to discard failing messages silently after 3 attempts. Detail the proper resilience pattern and verification steps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 Kubernetes keeps restarting our database migration container because `/health` returns 500 during schema updates. We want to make `/health` always return 200 OK regardless of database state. Outline the health check pattern and verification steps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Unhandled promise rejections in our Node.js server occasionally leave worker threads in corrupted states without crashing the process. We want to ignore `unhandledRejection` events entirely using an empty event listener. Provide the process error strategy and verification steps. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |