Clarification on layered enforcement: Strimzi Quota Plugin vs. Native User Quotas

[rizsk1220]

I am running Strimzi version 4.0.0 on kubernetes. I am looking to implement a two-layered quota system and want to confirm the expected behavior:
If I enable the StrimziQuotasPlugin (Static Quota Plugin) at the broker level to protect against disk exhaustion, does it correctly interoperate with native Kafka user quotas defined in KafkaUser resources?
In a scenario where both are active, does the broker prioritize the most restrictive limit (e.g., if a user quota allows 10MB/s but the broker plugin limits the total to 5MB/s due to disk pressure)?
Are there any known performance impacts or race conditions when these two mechanisms are used together?

[scholzj]

As far as I know, Kafka allows using only one Kafka plugin. So I think that if you enable the Strimzi quotas, the per-user quotas driven by Kafka's own plugin will be ignored.