In debugging security rules, what does the blue color code indicate?

In debugging security rules, what does the blue color code indicate?

• A. that the ACL is already in the cache and does not need to be re-evaluated
• B. that the ACL is failing
• C. that the ACL is not found
• D. that the ACL is being reloaded

Answer: (A)

Blue in the security rule debugging view marks a cache hit. It means the ACL decision was already computed and stored in the ACL cache, so the engine reused that result instead of re-evaluating the rule from scratch. This reflects efficient handling, as repeated checks for the same user and resource can skip the full evaluation. If you change ACL rules, the cached decision may become stale until the cache is refreshed or cleared, which is when you’d see new evaluations take place.

Blue in the security rule debugging view marks a cache hit. It means the ACL decision was already computed and stored in the ACL cache, so the engine reused that result instead of re-evaluating the rule from scratch. This reflects efficient handling, as repeated checks for the same user and resource can skip the full evaluation. If you change ACL rules, the cached decision may become stale until the cache is refreshed or cleared, which is when you’d see new evaluations take place.