Logs are chronological records of all system and network occurrences, known as events. A log file, by its nature, contains a complete history. This includes events that have triggered alarms which are still active (representing an ongoing or "active" issue) as well as all other events that are purely historical (e.g., cleared faults, routine notifications). Therefore, logs serve as a comprehensive repository for both currently relevant and past event data.

B. This is an incomplete description. While the active alarm list provides a real-time status, the fault management system also maintains and reports on historical (cleared) alarms.

C. This is incorrect. The primary function of an alarm system is to provide immediate notification and status of current, active faults on the node.

D. This is conceptually incorrect. Logs record discrete, point-in-time events. They do not represent a persistent, consolidated "status" of a node; status is represented by alarms.

1. Nokia Network Services Platform (NSP) Fault Management Guide, Release 22.10

Reference for A and D: In the "Alarms vs. events" section, it is explained that an event is a single, atomic occurrence, while an alarm is a persistent condition. Logs are the records of these atomic events. This supports that logs contain all events (both related to active issues and purely historical ones) and do not represent a "status" themselves. (Document Part Number: 3HE-18278-AAAA-TQZZA, Chapter 2, "Alarm and event management").

Reference for B and C: The section "Active and historical alarms" explicitly states, "The NSP maintains a list of active alarms and a list of historical alarms." This confirms that the alarm system reports both real-time and historical information, making the statement in option B incomplete and the statement in option C incorrect. (Document Part Number: 3HE-18278-AAAA-TQZZA, Chapter 2, "Alarm and event management").