AZ-204 Develop Azure compute solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create Cosmos DB, then create Function App, then add trigger binding, then write code, then test.

  Why this is correct

  This sequence is correct because establishing the Azure Cosmos DB account first provides the necessary resource for the Azure Function App to reference. The Function App is then created, followed by configuring the Cosmos DB trigger binding, which defines how the function will react to changes. Writing the function code comes next, implementing the logic based on the trigger's input, and finally, testing validates the entire integration.

• ✗

  Create Function App, then create Cosmos DB, then add trigger binding, then write code, then test.

  Why it's wrong here

  This order is incorrect because the Azure Cosmos DB trigger binding, a core component of the Azure Function, requires an existing Cosmos DB account and its connection string to be properly configured. Creating the Function App before Cosmos DB means the necessary database and collection details for the trigger would not yet exist, preventing the binding from being correctly established.

• ✗

  Create Cosmos DB, then create Function App, then write code, then add trigger binding, then test.

  Why it's wrong here

  This order is incorrect because the trigger binding must be defined before writing the function code. The Cosmos DB trigger binding dictates the function's signature, including the specific input parameters (e.g., `IReadOnlyList<Document> documents`) and attributes like `[CosmosDBTrigger(...)]`. Writing code without this established signature would lead to compilation errors or a function that cannot correctly receive data from the change feed.

• ✗

  Create Cosmos DB, then create Function App, then add trigger binding, then test, then write code.

  Why it's wrong here

  This order is incorrect because testing an Azure Function's integration with Cosmos DB requires the function's code to be fully written, deployed, and operational. Attempting to test before the code is implemented means there is no logic to execute or observe, making any form of functional validation impossible. Code must always precede testing in the development lifecycle.

Go deeper

Related to this question