A retail network team runs a Catalyst Center lab and wants its Assurance eventing to POST a JSON payload into a chatbot when a client-health issue is raised, while a second engineer scripts the fabric site build with SD-Access automation APIs. Which configuration pair delivers both the event-driven webhook notification and the scripted fabric build?
Select an answer to reveal the explanation.
Short Explanation
You want the notification to fire on the Assurance client-health event, with a webhook delivering its JSON payload to the chatbot. Pair that with SD-Access automation for the fabric-site build, and you cover both needs. It’s a doorbell, not a nightly mail sweep.
Full Explanation
The required pairing is an event-driven Assurance notification configured to use a webhook, together with SD-Access automation APIs for the scripted fabric-site build. The webhook can deliver a JSON event to the chatbot when the specified client-health issue occurs, while the automation APIs address the separate need to create the fabric site programmatically. Sending Assurance device-availability alerts by webhook uses the right notification mechanism and fabric-build method, but its trigger is device availability rather than the stated client-health issue; changing the event type changes what condition raises the notification. Sending client-health JSON by Assurance webhook to the chatbot uses the appropriate event and destination, but configuration templates are a general mechanism for deploying device configurations, not the specified SD-Access automation API workflow for building a fabric site. Sending client-health JSON by Assurance webhook to a service desk uses the correct event type and fabric automation method, but the destination is a service desk instead of the required chatbot. Exam caveat: Catalyst Center offers several ways to notify systems and deploy configurations, so matching the tool category alone is not enough; check the event trigger, destination, and fabric workflow independently. As a practical check, raise a test client-health event and verify the chatbot receives the expected JSON, then confirm the site build is executed through the intended SD-Access automation API calls.