MENU
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?
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
35 comments · newest first
ST
Stacey
11 months ago
Totally agree, this meets the goal for sure!
DE
Derrick
11 months ago
Wait, can you really use custom procedures for conflict resolution?
CO
Cory
11 months ago
Not sure about the isTomstone parameter, though. Seems a bit off.
OD
Odelia
11 months ago
I think using a stored procedure for resolution is a solid choice.
AN
Annabelle
12 months ago
Yes, setting ConflictResolutionMode to Custom is the right approach!
SE
Sena
12 months ago
I’m leaning towards "No" because I recall that the isTombstone parameter is usually for marking deleted items, not resolving conflicts directly.
PR
Princess
1 year ago
This question feels similar to one we practiced where we had to choose between built-in and custom resolution. I think custom might be the way to go here.
DE
Desirae
1 year ago
I think setting ConflictResolutionMode to Custom is correct, but I’m a bit confused about how the isTombstone parameter actually works in this context.
WY
Wynell
1 year ago
I remember studying conflict resolution in Azure Cosmos DB, but I'm not entirely sure if using a custom stored procedure with isTombstone is the right approach.
PI
Pilar
1 year ago
Hmm, I'm a bit unsure about this one. The question mentions a heavily customized Salesforce implementation, so I'm not sure a greenfield approach (option A) would be the best fit.
ME
Merissa
1 year ago
Hmm, I'm not sure about this one. I know the system log can provide a lot of useful information, but I'm not sure if checking license usage is one of its main functions.
RI
Rima
1 year ago
Ah, I see the issue now. The password configuration is likely the key to getting the LDP session up. I'll carefully consider the options and select the right one.
AS
Ashlyn
1 year ago
Hmm, I'm not too familiar with the history of data protection laws. I'll have to think this through carefully and consider the options before making a guess.
DA
Dannie
1 year 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.
AN
Angella
1 year ago
User 3: I agree, we should use the correct terminology for Cosmos DB
KA
Kathryn
1 year ago
User 2: No
NE
Nettie
1 year ago
User 1: Yes
HE
Henriette
1 year 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.
MI
Mitsue
1 year 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?
DE
Delisa
1 year ago
User 3: I agree with Delisa, a custom conflict resolution logic might be better
FR
Francesco
1 year ago
User 2: B) No
LA
Lauran
1 year ago
User 1: A) Yes
CY
Cyndy
1 year 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.
MO
Mona
1 year ago
I agree with B) No, we need a resolution procedure that preserves conflicting data.
MO
Mona
1 year ago
I think B) No is the correct answer.
MO
Mona
1 year ago
B) No
MO
Mona
1 year ago
A) Yes
CH
Chi
1 year ago
I agree, B) No is the right choice. We want to ensure conflicts are sent to the conflict feed.
CH
Chi
1 year ago
I think B) No is the correct answer. We need a resolution procedure that preserves the conflicting data.
CH
Chi
1 year ago
B) No
CH
Chi
1 year ago
A) Yes
JO
Johnetta
1 year 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?
RO
Rosalia
2 years ago
I'm not sure. Maybe we should also consider other options before deciding if this solution meets the goal or not.
RE
Rebeca
2 years 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.
KE
Kerry
2 years 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.