Courts IT creates a new custom Event Grid topic and webhook endpoint for workflow events. What must the endpoint handle during subscription setup?
Select an answer to reveal the explanation.
Short Explanation
Subscription validation is the courts’ “prove you own this mailbox” postcard—answer Event Grid’s handshake or the custom topic never starts delivering workflow events.
Full Explanation
When Courts IT creates a new custom Event Grid topic and webhook endpoint for workflow events, the endpoint must handle Event Grid subscription validation. During subscription creation, Event Grid sends a validation event (or uses the validation handshake mechanism for the delivery mode); the endpoint must prove ownership—typically by echoing the validation code—before cloud events flow. Without a correct validation response, the subscription never activates and municipal workflow events never arrive.
Ignoring validation handshakes and accepting only business events from day one fails setup: Event Grid will not confirm the subscription. Rejecting all Event Grid requests including the validation challenge likewise blocks activation. Requiring Service Bus sessions before any Event Grid subscription can exist confuses products: sessions are a Service Bus ordering feature and are not a prerequisite for Event Grid webhook confirmation.
Exam caveat: validation mechanics differ slightly between Event Grid event schema and CloudEvents delivery, and between webhook vs Azure resource handlers—know which your endpoint implements. Secure the webhook so only Event Grid (or authenticated callers) can post. Operational check: create the subscription, watch for the validation request in logs, return the correct validation response, confirm the subscription shows successful provisioning, then publish a test courts workflow event and verify delivery.