An eight-second UCS inventory sync on the user’s click path blows a city portal’s interactive latency objective. How should that slow Cisco-API work be placed?
Select an answer to reveal the explanation.
Short Explanation
Do not make a citizen wait at the counter while someone rebuilds the entire warehouse list. Accept the request and finish the slow UCS work on a queue. That protects the interactive SLO.
Full Explanation
An eight-second inventory sync on the user’s request path blows a latency objective. Returning accepted and finishing controller work on a queue protects the interactive SLO. This is synchronous versus asynchronous placement of slow Cisco-API work at design level, not a message-bus product exam.