A draft sequence for the city's protected Intersight inventory pull shows the resource GET before any token acquisition hop. What is wrong with that diagram from a Domain 1 sequence perspective?
Select an answer to reveal the explanation.
Short Explanation
You cannot knock on a locked door before you pick up the key. On the diagram, the token hop comes first; then the protected resource call. Wrong order is the defect—not a full OAuth lecture.
Full Explanation
DEVCOR 1.12 focuses on correct API call ordering on the sequence diagram. Hitting a protected resource before acquiring a token is an ordering error. Reciting every OAuth grant (Domain 2 depth), inventing NETCONF for Intersight retrieve, or omitting APIs entirely misses the sequence-order judgment.