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

The correct answer is A. all service transition states B. service dependencies that have stopped or faulted E. services that have been disabled F. service fault management events. D is wrong - legacy instances are not managed by the SMF but they can only be observed using the facility and are not transferred into other states. G is wrong - On top of that I find the explanation here very misleading, since when has the SMF managed the processes state?…

Managing Services and Processes

Question

Options

Aall service transition states
Bservice dependencies that have stopped or faulted
Cservice configuration modifications
Dlegacy services that have not started
Eservices that have been disabled
Fservice fault management events
Gprocesses that have been killed

How the community answered

(54 responses)

A
78% (42)
C
2% (1)
D
7% (4)
G
13% (7)

Explanation

D is wrong - legacy instances are not managed by the SMF but they can only be observed using the facility and are not transferred into other states. G is wrong - On top of that I find the explanation here very misleading, since when has the SMF managed the processes state? Service state being offline doesn't not mean a process was killed. Well no arguing with A & E. Reason for B is because, even if it a service dependency but it is also monitored on it's own and when it stopped it means it changes state to either offline, etc. Reason for F: man svccfg setnotify {[-g] tset | class} notification_parameters Sets notifications parameters for software events and Fault Management problem lifecycle events in the SMF repository.

Topics

#SMF notification framework#service state transitions#fault management events#service monitoring

Community Discussion

No community discussion yet for this question.

Full 1Z0-821 Practice