You want to monitor FortiAuthenticator system information and receive FortiAuthenticator traps through SNMP. Which two configurations must be…

To effectively monitor a FortiAuthenticator and receive traps via SNMP, two key configurations are required after enabling the service on an interface. First, on the FortiAuthenticator itself, you must define the conditions that will trigger a trap message. This is done by setting system thresholds for metrics like CPU, memory, and disk usage. Second, on the SNMP management server, you must upload the FortiAuthenticator's Management Information Base (MIB) files. The MIBs act as a dictionary, enabling the SNMP server to decode the numeric Object Identifiers (OIDs) and trap information sent by the FortiAuthenticator into human-readable text.

A. Enable logging services.

This configures syslog, which is a separate monitoring protocol. Enabling logging services is not a requirement for SNMP traps to function.

C. Associate an ASN.1 mapping rule to the receiving host.

This is not a standard configuration step. The SNMP server uses the MIB files to interpret the data, not a manually configured ASN.1 mapping rule.

1. FortiAuthenticator 6.4 Administration Guide

Page 111

"SNMP" section.

Reference for B: Under the "SNMP Traps" subsection

it states: "The FortiAuthenticator SNMP agent can send traps to an SNMP manager when certain events occur

such as high CPU usage... Use the sliders to set the thresholds for CPU

memory

and log disk usage." This directly supports configuring thresholds to trigger traps.

Reference for D: Under the "Management Information Base (MIB) files" subsection

it states: "To view SNMP data from your FortiAuthenticator unit

you must compile these MIBs into your SNMP manager." This confirms the necessity of loading MIBs onto the SNMP server.