Consider a proposed page for a gaming service: a tenant's scoped key has been revoked, but its previously admitted model requests still hold budget reservations. The responder sees refused requests alongside reserved spending, while the routing constraint says to pin a vendor or exclude one. Which decision stopped traffic? This is a design exercise, not an account of a production incident.
Short answer: excluding a provider ages better when the intended rule is that one destination must remain forbidden while other approved destinations can change. Pinning ages better when permission applies to exactly one provider, because adding another destination must require an explicit policy change. Neither rule enforces a tenant's spend ceiling or revokes its key.…