Debugging Across the Seam — Concept Check
Questions on Debugging Across the Seam. When something fails between two deployables, the first job is deciding which side it is on. A method for that is worth more than knowledge of any particular bug.
Questions in this quiz
7 questions on Debugging Across the Seam — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A frontend developer sees a failed request and blames the API, while the backend developer sees a 200 in the logs and blames the client. What should be the first step to resolve this?
- ACheck the database for issues
- BCheck the network tab in the browser
- CReproduce the request with curl
- DDirectly check server logs
2.A request fails with a 422 status code. What should you do next?
- ARead the response body for field errors
- BCheck for network issues
- CRetry the request
- DAssume a server-side bug
3.A request works in Postman but fails in the browser. What is likely the issue?
- AThe server is down
- BNetwork tab shows no request
- CCORS or cookie differences
- DThe API endpoint is incorrect
4.You receive a 401 error only in production. What might be the cause?
- ANetwork latency
- BIncorrect request payload
- CA missing API endpoint
- DCross-site cookie issues
5.A bug only occurs on the first page load, resulting in a 401 error. What could be the cause?
- ANetwork latency
- BIncorrect request payload
- CA missing API endpoint
- DServer-side rendering without forwarding cookies
6.What is the purpose of having a request id on every request?
- ATo ensure data consistency
- BTo improve network speed
- CTo correlate client and server logs for the same request
- DTo identify which server handled the request
7.A 500 error occurs before CORS middleware runs, leading to no headers. What is the telltale sign?
- AA stack trace in the server log
- BA successful response in Postman
- CA 422 error in the response
- DA 404 error in the browser