Question 610
A user receives two identical emails and audit logs show a business rule generated the same event on each update. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Inspect event queue entry, event name/parameters, notification condition, recipient preferences, delivery state, and repeated event generation. Event creation, notification evaluation, and email delivery are separate lifecycle stages; a queued event is not proof a message reached its user. The appropriate response is: Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs. Scenario: A user receives two identical emails and audit logs show a business rule generated the same event on each update.
Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs. Event creation, notification evaluation, and email delivery are separate lifecycle stages; a queued event is not proof a message reached its user. Verify prerequisites with: Inspect event queue entry, event name/parameters, notification condition, recipient preferences, delivery state, and repeated event generation. Scenario: A user receives two identical emails and audit logs show a business rule generated the same event on each update.
Incorrect Answers
Configure notification conditions, recipients, and message content against the correct table/event with clear suppression and access boundaries, then test actual delivery. This step may apply to Notification trigger recipient and content configuration but is not one of the complementary requirements in this case. The intended pair is: Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs. Together with: Inspect event queue entry, event name/parameters, notification condition, recipient preferences, delivery state, and repeated event generation. Scenario: A user receives two identical emails and audit logs show a business rule generated the same event on each update.
Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling. This step may apply to Trend indicators versus transactional reports but is not one of the complementary requirements in this case. The intended pair is: Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs. Together with: Inspect event queue entry, event name/parameters, notification condition, recipient preferences, delivery state, and repeated event generation. Scenario: A user receives two identical emails and audit logs show a business rule generated the same event on each update.
The script reads or changes only intended records with approved permission boundaries and predictable performance. This step may apply to GlideRecord server-side query and secure result handling but is not one of the complementary requirements in this case. The intended pair is: Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs. Together with: Inspect event queue entry, event name/parameters, notification condition, recipient preferences, delivery state, and repeated event generation. Scenario: A user receives two identical emails and audit logs show a business rule generated the same event on each update.


