Question 590
A SQL-derived notifications system generates the same event twice after a function retry. Which result distinguishes a successful implementation from a cosmetic change?
Explanation
Correct Answer
Change triggers and at-least-once deliveries demand explicit deduplication and checkpointing. The observation “Replaying the same event leaves one effective downstream change without data loss” directly confirms the chosen action worked for this situation: A SQL-derived notifications system generates the same event twice after a function retry.
Incorrect Answers
SQL trigger bindings integrate change detection into function execution but handlers need idempotency. This observation would not establish that the required result occurred for A SQL-derived notifications system generates the same event twice after a function retry. The confirming test is: Replaying the same event leaves one effective downstream change without data loss.
DAB configuration must be deployed with environment-specific secure connections and validated schema mappings. This observation would not establish that the required result occurred for A SQL-derived notifications system generates the same event twice after a function retry. The confirming test is: Replaying the same event leaves one effective downstream change without data loss.
MCP is an action gateway; server-side permissions and tool allowlists are necessary even with trusted prompts. This observation would not establish that the required result occurred for A SQL-derived notifications system generates the same event twice after a function retry. The confirming test is: Replaying the same event leaves one effective downstream change without data loss.