Microsoft AZ-204 Exam - Topic 2 Question 90 Discussion

Actual exam question for Microsoft's AZ-204 exam

Question #: 90
Topic #: 2

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 Grid.

Solution: Publish events to a partner topic. Create an event subscription for each customer.

Does the solution meet the goal?

AYes

BNo

Show Suggested Answer

Suggested Answer: B

by Yolando at Apr 09, 2024, 03:34 AM

Limited Time Offer

25%

Off

Get Premium AZ-204 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Nana

3 months ago

Definitely a good approach for scalability!

upvoted 0 times

...

Chanel

4 months ago

Wait, can you really filter by event type with that setup?

upvoted 0 times

...

Stephaine

4 months ago

Yes, this meets the requirements perfectly!

upvoted 0 times

...

Stephaine

4 months ago

I think it might get complicated with so many subscriptions.

upvoted 0 times

...

Ashlyn

4 months ago

Sounds like a solid plan!

upvoted 0 times

...

Cary

4 months ago

I feel like this could meet the goals, but I wonder if there’s a better way to manage the subscriptions without overwhelming the system.

upvoted 0 times

...

Sanjuana

5 months ago

I’m a bit confused about the authentication part. Does using Microsoft Entra ID automatically cover all customers if we have a single endpoint?

upvoted 0 times

...

Arthur

5 months ago

I remember a practice question where we had to filter events by type, and I feel like this setup might not handle that well.

upvoted 0 times

...

Art

5 months ago

I think this solution might work because publishing to a partner topic could help with scalability, but I'm not sure if creating an event subscription for each customer is efficient.

upvoted 0 times

...

Jennifer

5 months ago

This seems straightforward enough. Publish to a partner topic and create individual subscriptions - that should do the trick. I'll double-check the details, but I think I've got a good handle on this one.

upvoted 0 times

...

Gladys

5 months ago

I'm a bit confused by the requirement to publish to a single endpoint. Wouldn't that limit the flexibility of the solution? I'll need to think through how to best address that while still meeting the other requirements.

upvoted 0 times

...

Aleisha

5 months ago

Okay, I think I have a strategy. I'll focus on using the filtering capabilities of Event Grid to handle the different event types, and then look into how to efficiently manage the subscriptions for all the customers.

upvoted 0 times

...

Meaghan

5 months ago

This looks like a tricky one. I'll need to carefully read through the requirements and think about how to best leverage Azure Event Grid to meet them.

upvoted 0 times

...

Haley

5 months ago

Hmm, publishing events to a partner topic and creating individual event subscriptions for each customer seems like it could get complicated with thousands of customers and hundreds of event types. I'll need to consider a more scalable approach.

upvoted 0 times

...

Fairy

5 months ago

Hmm, I'm leaning towards option A, but I want to make sure I'm not missing anything. I'll quickly skim through the relevant sections in the textbook to confirm.

upvoted 0 times

...

Jannette

5 months ago

This looks straightforward - I'd go with option C, creating a group and assigning Bob and Sally to it, then provisioning the Consolidate role to the group.

upvoted 0 times

...

Belen

5 months ago

This looks like a pretty straightforward question about NETCONF and YANG. I think the key is to find the command that will display the login times for each user session.

upvoted 0 times

...

India

5 months ago

This looks like a straightforward matching question. I'll read through the options carefully and try to match the descriptions to the review types.

upvoted 0 times

...

Major

5 months ago

Hmm, I'm a bit unsure about this one. There are a few options that seem plausible, but I'm not sure which one is the primary benefit they're looking for. I'll need to carefully read through the case study information to make sure I understand the context.

upvoted 0 times

...

Alease

2 years ago

No, I don't think it meets the goal. It would be more efficient to publish events to a single endpoint rather than creating individual event subscriptions.

upvoted 0 times

...

Melita

2 years ago

I think creating event subscriptions for each customer might work initially, but it could become cumbersome to manage in the long run.

upvoted 0 times

...

Pearlie

2 years ago

But wouldn't creating an event subscription for each customer become unmanageable as the number of customers grow?

upvoted 0 times

...

Reid

2 years ago

Yes, it meets the goal because we need to send events to thousands of customers with different event types.

upvoted 0 times

...

Nan

2 years ago

In my opinion, the solution does not meet the goal because it would be too complex to manage all those event subscriptions.

upvoted 0 times

...

Demetra

2 years ago

Perhaps a better solution would be to use a single endpoint for all customers instead of creating individual event subscriptions.

upvoted 0 times

...

Colton

2 years ago

I agree with Managing individual event subscriptions for each customer doesn't seem efficient.

upvoted 0 times

...

Melissa

2 years ago

That's a valid point. It could be challenging to scale with so many customers.

upvoted 0 times

...

Marti

2 years ago

But wouldn't creating an event subscription for each customer be cumbersome and difficult to manage?

upvoted 0 times

...

Melissa

2 years ago

I think the solution meets the goal because it allows for sending events to thousands of customers with various event types.

upvoted 0 times

...

Claudia

2 years ago

Exactly, plus having to manage authentication and authorization for all those individual subscriptions sounds like a headache. I'd vote for a 'No' on this one - there has to be a more efficient way to meet all these requirements.

upvoted 0 times

...

Dominque

2 years ago

I'm a bit skeptical about this solution. Wouldn't it be more efficient to use a single Event Grid topic and leverage the built-in filtering capabilities? That way, we could avoid the overhead of managing multiple event subscriptions and still meet all the requirements.

upvoted 0 times

Ryann

2 years ago

User 2

upvoted 0 times

...

Lonna

2 years ago

User 1

upvoted 0 times

...

Carlee

2 years ago

Yeah, and the requirement to use a single endpoint for publishing events seems at odds with the individual event subscriptions. Wouldn't a more scalable solution be to use a topic with multiple subscriptions to handle the filtering and distribution?

upvoted 0 times

...

Josephine

2 years ago

Hmm, I'm not convinced that this solution is the best approach. Wouldn't it be simpler to use a single Event Grid topic and handle the filtering and authentication on our side? That way, we could avoid the complexity of managing multiple event subscriptions.

upvoted 0 times

...

Destiny

2 years ago

I agree, the requirement to filter events by type before processing makes me think a partner topic might not be the best approach. Wouldn't it be better to have a more centralized way to manage all those event types and customers?

upvoted 0 times

...

Oliva

2 years ago

Hmm, I'm not sure if this solution meets all the requirements. Sending events to thousands of customers with hundreds of event types seems like it might get a bit messy with individual event subscriptions for each customer.

upvoted 0 times

...

Kathryn

2 years ago

I'm not sure about this solution. Creating an event subscription for each customer seems like it could get really unwieldy, especially with thousands of customers and hundreds of event types. I think we should explore a more scalable solution that uses the built-in features of Event Grid.

upvoted 0 times

...

Tijuana

2 years ago

The solution seems overly complex to me. Wouldn't it be better to use a single Event Grid topic and leverage the built-in authentication and authorization features of Microsoft Entra ID? That way, we could keep things simple and still meet all the requirements.

upvoted 0 times

...

Jody

2 years ago

I think the solution provided might work, but it seems a bit complicated. Wouldn't it be better to use a single Event Grid topic and use the built-in filtering capabilities to handle the event types? That way, we could avoid the overhead of creating multiple event subscriptions.

upvoted 0 times

Emeline

2 years ago

Good point. We'll need to consider scalability as well.

upvoted 0 times

...

Janessa

2 years ago

It could become more difficult to scale if we have a large number of customers.

upvoted 0 times

...

Louisa

2 years ago

Do you see any potential drawbacks to using a single Event Grid topic?

upvoted 0 times

...

Gerald

2 years ago

That makes sense. It would be more efficient that way.

upvoted 0 times

...

Brent

2 years ago

Using a single topic simplifies the setup and reduces management overhead.

upvoted 0 times

...

In

2 years ago

Why do you think it would be better to use a single Event Grid topic?

upvoted 0 times

...

Minna

2 years ago

Yes

upvoted 0 times

...

Maxima

2 years ago

I'm not sure about this question. The requirements seem a bit unclear to me. Publishing events to a partner topic and creating an event subscription for each customer seems like a lot of overhead. Wouldn't it be simpler to just use a single Event Grid topic and handle the filtering and authentication on our end?

upvoted 0 times

...