Architecture · interview question
Which option describes the most likely pitfall around background jobs?
Multiple choiceMediumchapter-18-curatedpremiumarchitecturebackground-jobs
Answer and explanation
Correct answer
D. Pushing work to background jobs casually can hide consistency and visibility problems instead of solving them.
Why
Pushing work to background jobs casually can hide consistency and visibility problems instead of solving them. Calling out that risk matters because strong answers explain why the job exists and how its boundary is observed.
Test yourself on Architecture
A free test with instant, explained results. No account needed.
More Architecture questions
- Which explanation would best help the team align on caching?
- A senior interviewer asks for one tradeoff behind environment-based deployment. What is the strongest follow-up?
- Another engineer will maintain this code later. What choice helps the most around caching?
- A teammate submits shaky idempotency code. Which review comment is the strongest?
- Which option is the safer default when shipping code around container and process shape?
- Which move is the best default when idempotency becomes part of this workflow?