New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft DP-420 Exam - Topic 2 Question 61 Discussion

Actual exam question for Microsoft's DP-420 exam
Question #: 61
Topic #: 2
[All DP-420 Questions]

You have an Azure Cosmos DB Core (SQL) API account that uses a custom conflict resolution policy. The account has a registered merge procedure that throws a runtime exception.

The runtime exception prevents conflicts from being resolved.

You need to use an Azure function to resolve the conflicts.

What should you use?

Show Suggested Answer Hide Answer
Suggested Answer: D

The Azure Cosmos DB Trigger uses the Azure Cosmos DB Change Feed to listen for inserts and updates across partitions. The change feed publishes inserts and updates, not deletions.


Contribute your Thoughts:

0/2000 characters
Beckie
3 months ago
I disagree, pulling from the conflicts feed seems more reliable.
upvoted 0 times
...
Shawana
3 months ago
I’m surprised a merge procedure can throw exceptions like that!
upvoted 0 times
...
Aliza
3 months ago
Wait, isn't option B better for real-time updates?
upvoted 0 times
...
Ollie
3 months ago
Definitely not A, timer triggers are too slow for conflicts.
upvoted 0 times
...
Barbra
3 months ago
I think option D is the way to go!
upvoted 0 times
...
Filiberto
4 months ago
I'm leaning towards option B, but I feel like I need to double-check if the change feed is the right choice for handling conflicts.
upvoted 0 times
...
Erasmo
4 months ago
I practiced a similar question about triggers, but I can't recall if a timer trigger is appropriate for this scenario.
upvoted 0 times
...
Nicolette
4 months ago
I think it might be option D since it mentions the conflicts feed, which is directly related to resolving conflicts.
upvoted 0 times
...
Leota
4 months ago
I remember studying the differences between the conflicts feed and the change feed, but I'm not sure which one to use here.
upvoted 0 times
...
Rolande
4 months ago
I feel pretty confident that option D is the right answer. Receiving items pushed from the conflicts feed and using an Azure Cosmos DB trigger seems like the most appropriate solution given the problem statement.
upvoted 0 times
...
Tandra
5 months ago
I'm a bit confused on the difference between the change feed and the conflicts feed. I'll need to review those concepts before deciding on the best approach.
upvoted 0 times
...
Angella
5 months ago
Okay, I'm leaning towards option B. Receiving items pushed from the change feed and using an Azure Cosmos DB trigger seems like the most direct way to address the conflict resolution issue.
upvoted 0 times
...
Pura
5 months ago
Hmm, the key here is that the runtime exception is preventing the conflicts from being resolved. I think the Azure function will need to handle that somehow.
upvoted 0 times
...
Paris
5 months ago
This seems like a tricky one. I'll need to carefully read through the details and think through the different options.
upvoted 0 times
...
Carma
10 months ago
I don't know about you, but I'm feeling a bit 'conflicted' about this question. Option B is the way to go, though.
upvoted 0 times
Glenn
9 months ago
User 3: Yeah, that seems like the most efficient way to resolve conflicts.
upvoted 0 times
...
Jolene
9 months ago
User 2: I agree, using a function triggered by an Azure Cosmos DB trigger makes sense.
upvoted 0 times
...
Lenna
9 months ago
User 1: I think option B is the best choice.
upvoted 0 times
...
...
Aleisha
10 months ago
This is a classic case of 'the solution is right in front of you.' Option B is the winner, my friends.
upvoted 0 times
Lyla
8 months ago
Let's go with option B then, it seems like the best choice.
upvoted 0 times
...
Joanna
8 months ago
Exactly, it's the most suitable option for resolving conflicts in this scenario.
upvoted 0 times
...
Denae
8 months ago
That makes sense, it will receive items pushed from the change feed.
upvoted 0 times
...
Esteban
9 months ago
I think we should use option B, a function triggered by an Azure Cosmos DB trigger.
upvoted 0 times
...
...
Tori
10 months ago
Haha, I bet the developer who wrote that runtime exception is regretting it now. Option B is the answer, no doubt about it.
upvoted 0 times
Truman
9 months ago
Absolutely, Option B with the Azure Cosmos DB trigger is the perfect solution for resolving those conflicts.
upvoted 0 times
...
Detra
9 months ago
Yeah, Option B is the best choice here. It's the most efficient way to resolve those conflicts.
upvoted 0 times
...
Silva
9 months ago
I agree, that developer must be kicking themselves. Option B is definitely the way to go.
upvoted 0 times
...
...
Elliot
10 months ago
I think option D is the way to go. Receiving the items directly from the conflicts feed and resolving them in the function sounds like the best solution.
upvoted 0 times
...
Evangelina
10 months ago
Option B seems the most straightforward approach. Using the Azure Cosmos DB trigger to handle the conflicts feed is the logical choice here.
upvoted 0 times
Reta
9 months ago
Yes, option B seems like the most efficient way to resolve conflicts in the Azure Cosmos DB Core (SQL) API account.
upvoted 0 times
...
Lynsey
9 months ago
I think using the Azure Cosmos DB trigger to receive items pushed from the change feed is the way to go.
upvoted 0 times
...
Simona
10 months ago
I agree, option B is the best choice for handling conflicts in this scenario.
upvoted 0 times
...
...
Kenia
11 months ago
I'm not sure, but I think A could also work since it pulls items from the conflicts feed.
upvoted 0 times
...
Winfred
11 months ago
I agree with Apolonia, because the function needs to receive items pushed from the change feed.
upvoted 0 times
...
Apolonia
11 months ago
I think the answer is B.
upvoted 0 times
...

Save Cancel