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 3 Question 68 Discussion

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

You are troubleshooting the current issues caused by the application updates.

Which action can address the application updates issue without affecting the functionality of the application?

Show Suggested Answer Hide Answer
Suggested Answer: C

Bounded staleness is frequently chosen by globally distributed applications that expect low write latencies but require total global order guarantee. Bounded staleness is great for applications featuring group collaboration and sharing, stock ticker, publish-subscribe/queueing etc.

Scenario: Application updates in con-product frequently cause HTTP status code 429 'Too many requests'. You discover that the 429 status code relates to excessive request unit (RU) consumption during the updates.


https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

Contribute your Thoughts:

0/2000 characters
Roslyn
7 days ago
I think option C is the best choice. It balances performance and consistency.
upvoted 0 times
...
Shasta
13 days ago
Totally agree with C, it balances performance and consistency!
upvoted 0 times
...
Arlene
18 days ago
Wait, are we sure D won't mess things up?
upvoted 0 times
...
Murray
23 days ago
I think A could actually help with performance too.
upvoted 0 times
...
Elmer
28 days ago
Option C seems like a safe bet for stability.
upvoted 0 times
...
Altha
1 month ago
C) Set the default consistency level of account1 to bounded staleness. This is the most appropriate action to address the application updates issue without affecting the functionality.
upvoted 0 times
...
Dierdre
1 month ago
I'm pretty sure the answer is C, but I'm also hungry. Anyone else want to grab a sandwich?
upvoted 0 times
...
Micheline
1 month ago
The correct answer is C. Bounded staleness is the way to go!
upvoted 0 times
...
Nilsa
2 months ago
D) Add a custom indexing policy to the con-product container.
upvoted 0 times
...
Remedios
2 months ago
I'm a bit confused about the time to live setting; I thought it was more about data expiration than functionality.
upvoted 0 times
...
Mose
2 months ago
I'm leaning towards option D. Adding a custom indexing policy to the container might be a good way to handle the updates while preserving the app's functionality.
upvoted 0 times
...
Pamella
2 months ago
Option A seems promising - enabling time to live for the container could help manage the updates without impacting the app. I'll have to look into that further.
upvoted 0 times
...
Domitila
2 months ago
If I remember correctly, setting the default consistency level to bounded staleness might help with performance issues without breaking anything.
upvoted 0 times
...
Melvin
2 months ago
I remember discussing how consistency levels can impact application performance, but I'm not sure which one would be best here.
upvoted 0 times
...
Laurel
3 months ago
C) Set the default consistency level of account1 to bounded staleness.
upvoted 0 times
...
Deja
3 months ago
I think we practiced a question about indexing policies, but I can't recall if they directly affect application functionality.
upvoted 0 times
...
Moon
3 months ago
Strong consistency? Sounds too strict for most apps.
upvoted 0 times
...
Raina
3 months ago
Hmm, I'm a bit confused on the difference between the consistency level options. I'll need to review those details before deciding.
upvoted 0 times
...
Mary
4 months ago
I think option C might be the way to go here. Setting the consistency level to bounded staleness could help address the application updates without affecting the functionality.
upvoted 0 times
...

Save Cancel