AZ-204 · Question #161
Case Study 7 - Proseware, Inc Background You are a developer for Proseware, Inc. You are developing an application that applies a set of governance policies for Proseware's internal services…
The correct answer is D. Create separate Azure Event Grid topics and subscriptions for sign-in and sign-out events. To process distinct sign-in and sign-out events for policy enforcement, it is best practice to configure separate Azure Event Grid topics and subscriptions. This ensures clear logical separation and allows for independent processing and policy actions tailored to each event type.
Question
Options
- AEnsure that signout events have a subject prefix. Create an Azure Event Grid subscription that
- BCreate a new Azure Event Grid topic and add a subscription for the events.
- CCreate a new Azure Event Grid subscription for all authentication that delivers messages to an
- DCreate separate Azure Event Grid topics and subscriptions for sign-in and sign-out events.
How the community answered
(21 responses)- A10% (2)
- B14% (3)
- C5% (1)
- D71% (15)
Why each option
To process distinct sign-in and sign-out events for policy enforcement, it is best practice to configure separate Azure Event Grid topics and subscriptions. This ensures clear logical separation and allows for independent processing and policy actions tailored to each event type.
Ensuring signout events have a subject prefix is a filtering mechanism but does not inherently provide the same level of architectural separation for distinct event handling as separate topics/subscriptions.
Creating a single new topic and a general subscription does not provide the specific distinction needed to handle sign-in and sign-out events separately for different policy actions.
Creating a single subscription for "all authentication" events would require the consuming application to implement the logic to differentiate and process sign-in and sign-out events, which is less efficient and scalable than using Event Grid's filtering or topic separation.
Creating separate Azure Event Grid topics and subscriptions for sign-in and sign-out events allows for distinct processing of each event type, enabling different policy actions to be applied independently and providing greater isolation and manageability for different authentication flows. This separation facilitates clearer event routing and specialized handling based on the specific event context.
Concept tested: Azure Event Grid topic and subscription design
Source: https://learn.microsoft.com/en-us/azure/event-grid/overview
Topics
Community Discussion
No community discussion yet for this question.