Azure Event Grid Domain vs Custom Topic for Scaling
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are implementing an application by using Azure Event Grid to push near-real-time information to customers. You have the following requirements: • You must send events to thousands of customers that include hundreds of various event types. • The events must be filtered by event type before processing. • Authentication and authorization must be handled by using Microsoft Entra ID. • The events must be published to a single endpoint. You need to implement Azure Event Grid. Solution: Publish events to an event domain. Create a custom topic for each customer. Does the solution meet the goal?
Community Votes
64% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The key insight is that Event Domains act as meta-topics providing a unified publishing endpoint, whereas creating a custom topic per customer would fail scalability and endpoint constraints.
This question tests the architectural decision between using Azure Event Domains and custom topics for high-scale event publishing. The solution meets the goal by leveraging domains to manage thousands of topics under a single endpoint.
Candidates often choose 'No' because they incorrectly believe that each customer requires a distinct custom topic or overlook the domain's ability to handle massive topic counts via its quota limits.
Community Discussion (11 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
An Event Domain in Azure Event Grid is designed specifically to manage large numbers of related topics (up to 100,000) under a single management scope. It provides a single publishing endpoint for all topics within the domain, which satisfies the requirement to publish to a single endpoint while supporting thousands of customers. This architecture allows for efficient filtering and authorization at the topic or subscription level without needing separate endpoints per customer.Why the Other Options Are Wrong
Choosing 'No' implies the solution is flawed, but the proposed design aligns with Microsoft's recommended pattern for scaling Event Grid. The alternative of creating a custom topic for each customer would be inefficient and harder to manage at scale, though technically possible; however, the domain approach explicitly solves the 'single endpoint' constraint more elegantly. Option B is incorrect because it fails to recognize the domain's purpose.Community Comment Notes
Community feedback is split, with many users correctly identifying 'Yes' based on official documentation stating domains support up to 100,000 topics. Some users argue for 'No', citing that subscriptions are needed for filtering, but the solution description implies the necessary configuration exists. Others note that 'Domain Topics' are used within domains, not traditional custom topics, but this distinction does not invalidate the core benefit of the single endpoint and scalability.Official Reference
Exam Strategy
When asked about scaling Event Grid for many customers, prioritize Event Domains over individual custom topics if a single publishing endpoint is required. Always check if the scenario mentions 'thousands' of entities or a need for centralized management.
Frequently Asked Questions
Why is an Event Domain better than a custom topic for this scenario?
Event Domains support up to 100,000 topics and provide a single publishing endpoint, making them ideal for managing thousands of customers efficiently.
Can I use Event Subscriptions for filtering with Event Domains?
Yes, you can create event subscriptions on domain topics to filter events by type before processing, meeting the filtering requirement.