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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft AZ-305 Exam - Topic 2 Question 58 Discussion

Actual exam question for Microsoft's AZ-305 exam
Question #: 58
Topic #: 2
[All AZ-305 Questions]

You have an Azure subscription. The subscription contains an app that is hosted in the East US, Central Europe, and East Asia regions.

You need to recommend a data-tier solution for the app. The solution must meet the following requirements:

Support multiple consistency levels.

Be able to store at least 1 TB of data.

Be able to perform read and write operations in the Azure region that is local to the app instance.

What should you include in the recommendation?

Show Suggested Answer Hide Answer
Suggested Answer: D, E

by Barbra at May 29, 2024, 12:01 AM

Limited Time Offer

25%

Off

Get Premium AZ-305 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dierdre
3 months ago
Azure SQL in an elastic pool could work too, but Cosmos DB is the best fit.
upvoted 0 times
...
Alisha
3 months ago
Wait, can Cosmos DB really handle 1 TB? That seems a lot!
upvoted 0 times
...
Vanda
3 months ago
Not so sure about Cosmos DB, SQL Server might be better for consistency.
upvoted 0 times
...
Janine
4 months ago
I agree, it’s perfect for multiple regions.
upvoted 0 times
...
Thersa
4 months ago
Definitely Azure Cosmos DB for that flexibility!
upvoted 0 times
...
Rebeca
4 months ago
Azure Table storage seems too basic for this app's needs, especially with the requirement for local read and write operations.
upvoted 0 times
...
Tamar
4 months ago
I practiced a similar question, and I feel like Azure SQL in an elastic pool could work, but I'm not confident it meets all the requirements for consistency levels.
upvoted 0 times
...
Matthew
4 months ago
I'm not entirely sure, but I remember that SQL Server Always On might not be the best fit for this scenario due to its complexity and regional limitations.
upvoted 0 times
...
Huey
5 months ago
I think Azure Cosmos DB might be the right choice since it supports multiple consistency levels and is designed for global distribution.
upvoted 0 times
...
Isreal
5 months ago
This seems straightforward to me. Azure Cosmos DB is designed for global distribution and flexible consistency models, plus it can handle large data volumes. I'm pretty sure that's the right choice here.
upvoted 0 times
...
Romana
5 months ago
Okay, I've got a strategy here. The question is really testing our knowledge of the various Azure data options and how they match up to the specific requirements. I'm going to carefully evaluate each answer choice against the stated needs to determine the best fit.
upvoted 0 times
...
Leonida
5 months ago
Hmm, I'm a bit unsure about this one. The requirements around consistency levels and data size make me think Azure Cosmos DB, but I'm not totally confident. I'll need to review the differences between the Azure data services to make sure I pick the right one.
upvoted 0 times
...
Marya
5 months ago
This looks like a classic Azure data solution question. I think the key is to focus on the requirements - multiple consistency levels, 1 TB of data, and local read/write operations. Azure Cosmos DB seems like the best fit based on those needs.
upvoted 0 times
...
Eun
5 months ago
Hmm, I'm a little unsure about this one. I know it has something to do with when cash is recorded, but I'm not totally confident in the right answer.
upvoted 0 times
...
Ma
5 months ago
This question seems straightforward - it's asking about the biggest risk in the given environment. I think the answer is A, since not having documentation on the system interactions and dependencies is a major vulnerability.
upvoted 0 times
...
Elke
10 months ago
Azure Table storage, eh? Sounds like a real party trick. I bet you can store all your emojis in there and still have room for the kitchen sink.
upvoted 0 times
...
Gertude
10 months ago
Wait, did you say 1 TB of data? In that case, I'd better start doing some serious squats to prepare for all the heavy lifting I'll be doing with that SQL Server availability group.
upvoted 0 times
Rodrigo
9 months ago
C) an Azure SQL database in an elastic pool
upvoted 0 times
...
Irene
9 months ago
B) a Microsoft SQL Server Always On availability group on Azure virtual machines
upvoted 0 times
...
Belen
9 months ago
A) an Azure Cosmos DB database
upvoted 0 times
...
...
Micaela
10 months ago
Personally, I'd go with the Cosmos DB option. It ticks all the boxes and you can't beat that global distribution. Plus, it's perfect for those late-night coding sessions with tacos and Red Bull.
upvoted 0 times
Jesse
8 months ago
User 3: Cosmos DB it is then, sounds like a perfect fit for the app's requirements.
upvoted 0 times
...
Fletcher
9 months ago
User 2: Definitely, the global distribution and multiple consistency levels make it a strong option.
upvoted 0 times
...
Dalene
9 months ago
User 1: I agree, Cosmos DB seems like the best choice for this scenario.
upvoted 0 times
...
...
Miesha
10 months ago
An elastic Azure SQL database pool? Hmm, I'm not convinced. What about Azure Table storage? It can handle huge amounts of data and the geo-redundant replication is a nice bonus.
upvoted 0 times
...
Tatum
10 months ago
I'm not sure about Azure Cosmos DB... Sounds a bit too complicated. Why not just use a good old SQL Server availability group? It's reliable and scalable, right?
upvoted 0 times
...
Eladia
10 months ago
Azure Cosmos DB is the way to go! It supports multiple consistency levels, can handle massive amounts of data, and allows for local read/write operations. Easy choice if you ask me.
upvoted 0 times
Lashon
10 months ago
User 2: I agree, it meets all the requirements perfectly.
upvoted 0 times
...
Norah
10 months ago
User 1: Azure Cosmos DB is definitely the best option for this scenario.
upvoted 0 times
...
...
Tiera
11 months ago
But Azure Cosmos DB also allows for local read and write operations, and it's specifically designed for globally distributed apps. I still think it's the best option.
upvoted 0 times
...
Felicitas
11 months ago
I disagree, I believe option B, a Microsoft SQL Server Always On availability group on Azure virtual machines, would be a better choice. It can handle read and write operations locally.
upvoted 0 times
...
Tiera
11 months ago
I think we should go with option A, an Azure Cosmos DB database. It supports multiple consistency levels and can store a large amount of data.
upvoted 0 times
...

Save Cancel