A city library wants branch managers notified when fine balances in SQL cross a configured threshold. Which Azure integration should they use?
Select an answer to reveal the explanation.
Short Explanation
You can use Azure Logic Apps as a polite tap on the shoulder: when fines cross the configured line in SQL, branch managers get notified. That beats waiting for an annual printout to reveal a breach.
Full Explanation
Azure Logic Apps is the right integration for this workflow because it can connect to SQL, evaluate fine balances against a configured threshold, and notify branch managers when that condition is met. This gives the library an automated way to respond to threshold crossings without building a custom always-on worker. Printing fine reports once a year and hoping managers notice breaches fails on timeliness: an annual report cannot prompt a response when a balance crosses the limit. Disabling notifications and storing thresholds only in a paper binder fails because the process is neither automated nor readily discoverable by the system evaluating the balances. Requiring patrons to verbally announce their own fine thresholds at the desk is unreliable and shifts detection away from the library’s system of record. Exam caveat: in DP-800 integration framing, sending threshold notifications based on SQL state maps to Logic Apps; the key is selecting the listed integration that can read SQL, evaluate a condition, and send an alert. For a practical check, build a Logic App that queries fine balances, compares them with the configured threshold, and notifies a test branch-manager channel. Insert a balance above the threshold in a library test database and confirm the alert fires once according to policy, with appropriate de-duplication.