NSE4 · Question #129
Caching improves performance by reducing FortiGate unit requests to the FortiGuard server. Which of the following statements are correct regarding the caching of FortiGuard responses? (Select all…
The correct answer is B. The cache uses a small portion of the FortiGate system memory. C. When the cache is full, the least recently used IP address or URL is deleted from the cache. D. An administrator can configure the number of seconds to store information in the cache before. FortiGuard caching uses a small portion of the FortiGate's memory, employs an LRU algorithm to manage capacity, and allows administrators to configure the time-to-live for cached responses.
Question
Caching improves performance by reducing FortiGate unit requests to the FortiGuard server. Which of the following statements are correct regarding the caching of FortiGuard responses? (Select all that apply.)
Options
- ACaching is available for web filtering, antispam, and IPS requests.
- BThe cache uses a small portion of the FortiGate system memory.
- CWhen the cache is full, the least recently used IP address or URL is deleted from the cache.
- DAn administrator can configure the number of seconds to store information in the cache before
- EThe size of the cache will increase to accomodate any number of cached queries.
How the community answered
(29 responses)- A7% (2)
- B90% (26)
- E3% (1)
Why each option
FortiGuard caching uses a small portion of the FortiGate's memory, employs an LRU algorithm to manage capacity, and allows administrators to configure the time-to-live for cached responses.
While caching is available for web filtering and anti-spam requests, it is not typically applied to IPS requests in the same manner, as IPS relies on real-time signature matching rather than caching external database lookups.
The FortiGuard cache primarily utilizes a small, dedicated portion of the FortiGate's system memory (RAM) to store frequently accessed FortiGuard responses, ensuring fast retrieval without impacting storage.
When the FortiGuard cache reaches its maximum capacity, it employs a Least Recently Used (LRU) algorithm, deleting the oldest and least frequently accessed entries to make room for new responses, optimizing cache efficiency.
FortiGate administrators can configure the cache time-to-live (TTL) in seconds, which dictates how long FortiGuard responses, such as web filter ratings or spam hashes, remain valid in the cache before being considered stale and requiring a fresh lookup.
The size of the FortiGuard cache is fixed or configurable within limits and does not dynamically increase indefinitely to accommodate an unlimited number of queries; it has a finite capacity.
Concept tested: FortiGuard caching mechanism and configuration
Source: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/321909/fortiguard-service-status
Topics
Community Discussion
No community discussion yet for this question.