Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam DP-420 Topic 14 Question 24 Discussion

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

You have a database in an Azure Cosmos DB for NoSQL account that is configured for multi-region writes.

You need to use the Azure Cosmos DB SDK to implement the conflict resolution policy for a container. The solution must ensure that any conflict sent to the conflict feed.

Solution: You set ConfilictResolutionMode to Custom. You Set ResolutionProcedures to a custom stored procedure. You configure the custom stored procedure to use the isTomstone parameter to resolve conflict.

Does this meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Dannie
1 months ago
Haha, 'isTomstone'? Is that like a stone that's been turned into a tomb or something? I think we need to stick to the proper Cosmos DB lingo here, folks.
upvoted 0 times
Angella
14 days ago
User 3: I agree, we should use the correct terminology for Cosmos DB
upvoted 0 times
...
Kathryn
19 days ago
User 2: No
upvoted 0 times
...
Nettie
21 days ago
User 1: Yes
upvoted 0 times
...
...
Henriette
1 months ago
Wait, is 'isTomstone' even a real parameter? That sounds like a typo to me. I'd double-check the documentation to make sure we're using the correct terminology.
upvoted 0 times
...
Mitsue
1 months ago
Hmm, I'm not sure the isTombstone parameter is the best way to go here. Wouldn't it be better to use a custom conflict resolution logic that can intelligently merge the conflicting data and send it to the conflict feed?
upvoted 0 times
Delisa
5 days ago
User 3: I agree with Delisa, a custom conflict resolution logic might be better
upvoted 0 times
...
Francesco
20 days ago
User 2: B) No
upvoted 0 times
...
Lauran
25 days ago
User 1: A) Yes
upvoted 0 times
...
...
Cyndy
2 months ago
I agree with Johnetta. The goal is to ensure that any conflict is sent to the conflict feed, so we need a resolution procedure that preserves the conflicting data, not one that simply deletes it.
upvoted 0 times
Mona
5 days ago
I agree with B) No, we need a resolution procedure that preserves conflicting data.
upvoted 0 times
...
Mona
6 days ago
I think B) No is the correct answer.
upvoted 0 times
...
Mona
11 days ago
B) No
upvoted 0 times
...
Mona
1 months ago
A) Yes
upvoted 0 times
...
Chi
1 months ago
I agree, B) No is the right choice. We want to ensure conflicts are sent to the conflict feed.
upvoted 0 times
...
Chi
1 months ago
I think B) No is the correct answer. We need a resolution procedure that preserves the conflicting data.
upvoted 0 times
...
Chi
1 months ago
B) No
upvoted 0 times
...
Chi
2 months ago
A) Yes
upvoted 0 times
...
...
Johnetta
2 months ago
The solution seems to be on the right track, but I'm not sure about using the isTombstone parameter to resolve conflicts. Doesn't that just delete the conflicting data instead of preserving it in the conflict feed?
upvoted 0 times
...
Rosalia
2 months ago
I'm not sure. Maybe we should also consider other options before deciding if this solution meets the goal or not.
upvoted 0 times
...
Rebeca
2 months ago
I agree with Kerry. Using a custom stored procedure with the isTomstone parameter sounds like a good way to handle conflicts in a multi-region writes scenario.
upvoted 0 times
...
Kerry
3 months ago
Yes, that should meet the goal because setting ConflictResolutionMode to Custom and using a custom stored procedure with isTomstone parameter should help resolve conflicts.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77