MENU
You have an Azure Cosmos DB for NoSQL 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?
Suggested Answer: A
Get Premium DP-420 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
AU
Audra
11 months ago
A seems interesting, but I wouldn't trust it for conflicts.
AN
Anissa
11 months ago
B is the best choice, no doubt about it!
RU
Ruby
11 months ago
Wait, can you really use a timer trigger for this? Sounds off.
TO
Torie
12 months ago
I think C could work too, but not as efficient.
HE
Helene
12 months ago
Definitely B, that's the way to handle conflicts!
EV
Eva
1 year ago
I believe option B sounds correct since it mentions being triggered by the conflicts feed, which seems relevant to resolving conflicts directly.
FE
Felicitas
1 year ago
I'm a bit confused about the difference between the change feed and conflicts feed. I feel like I might mix them up in the exam.
KA
Karl
1 year ago
I think we practiced a similar question where we had to choose between triggers. If I recall, the conflicts feed is the right one to use here.
MA
Mariann
1 year ago
I remember something about using the conflicts feed, but I'm not sure if it should be a pull or push method.
DA
Daniel
1 year ago
Based on the information provided, I believe the correct answer is option B. Receiving items pushed from the conflicts feed and using an Azure Cosmos DB trigger seems like the most direct way to resolve the conflicts.
CO
Cordelia
1 year ago
I'm a bit confused on the difference between the change feed and the conflicts feed. I'll need to review the Azure Cosmos DB documentation to make sure I understand the right approach.
CO
Cordelia
1 year ago
Okay, let's see here. I think the key is to use the conflicts feed to resolve the conflicts, since the runtime exception is preventing the custom merge procedure from working.
RO
Royal
1 year ago
Hmm, this seems like a tricky one. I'll need to carefully consider the options and think through the implications of each approach.
YE
Yesenia
1 year ago
Ah, the old 'runtime exception preventing conflict resolution' trick. Classic Azure Cosmos DB. Definitely going with B, the Cosmos DB trigger function.
CO
Cory
1 year ago
Haha, I bet the person who wrote this question is a real conflict junkie. But I digress, B is the answer, no doubt about it.
AV
Avery
1 year ago
It's the most efficient way to resolve conflicts.
AL
Alpha
1 year ago
Yeah, using an Azure Cosmos DB trigger makes the most sense.
TI
Tien
1 year ago
I agree, B is definitely the answer.
RI
Ria
2 years ago
Wait, why would I want to pull items from the change feed? That's not gonna help me resolve the conflicts caused by the runtime exception. Gotta go with B, the Cosmos DB trigger.
FA
Fatima
1 year ago
Definitely, the Cosmos DB trigger is the best option for resolving conflicts in this scenario.
WA
Walker
1 year ago
Yeah, pulling items from the change feed won't solve the issue. B is the way to go.
ET
Ettie
1 year ago
I think B is the right choice too. The Cosmos DB trigger will help us resolve the conflicts.
DO
Dominque
2 years ago
Hmm, the key here is to use a function that receives items from the conflicts feed, not the change feed. I think option B is the way to go.
EL
Elfrieda
1 year ago
Yes, option B makes the most sense for resolving conflicts.
AD
Adria
2 years ago
I agree, option B is the best choice.
KE
Keneth
2 years ago
Hmm, that makes sense too. Let's review the question again to be sure.
AR
Arlette
2 years ago
I disagree, I believe the correct answer is A. It mentions pulling items from the change feed.
KE
Keneth
2 years ago
I think the answer is B, because it mentions receiving items pushed from the conflicts feed.