Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam AZ-204 Topic 17 Question 86 Discussion

Actual exam question for Microsoft's AZ-204 exam
Question #: 86
Topic #: 17
[All AZ-204 Questions]

You develop Azure Durable Functions to manage vehicle loans.

The loan process includes multiple actions that must be run in a specified order. One of the actions includes a customer credit check process, which may require multiple days to process.

You need to implement Azure Durable Functions for the loan process.

Which Azure Durable Functions type should you use?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Alberto
2 days ago
Yup, Orchestrator is the way to go. The credit check process is a good example of why you'd want to use Durable Functions - it allows you to handle those long-running tasks without the client having to wait around.
upvoted 0 times
...
Wilda
3 days ago
Definitely Orchestrator. The client function is more for initiating the workflow, and the activity functions are the individual tasks that get executed. The entity function is used for managing state, which doesn't really fit this use case.
upvoted 0 times
...
Helaine
4 days ago
I agree, the Orchestrator type seems like the way to go here. It'll allow us to define the overall workflow and handle the coordination of the different steps, including the long-running credit check process.
upvoted 0 times
...
Georgeanna
5 days ago
This question seems pretty straightforward. Based on the scenario, we're dealing with a multi-step process that needs to run in a specific order, and some of those steps may take a while to complete. That sounds like a perfect use case for the Orchestrator function type in Durable Functions.
upvoted 0 times
...

Save Cancel