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 2 Question 62 Discussion

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

You configure multi-region writes for account1.

You need to ensure that App1 supports the new configuration for account1. The solution must meet the business requirements and the product catalog requirements.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

App1 queries the con-product and con-productVendor containers.

Note: Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.

Scenario:

Develop an app named App1 that will run from all locations and query the data in account1.

Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.

Whenever there are multiple solutions for a requirement, select the solution that provides the best performance, as long as there are no additional costs associated.


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

Contribute your Thoughts:

0/2000 characters
Alison
3 months ago
Wait, can we really use bounded staleness for this?
upvoted 0 times
...
Providencia
3 months ago
I think C makes more sense for App1's connection.
upvoted 0 times
...
Carey
3 months ago
D sounds like a good idea, but is it necessary?
upvoted 0 times
...
Keva
3 months ago
Totally agree with A, it fits the requirements perfectly!
upvoted 0 times
...
Jacki
4 months ago
Option A is the best choice for consistency.
upvoted 0 times
...
Rikki
4 months ago
Increasing the RU/s for the containers sounds familiar, but I feel like that might be more about scaling rather than directly addressing the multi-region writes.
upvoted 0 times
...
Brigette
4 months ago
Creating a private endpoint connection seems like it could enhance security, but I wonder if it directly supports the multi-region write configuration.
upvoted 0 times
...
Yoko
4 months ago
I remember a practice question that mentioned modifying the connection policy could improve performance, but I can't recall the specifics.
upvoted 0 times
...
Solange
4 months ago
I think setting the default consistency level to bounded staleness might help with multi-region writes, but I'm not entirely sure if that's the best option for App1.
upvoted 0 times
...
Teri
5 months ago
I've got a good feeling about this one. Setting the default consistency level to bounded staleness seems like the most straightforward approach to meet the business and product catalog requirements. I'd start there and see if that solves the issue.
upvoted 0 times
...
Ranee
5 months ago
Okay, let's think this through step-by-step. First, we need to ensure the default consistency level is appropriate for the new configuration. Then, we should consider the connection policy to optimize performance and reliability. The private endpoint connection could be a good option to explore.
upvoted 0 times
...
Georgiann
5 months ago
Hmm, this seems like a tricky one. I'm a bit unsure about the details of the multi-region write configuration and how that impacts the product catalog requirements. I'll need to review the information carefully.
upvoted 0 times
...
Trina
5 months ago
I think the key here is to ensure that App1 supports the new multi-region write configuration for account1. Based on the requirements, I'd start by looking at the consistency level and connection policy options.
upvoted 0 times
...
Craig
9 months ago
Personally, I'd go with option A. Bounded staleness is the perfect consistency level for this scenario. It's like a good old-fashioned 'close enough' approach, you know?
upvoted 0 times
Brynn
7 months ago
User4: Let's go with option A then.
upvoted 0 times
...
Yun
7 months ago
User3: I agree, it's like a 'close enough' approach.
upvoted 0 times
...
Glenna
8 months ago
Yeah, I agree. It's a good balance between consistency and performance.
upvoted 0 times
...
Beckie
8 months ago
I think option A is the way to go. Bounded staleness is a good fit for this.
upvoted 0 times
...
Curtis
8 months ago
User2: Yeah, bounded staleness sounds like a good fit for this.
upvoted 0 times
...
Alonzo
9 months ago
User1: I think option A is the way to go.
upvoted 0 times
...
...
Afton
9 months ago
I think increasing the number of request units per second allocated to the containers is the best option for scalability.
upvoted 0 times
...
Twana
9 months ago
But modifying the connection policy of App1 could also work, don't you think?
upvoted 0 times
...
Juan
9 months ago
Haha, I bet the exam writers are having a field day with this one. They're probably sitting back, wondering which option will make the candidates scratch their heads the most.
upvoted 0 times
Arlette
9 months ago
B) Create a private endpoint connection.
upvoted 0 times
...
Cherry
9 months ago
A) Set the default consistency level of account1 to bounded staleness.
upvoted 0 times
...
...
Altha
9 months ago
I disagree, I believe creating a private endpoint connection would be a better solution.
upvoted 0 times
...
Rory
10 months ago
Hold on, what about option D? Increasing the RU/s for the containers could help meet the product catalog requirements. It's worth considering.
upvoted 0 times
Gail
9 months ago
User3: Let's go with option D then, it seems like the best choice for App1.
upvoted 0 times
...
Keneth
9 months ago
User2: I agree, increasing the RU/s allocated to the containers might be the way to go.
upvoted 0 times
...
Caren
9 months ago
User1: Option D could be a good solution to meet the product catalog requirements.
upvoted 0 times
...
...
Twana
10 months ago
I think we should set the default consistency level of account1 to bounded staleness.
upvoted 0 times
...
Louvenia
10 months ago
Hmm, I'm not sure. Option B, creating a private endpoint connection, might be a good idea to ensure secure communication between App1 and account1.
upvoted 0 times
Magda
9 months ago
User3: Creating a private endpoint connection could also ensure secure communication between App1 and account1.
upvoted 0 times
...
Yoko
9 months ago
User2: I agree, that could help meet the business requirements and product catalog requirements.
upvoted 0 times
...
Refugia
10 months ago
User1: I think setting the default consistency level of account1 to bounded staleness might be a good idea.
upvoted 0 times
...
...
Vivienne
10 months ago
I think option C is the way to go. Modifying the connection policy of App1 to support the new multi-region configuration for account1 seems like the most logical solution.
upvoted 0 times
Rebecka
9 months ago
Creating a private endpoint connection could also be a good solution to ensure App1 supports the new configuration for account1.
upvoted 0 times
...
Tiera
9 months ago
I think setting the default consistency level of account1 to bounded staleness might be a better option.
upvoted 0 times
...
Kaitlyn
9 months ago
I agree, modifying the connection policy of App1 sounds like the best approach.
upvoted 0 times
...
...

Save Cancel