Enforcing max cluster and max node settings within a tenant.

Trying to create a cluster that violates the max will cause the
request to fail with a 409. Similarly, trying to lower the max
below whats already in use will cause the request to fail with a
409.
But what if as an administrator I want to reduce the tenant's quota below what the tenant is using right now? If you allow me to reduce the quota even if it causes violations now, later when the tenant deletes some cluster he won't be able to replace them. This will automatically cause the quota to be respected at that point. 

If you don't allow the admin to reduce the quota then he'll never be able to reduce a tenant's quota, right?