Discuss Microsoft DP-420 Exam Topic 2 Question 62

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?

ASet the default consistency level of accountl to bounded staleness.

BCreate a private endpoint connection.

CModify the connection policy of App1.

DIncrease the number of request units per second (RU/s) allocated to the con-product and con-productVendor containers.

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

Get Premium DP-420 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

39 comments · newest first

Alison 10 months ago

Wait, can we really use bounded staleness for this?

Providencia 10 months ago

I think C makes more sense for App1's connection.

Carey 11 months ago

D sounds like a good idea, but is it necessary?

Keva 11 months ago

Totally agree with A, it fits the requirements perfectly!

Jacki 11 months ago

Option A is the best choice for consistency.

Rikki 11 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.

Brigette 12 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.

Yoko 12 months ago

I remember a practice question that mentioned modifying the connection policy could improve performance, but I can't recall the specifics.

Solange 12 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.

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

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

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

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

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

Brynn 1 year ago

↳ replying to Craig

User4: Let's go with option A then.

Yun 1 year ago

↳ replying to Craig

User3: I agree, it's like a 'close enough' approach.

Glenna 1 year ago

↳ replying to Craig

Yeah, I agree. It's a good balance between consistency and performance.

Beckie 1 year ago

↳ replying to Craig

I think option A is the way to go. Bounded staleness is a good fit for this.

Curtis 1 year ago

↳ replying to Craig

User2: Yeah, bounded staleness sounds like a good fit for this.

Alonzo 1 year ago

↳ replying to Craig

User1: I think option A is the way to go.

Afton 1 year ago

I think increasing the number of request units per second allocated to the containers is the best option for scalability.

Twana 1 year ago

But modifying the connection policy of App1 could also work, don't you think?

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

Arlette 1 year ago

↳ replying to Juan

B) Create a private endpoint connection.

Cherry 1 year ago

↳ replying to Juan

A) Set the default consistency level of account1 to bounded staleness.

Altha 1 year ago

I disagree, I believe creating a private endpoint connection would be a better solution.

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

Gail 1 year ago

↳ replying to Rory

User3: Let's go with option D then, it seems like the best choice for App1.

Keneth 1 year ago

↳ replying to Rory

User2: I agree, increasing the RU/s allocated to the containers might be the way to go.

Caren 1 year ago

↳ replying to Rory

User1: Option D could be a good solution to meet the product catalog requirements.

Twana 1 year ago

I think we should set the default consistency level of account1 to bounded staleness.

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

Magda 1 year ago

↳ replying to Louvenia

User3: Creating a private endpoint connection could also ensure secure communication between App1 and account1.

Yoko 1 year ago

↳ replying to Louvenia

User2: I agree, that could help meet the business requirements and product catalog requirements.

Refugia 1 year ago

↳ replying to Louvenia

User1: I think setting the default consistency level of account1 to bounded staleness might be a good idea.

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

Rebecka 1 year ago

↳ replying to Vivienne

Creating a private endpoint connection could also be a good solution to ensure App1 supports the new configuration for account1.

Tiera 1 year ago

↳ replying to Vivienne

I think setting the default consistency level of account1 to bounded staleness might be a better option.

Kaitlyn 1 year ago

↳ replying to Vivienne

I agree, modifying the connection policy of App1 sounds like the best approach.

Microsoft DP-420 Exam - Topic 2 Question 62 Discussion