Microsoft DP-420 Exam - Topic 14 Question 24 Discussion

Actual exam question for Microsoft's DP-420 exam

Question #: 24
Topic #: 14

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?

AYes

BNo

Show Suggested Answer

Suggested Answer: A

by Alaine at Aug 04, 2023, 05:25 PM

Limited Time Offer

25%

Off

Get Premium DP-420 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Stacey

6 months ago

Totally agree, this meets the goal for sure!

upvoted 0 times

...

Derrick

7 months ago

Wait, can you really use custom procedures for conflict resolution?

upvoted 0 times

...

Cory

7 months ago

Not sure about the isTomstone parameter, though. Seems a bit off.

upvoted 0 times

...

Odelia

7 months ago

I think using a stored procedure for resolution is a solid choice.

upvoted 0 times

...

Annabelle

7 months ago

Yes, setting ConflictResolutionMode to Custom is the right approach!

upvoted 0 times

...

Sena

8 months ago

I’m leaning towards "No" because I recall that the isTombstone parameter is usually for marking deleted items, not resolving conflicts directly.

upvoted 0 times

...

Princess

8 months 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.

upvoted 0 times

...

Desirae

8 months 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.

upvoted 0 times

...

Wynell

8 months 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.

upvoted 0 times

...

Pilar

8 months 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.

upvoted 0 times

...

Merissa

8 months 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.

upvoted 0 times

...

Rima

8 months 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.

upvoted 0 times

...

Ashlyn

8 months 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.

upvoted 0 times

...

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.

upvoted 0 times

Angella

1 year ago

User 3: I agree, we should use the correct terminology for Cosmos DB

upvoted 0 times

...

Kathryn

1 year ago

User 2: No

upvoted 0 times

...

Nettie

1 year ago

User 1: Yes

upvoted 0 times

...

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.

upvoted 0 times

...

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?

upvoted 0 times

Delisa

12 months ago

User 3: I agree with Delisa, a custom conflict resolution logic might be better

upvoted 0 times

...

Francesco

1 year ago

User 2: B) No

upvoted 0 times

...

Lauran

1 year ago

User 1: A) Yes

upvoted 0 times

...

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.

upvoted 0 times

Mona

12 months ago

I agree with B) No, we need a resolution procedure that preserves conflicting data.

upvoted 0 times

...

Mona

12 months ago

I think B) No is the correct answer.

upvoted 0 times

...

Mona

12 months ago

B) No

upvoted 0 times

...

Mona

1 year ago

A) Yes

upvoted 0 times

...

Chi

1 year 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 year ago

I think B) No is the correct answer. We need a resolution procedure that preserves the conflicting data.

upvoted 0 times

...

Chi

1 year ago

B) No

upvoted 0 times

...

Chi

1 year ago

A) Yes

upvoted 0 times

...

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?

upvoted 0 times

...

Rosalia

1 year 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

1 year 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

1 year 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

...