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 AZ-204 Exam - Topic 9 Question 81 Discussion

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

You are developing an Azure Durable Function to manage an online ordering process.

The process must call an external API to gather product discount information.

You need to implement Azure Durable Function.

Which Azure Durable Function types should you use? Each correct answer presents part of the solution

NOTE: Each correct selection is worth ore point

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Shawnta
4 months ago
I’m surprised the Client function isn’t mentioned more often in these discussions.
upvoted 0 times
...
Stephanie
4 months ago
Totally agree, Orchestrator and Activity are a must!
upvoted 0 times
...
Kaitlyn
4 months ago
Wait, why would you need an Entity function here? Seems unnecessary.
upvoted 0 times
...
Kris
4 months ago
I think Activity functions are also essential for calling the API.
upvoted 0 times
...
Sylvie
5 months ago
Definitely need the Orchestrator for managing the workflow.
upvoted 0 times
...
Mike
5 months ago
The Client function seems like it might be important for starting the orchestration, but I’m not entirely sure if it’s required in this scenario.
upvoted 0 times
...
Mammie
5 months ago
I’m a bit confused about the Entity function. I don’t recall it being necessary for this kind of process, but I could be wrong.
upvoted 0 times
...
Sonia
5 months ago
I remember practicing a similar question where we used both Orchestrator and Activity functions. I think that’s the right approach here too.
upvoted 0 times
...
Ellsworth
5 months ago
I think we definitely need the Orchestrator function to manage the workflow, but I'm not sure if we also need the Activity function for the API call.
upvoted 0 times
...
Lavonne
5 months ago
This looks straightforward enough. I'll use the Orchestrator to orchestrate the overall process, the Activity to make the API call, and the Entity to manage the order state. Should be a piece of cake!
upvoted 0 times
...
Eliz
5 months ago
I'm not too familiar with Durable Functions, but I think the key here is to use the Orchestrator to manage the high-level flow and the Activity to encapsulate the API call. I'll need to do some research on best practices for structuring Durable Functions apps.
upvoted 0 times
...
Irma
5 months ago
Okay, I've got this. The Orchestrator function will coordinate the overall workflow, the Activity function will handle the external API call, and the Entity function can be used to manage the state of the order throughout the process. Time to get coding!
upvoted 0 times
...
Isabelle
5 months ago
I'm a bit confused on the different Durable Functions types and how they work together. I'll need to review the documentation to make sure I understand the differences between Orchestrator, Entity, and Activity.
upvoted 0 times
...
Joanna
5 months ago
Hmm, this looks like a classic Durable Functions scenario. I think I'll need to use the Orchestrator and Activity functions to coordinate the external API call and manage the overall ordering process.
upvoted 0 times
...
Sylvie
6 months ago
I'm leaning towards the "Custom Multiple row formula" option. That sounds like it could help us identify renewals by comparing the Opportunity history for each Account.
upvoted 0 times
...
Juan
6 months ago
I'm pretty sure the "Add Log Fields" activity is used to customize the standard log message by adding new fields to it. That sounds like option B to me.
upvoted 0 times
...
Garry
6 months ago
Hmm, this looks like a question about cryptography. I'll need to think carefully about the LAN manager hash and what the second half might be.
upvoted 0 times
...

Save Cancel