Question: When a new alarm is raised and AlarmList.administrativeState=UNLOCKED, how does the MnS producer update the AlarmList to reflect this new alarm, assuming no identical matching-criteria-attributes values exist in the list?
Option 1: Modify an existing alarmRecord in the AlarmList.alarmRecords attribute to accommodate the new alarm details.
Option 2: Add a new attribute element (referred to as an alarmRecord) to the AlarmList.alarmRecords attribute, representing the new alarm.
Option 3: Create a new AlarmList instance under the same ancestor MOI of type ManagedElement and/or Subnetwork.
Option 4: Update the NtfSubscriptionControl MOI to trigger a notifyNewAlarm notification without altering the AlarmList directly.
Explanation: When a new alarm is detected and the administrative state of the AlarmList is unlocked, the system ensures the AlarmList remains updated by adding a new entry for the alarm. This approach maintains historical integrity and allows for easy tracking of new alarms without overwriting existing records. The correct action, as per telecom fault management principles, is to add a new alarmRecord to the AlarmList.alarmRecords, ensuring each alarm has a distinct record for monitoring and management purposes.