Azure Event Grid Partner Topic for Thousands of Customers?
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 a partner topic. Create an event subscription for each customer. Does the solution meet the goal?
Community Votes
82% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Partner topics are restricted by subscription limits (500 per topic) and cannot handle thousands of customers; Event Domains are required for multi-tenant routing at scale.
Publishing events to an Azure Event Grid partner topic fails to meet the goal of routing events to thousands of customers due to subscription limits. The correct architectural choice for this scenario is an Event Domain, which supports massive subscription counts and a single publishing endpoint.
Choosing Yes because partner topics sound like they handle partner/customer routing, ignoring the hard quota limits on event subscriptions per topic.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is "No" because a partner topic is subject to Azure Event Grid quota limits, specifically a maximum of 500 event subscriptions per topic. The requirement explicitly states the need to send events to thousands of customers, which translates to thousands of event subscriptions. Partner topics are designed for SaaS providers to broadcast events to Azure subscribers, but they lack the scale required for this specific requirement.Why the Other Options Are Wrong
Option A ("Yes") is incorrect because it assumes a partner topic can handle thousands of individual customer subscriptions, which violates Azure's service quotas. Furthermore, partner topics are intended for SaaS-to-Azure integrations, not for an application pushing near-real-time information to thousands of its own customers. The architecture that actually meets these requirements is an Event Domain, which provides a single endpoint and can manage thousands of topics and subscriptions.Community Comment Notes
Community members correctly point out that a partner topic cannot meet the goal due to subscription limits, as overhill noted, "Partner topics doesn't support thousands of subscriptions. only 100 per Azure Subscription". Raymond_abcd also highlighted that "The only possible solution is an event domain" because custom and partner topics are limited to 500 subscriptions. Robertical clarified the purpose of partner topics, stating they are for a "customer to send events to another system or application", which doesn't fit this scenario.Official Reference
Exam Strategy
For Event Grid questions requiring a single endpoint for thousands of customers or topics, immediately identify Event Domains as the solution. Be aware of Event Grid quotas, such as the 500 subscription limit per custom or partner topic.