A topic calls a cloud flow to reserve inventory. The flow can fail when stock is insufficient or the API times out. What should the topic include?
Select an answer to reveal the explanation.
Short Explanation
Happy-path-only topics strand users when services hiccup. You should branch on failure: explain what happened, offer alternatives, or escalate — like a store associate who doesn’t freeze when an item’s out of stock.
Full Explanation
Handle connector/flow failures with conditions, outcome checks, and clear UX. Correct: error branches/outcome checks with friendly messages and alternatives (retry, suggest similar items, escalate), not only happy path. Wrong: no-error-path assumes flows never fail; display-name e check is irrelevant; deleting inventory table is destructive. Exam tip: design for 429/timeouts/business failures.