Microsoft Azure Architect Design (AZ-304) Practice Test

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the Microsoft Azure Architect Design (AZ-304) Exam with comprehensive quiz questions designed to enhance your understanding and confidence. Master essential Azure concepts and strategies to excel on your test day!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


What notification solution will minimize compute costs while providing email notifications from IoT data in Azure Cosmos DB?

  1. Deploy an Azure logic app with Azure Cosmos DB connector and SendGrid action.

  2. Deploy a function app with Consumption plan and SendGrid binding.

  3. Deploy a logic app with SendGrid connector configured for Azure Cosmos DB action.

  4. Deploy a function app configured with Consumption plan and Azure Event Hubs binding.

The correct answer is: Deploy a function app with Consumption plan and SendGrid binding.

The choice of deploying a function app with a Consumption plan and SendGrid binding is ideal for minimizing compute costs while effectively providing email notifications from IoT data in Azure Cosmos DB. A function app operates on a serverless architecture, where you only pay for the processing time consumed when the function is executed. The Consumption plan scales automatically and charges based on the number of executions and runtime duration, which is efficient for scenarios with variable workloads, such as processing IoT data. By integrating with SendGrid, the function app can send out email notifications seamlessly when certain triggers from the data in Azure Cosmos DB occur. This combination allows for a cost-effective solution because it leverages the serverless capabilities, ensuring that costs are kept low during periods of inactivity, while still providing the necessary functionality to handle incoming data and send notifications. Other options involve logic apps or configurations that may incur higher costs due to always-on resources or payment models that do not scale as efficiently as the Consumption plan provides in this scenario. Function apps offer a more scalable and economical way to handle the dynamic nature of IoT data notifications.