AZ-204 practice question 17 of 35

You are implementing an application by using Azure Event Grid to push near-real-time information to customers. You have the following requirements: •…

Full set: 489 questions

Domain Connect to and consume Azure services and third-party services

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 on 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 Gnd. Solution: Publish events to a custom topic. Create an event subscription for each customer. Does the solution meet the goal?
Answer options
A: Yes
B: No Correct answer
Correct Answer:
B. No
Explanation

The proposed solution does not meet the goal because it fails to meet the scalability requirement. An Azure Event Grid custom topic has a hard limit of 500 event subscriptions per topic. The requirement is to send events to "thousands of customers," and the solution proposes creating an event subscription for each customer. This would quickly exceed the service limit, making the solution unviable. While a custom topic provides a single endpoint and supports filtering and Microsoft Entra ID authentication, its subscription limit prevents it from scaling to the required number of customers.

Why Incorrect

A. Yes: This is incorrect. The solution is not viable due to the Azure Event Grid service limit of 500 subscriptions per custom topic, which contradicts the requirement to support thousands of customers.

References

1. Microsoft Learn | Azure Event Grid quotas and limits: This official documentation explicitly states the service limits for Event Grid resources.

Reference: Under the "Event Grid resource limits" table, the row "Event subscriptions per topic (custom, system, domain, and partner topics)" specifies a limit of "500". This directly supports the reason for the solution's failure.

2. Microsoft Learn | Event domains in Azure Event Grid: This document describes the appropriate architectural pattern for this multi-tenant scenario, highlighting why a single custom topic is insufficient.

Reference: In the "Event domains" section, it states, "Event domains are a management tool for large numbers of Event Grid topics related to the same application... Event domains make it easy for you to publish events to thousands of topics." This indicates that an Event Grid Domain, not a single custom topic, is the intended solution for this scale.

3. Microsoft Learn | Custom topics in Azure Event Grid: This document details the features of custom topics, confirming they meet some but not all requirements.

Reference: The "Publish to a custom topic" and "Secure your HTTP endpoint with Microsoft Entra ID" sections confirm that a custom topic provides a single endpoint and supports Microsoft Entra ID, but this does not override the fundamental scaling limitation.

Scroll to Top