Question 1 of 30
During a network audit of a corporate environment leveraging FortiAuthenticator for RADIUS authentication and accounting, it was discovered that while user authentication was consistently successful, intermittent gaps were observed in the session accounting records for approximately 500 concurrent users. These gaps manifested as missing session start or stop packets, potentially impacting compliance with logging requirements. The FortiAuthenticator\'s system health dashboard showed no critical alerts, and CPU and memory utilization remained within acceptable thresholds. What is the most likely underlying cause for these intermittent accounting record discrepancies, considering the system\'s overall stability?
Transient network congestion between FortiAuthenticator and the RADIUS accounting server, leading to dropped accounting packets.
An undersized RADIUS client configuration on the network access devices, causing them to fail to initiate or terminate accounting sessions properly.
A misconfiguration in the RADIUS accounting server's shared secret, causing accounting packets to be rejected by the server and not logged by FortiAuthenticator.
An outdated firmware version on the FortiAuthenticator, which has a known bug affecting the reliable processing of RADIUS accounting packets under moderate load.

Preparing for NSE6_FAC6.4 Fortinet NSE 6 FortiAuthenticator 6.4? Now land the interview.

73% of qualified candidates get rejected because of weak resumes. Build an ATS-optimized, recruiter-ready resume in under 5 minutes - free to start.

Build My Resume Free