Deal of The Day! 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 4 Question 50 Discussion

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

You need to recommend a data storage solution that meets the following requirements:

* Ensures that applications can access the data by using a REST connection

* Hosts 20 independent tables of varying sizes and usage patterns

* Automatically replicates the data to a second Azure region

* Minimizes costs

What should you recommend?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Audry at Feb 10, 2024, 10:36 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
Gretchen
6 months ago
C is solid, but I still prefer A for the elastic pool benefits!
upvoted 0 times
...
Tawanna
6 months ago
I was surprised to see that option B could work too, but it lacks some features.
upvoted 0 times
...
Jamal
6 months ago
Not sure about A, isn't it more expensive than just using Azure Storage?
upvoted 0 times
...
Alethea
7 months ago
Definitely agree, A seems to fit all the requirements perfectly!
upvoted 0 times
...
Nakita
7 months ago
I think option A is the best choice for REST access and geo-replication.
upvoted 0 times
...
Jeffrey
7 months ago
I’m a bit confused about the differences between GRS and RA-GRS. I wonder if option D could still meet the requirements despite not having read access.
upvoted 0 times
...
Solange
7 months ago
I practiced a similar question, and I feel like option C might be the best fit since it specifically mentions active geo-replication, which is crucial for the requirements.
upvoted 0 times
...
Francoise
7 months ago
I'm not entirely sure, but I remember something about Azure Storage being more cost-effective. Maybe option B is worth considering?
upvoted 0 times
...
Alex
8 months ago
I think option A could be a good choice since it mentions an elastic pool, which might help with cost efficiency for the varying table sizes.
upvoted 0 times
...
Luisa
8 months ago
This is a tough call, but I'm leaning towards option A. The elastic pool with active geo-replication seems like it would provide the flexibility and redundancy required, while potentially being more cost-effective than a single SQL database.
upvoted 0 times
...
Madonna
8 months ago
I've got a good feeling about option B. Storing the tables in Azure Storage with RA-GRS seems like it would meet the needs for REST access, replication, and cost-effectiveness.
upvoted 0 times
...
Tyisha
8 months ago
I'm a bit confused by the different storage options. I'll need to review the details of each one to understand the differences and which one best fits the requirements.
upvoted 0 times
...
Lang
8 months ago
Okay, let's see. The key things I'm looking at are the REST connection, the multiple tables, and the need for automatic replication. I think option A or C might be the way to go.
upvoted 0 times
...
Stevie
8 months ago
Hmm, this seems like a tricky one. I'll need to carefully consider the requirements and weigh the pros and cons of each option.
upvoted 0 times
...
Annelle
8 months ago
The Page Inbox seems like the clear winner to me. It's specifically designed for businesses to read and respond to messages, which is exactly what this business needs to do to follow up with potential customers. The other options don't seem as directly relevant or useful.
upvoted 0 times
...
Latanya
8 months ago
I practiced something similar last week, and I think free memory is a key indicator. Maybe option C could be right?
upvoted 0 times
...
Magnolia
8 months ago
Okay, let me think this through. I'm pretty sure Azure Private Link is the way to go here. It allows you to connect to Azure PaaS services privately, which should help reduce latency between the SAP components.
upvoted 0 times
...
Aleisha
2 years ago
I still think A is the best choice, as it ensures that applications can access the data using a REST connection, which is a crucial requirement.
upvoted 0 times
...
Leah
2 years ago
I believe C) an Azure SQL database that uses active geo-replication is also a good option, as it provides more structured data storage compared to a storage account.
upvoted 0 times
...
Susana
2 years ago
I don't think option B is the best choice since we need a data storage solution specifically for hosting tables, not just general storage.
upvoted 0 times
...
Magda
2 years ago
But what about option B) tables in an Azure Storage account that use read-access geo-redundant storage (RA-GRS)?
upvoted 0 times
...
Aleisha
2 years ago
I agree, because it meets all the requirements mentioned in the question.
upvoted 0 times
...
Susana
2 years ago
I think the answer is A) an Azure SQL Database elastic pool that uses active geo-replication.
upvoted 0 times
...
Sage
2 years ago
I agree with Vashti, option B seems like the most cost-effective and efficient choice.
upvoted 0 times
...
Vashti
2 years ago
Option B uses read-access geo-redundant storage, which can benefit our data replication needs.
upvoted 0 times
...
Lonny
2 years ago
Why do you think option B is better?
upvoted 0 times
...
Vashti
2 years ago
I disagree, I believe option B is the best choice.
upvoted 0 times
...
Lonny
2 years ago
I think we should recommend option A.
upvoted 0 times
...
Mayra
2 years ago
Yeah, option B does seem like the most logical choice here. And hey, at least we don't have to worry about managing any databases! Storage accounts are like the lazy person's dream come true.
upvoted 0 times
...
Leonard
2 years ago
I'm leaning towards option B, the Azure Storage account with RA-GRS. That provides the REST access, automatic replication, and should be more cost-effective than a full SQL database. The only potential downside is handling the varying table sizes and usage patterns.
upvoted 0 times
...
Melvin
2 years ago
Okay, let's think this through. Option A, the Azure SQL Database elastic pool with active geo-replication, could work, but it might be overkill for just 20 tables. Plus, the costs might be higher than we need.
upvoted 0 times
Bambi
2 years ago
Option B might be the best choice here, considering costs and requirements
upvoted 0 times
...
Evangelina
2 years ago
Good point, we need to ensure it can handle that
upvoted 0 times
...
Lazaro
2 years ago
But will it be able to handle the varying sizes and usage patterns of the tables?
upvoted 0 times
...
Yvonne
2 years ago
That could work since it meets all the other requirements
upvoted 0 times
...
Oretha
2 years ago
What about Option B, using tables in an Azure Storage account with read-access geo-redundant storage?
upvoted 0 times
...
Lynda
2 years ago
Option A could be too expensive for just 20 tables
upvoted 0 times
...
...
Carmelina
2 years ago
Hmm, this question seems straightforward, but it's important to really understand the requirements. We need a solution that supports REST access, has multiple tables with varying usage, and provides automatic replication to another region. And we need to minimize costs.
upvoted 0 times
...

Save Cancel