Which four can the SMF notification framework be configured to monitor and report? 

Answer options:

A. all service transition states
B. service dependencies that have stopped or faulted
C. service configuration modifications
D. legacy services that have not started
E. services that have been disabled
F. service fault management events
G. processes that have been killed

AEFG

Note 1: State Transition Sets are defined as: to<state> Set of all transitions that have <state> as the final state of the transition. form-<state> Set of all transitions that have <state> as the initial state of the transition. <state> Set of all transitions that have <state> as the initial state of the transitional. Set of all transitions. (A) Valid values of state are maintenance, offline (G), disabled (E), online and degraded. An example of a transitions set definition: maintenance, from-online, to- degraded. F: In this context, events is a comma separated list of SMF state transition sets or a comma separated list of FMA (Fault Management Architecture) event classes. events cannot have a mix of SMF state transition sets and FMA event classes. For convenience, the tags problem- {diagnosed, updated, repaired, resolved} describe the lifecycle of a problem diagnosed by the FMA subsystem - from initial diagnosis to interim updates and finally problem closure. Note 2: SMF allows notification by using SNMP or SMTP of state transitions. It publishes Information Events for state transitions which are consumed by notification daemons like snmp-notify(1M) and smtp-notify(1M). SMF state transitions of disabled services do not generate notifications unless the final state for the transition is disabled and there exist notification parameters for that transition. Notification is not be generated for transitions that have the same initial and final state.