Free Microsoft Azure AZ-900 Actual Exam Questions - Question 7 Discussion

I think the event routing description fits best with Event Grid, since it’s designed specifically to route events between sources and handlers at scale. Logic Apps do handle workflows and automation, but they’re more about process orchestration rather than event distribution itself. Azure Functions are great for running code on triggers, but they don’t manage event routing like Event Grid does. So for the service that primarily routes events, Event Grid seems like the right match here.

I’d say for the service that focuses on running code in response to events, Azure Functions fits best. It’s more about lightweight compute triggered by events, unlike Logic Apps which handle bigger orchestration and workflows. Event Grid is really just about routing those events around, not processing them directly. So if the description mentions event-driven code execution, that’s Functions. For storage of unstructured data, Blob Storage is your go-to. It’s pretty straightforward, just store your files and blobs without worrying about workflows or event handling.

I’d exclude Azure Functions for the event routing part because it’s more code-focused, not a full event system like Event Grid. Logic Apps handle integration flows better than Functions for orchestrating tasks.

I’d say Azure Event Grid fits best with event routing, different from Logic Apps or Functions. It’s designed for handling events at scale, so it’s not really about storage or workflows directly.

I’d rule out Azure Functions for anything that involves visual workflow or orchestration—that’s more Logic Apps territory. Blob Storage is definitely for unstructured data, so keep it separate from compute or automation services.

I think Azure Blob Storage fits the description about storing unstructured data, so it should match with that. It’s more about storage than running workflows or code, so it’s different from Logic Apps or Functions.

For the description about automating tasks across services, Logic Apps (A) is definitely the way to go since it’s built for that. Functions (B) are more about running small bits of code when an event happens, so that fits the quick execution part better.

Logic Apps are designed for visual workflows, not small, stateless code runs like Functions.

For the description about quick, small code executions triggered by events, Azure Functions (B) fits best. Logic Apps (A) is more about orchestrating complex workflows across various services, so that works better for integration tasks.

I think another way to look at it is by focusing on what each service primarily targets. For example, Azure Functions is mainly for running small pieces of code or functions in response to triggers, while Logic Apps are more about orchestrating workflows that connect different services without writing much code. So if the description talks about integrating multiple systems or automating business processes, Logic Apps fits better. If it’s about event-driven compute or serverless code snippets, Azure Functions is likely the match. This can help clear up the confusion when both seem similar at f

This drag-and-drop is confusing, got stuck between Azure Functions and Logic Apps.