When URL category is not found in the kernel cache, what action will GW do?

Question

Options

• ARAD In user space will forward request to the cloud
• BGW will update kernel cache during next policy install
• CRAD in kernel space will forward request to the cloud
• DRAD forwards this request to CMI which is the brain of inspection

• A
  92% (24)
• B
  4% (1)
• C
  4% (1)

Explanation

When a URL category is not found in the kernel cache, the gateway escalates the lookup to user space, where RAD (the URL categorization daemon) handles the cloud query - making A correct. The kernel cache only stores previously resolved categories; a miss requires out-of-kernel processing, and the user-space RAD is the component responsible for reaching out to the cloud categorization service to resolve it.

Why the distractors are wrong:

• B is wrong because kernel cache updates happen after a category is resolved, not during policy installation - policy install doesn't trigger category lookups.
• C is wrong because kernel-space RAD handles the fast-path cache check, but it cannot make cloud calls; cloud communication happens in user space.
• D is wrong because CMI (Content Management Infrastructure) is part of the broader inspection pipeline, but it is not the component that forwards uncached URL requests to the cloud.

Memory tip: Think of it as a two-layer lookup - the kernel is the fast local cache (L1), and user-space RAD is the cloud fallback (L2). Kernel = check; User space = ask the cloud.

No community discussion yet for this question.