What causes the Connection Rejection?

You are reviewing SmartView Tracker entries, and see a Connection Rejection on a Check Point QoS rule. What causes the Connection Rejection?

A.
No QoS rule exists to match the rejected traffic

B.
The number of guaranteed connections is exceeded. The rule’s action properties are not set to accept additional connections

C.
The Constant Bit Rate for a Low Latency Class has been exceeded by greater than 10%, and the Maximal Delay is set below requirements

D.
Burst traffic matching the Default Rule is exhausting the Check Point QoS global packet buffers

E.
The guarantee of one of the rule’s subrules exceeds the guarantee in the rule itself

Explanation:

QoS rules with the track field set to Log can generate the following types of log events:
QoS rejects a connection when the number of guaranteed connections is exceeded, and/or when the rule’s action properties are not set to accept additional connections.
359, accel_ccse_ngx