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 DP-300 Exam - Topic 6 Question 97 Discussion

Actual exam question for Microsoft's DP-300 exam
Question #: 97
Topic #: 6
[All DP-300 Questions]

You plan to move two 100-GB databases to Azure.

You need to dynamically scale resources consumption based on workloads. The solution must minimize

downtime during scaling operations.

What should you use?

Show Suggested Answer Hide Answer
Suggested Answer: A

https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-sql#combining-bcdr-technologies-with-site-recovery


by Nathan at Aug 04, 2024, 06:34 PM

Limited Time Offer

25%

Off

Get Premium DP-300 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lemuel
5 months ago
D is just basic, not ideal for dynamic scaling needs.
upvoted 0 times
...
Jaclyn
5 months ago
Wait, can elastic pools really minimize downtime? Sounds too good to be true!
upvoted 0 times
...
Dalene
5 months ago
B is too heavy for this, virtual machines add unnecessary complexity.
upvoted 0 times
...
Gertude
5 months ago
I think C is better for managed instances, more control.
upvoted 0 times
...
Slyvia
6 months ago
Definitely go with A, elastic pools are great for scaling!
upvoted 0 times
...
Amie
6 months ago
I’m leaning towards Azure SQL databases for their simplicity, but I’m not confident they can handle dynamic scaling as well as the elastic pool.
upvoted 0 times
...
Jovita
6 months ago
I feel like an Azure SQL Database managed instance could work too, but I’m a bit confused about how it compares to the elastic pool in terms of scaling.
upvoted 0 times
...
Leila
6 months ago
I remember practicing a similar question, and I think SQL Server on Azure VMs might not minimize downtime as effectively as the others.
upvoted 0 times
...
Jaclyn
6 months ago
I think using an Azure SQL Database elastic pool could be a good option since it allows for dynamic scaling, but I'm not entirely sure about the downtime aspect.
upvoted 0 times
...
Daron
6 months ago
I'm pretty confident the answer is A - an Azure SQL Database elastic pool. That's designed for scenarios just like this, where you need to scale resources up and down based on workloads. The other options don't seem to fit the requirements as well.
upvoted 0 times
...
Flo
6 months ago
Okay, let's see. We need to move two 100-GB databases to Azure and be able to scale resources dynamically. I'm leaning towards an Azure SQL Database managed instance - that should give us the flexibility we need while minimizing downtime.
upvoted 0 times
...
Argelia
6 months ago
Hmm, I'm not sure about this one. I'll need to think through the requirements carefully - minimizing downtime during scaling is important. Maybe SQL Server on Azure VMs could work, but I'm not confident that's the best solution.
upvoted 0 times
...
Lennie
6 months ago
I think the key here is to find a solution that can dynamically scale resources based on workloads. Azure SQL Database elastic pool seems like a good option for that.
upvoted 0 times
...
German
7 months ago
This is a good test of my SQL knowledge. I feel confident I can work through this and identify the two correct queries.
upvoted 0 times
...
Avery
7 months ago
I'm a bit unsure, but I think it's actually 15 or more employees. That sounds familiar from my notes.
upvoted 0 times
...
Valentine
11 months ago
Option D, huh? Guess they forgot to include the 'Azure' part in the name. I'll stick with the real deal, thanks.
upvoted 0 times
...
William
11 months ago
Option B? Are you kidding me? Hosting SQL Server on a VM? That's so 2010. I want the full power of the cloud, not some half-baked solution. Definitely going with option A!
upvoted 0 times
Bulah
10 months ago
Definitely going with option A!
upvoted 0 times
...
Avery
10 months ago
I want the full power of the cloud, not some half-baked solution.
upvoted 0 times
...
Shantay
10 months ago
Option B? Are you kidding me? Hosting SQL Server on a VM? That's so 2010.
upvoted 0 times
...
...
Leah
12 months ago
Option C seems promising, but I'm not sure if I want to deal with the added complexity of a Managed Instance. Might as well keep it simple with option A and the elastic pool.
upvoted 0 times
Lisha
11 months ago
I prefer option A as well, simplicity is key when it comes to minimizing downtime during scaling operations.
upvoted 0 times
...
Albina
11 months ago
User 3: I agree, minimizing downtime is key when moving databases to Azure.
upvoted 0 times
...
Stephanie
11 months ago
I think option C could be worth considering for better performance, even with the added complexity.
upvoted 0 times
...
Danilo
11 months ago
User 2: Yeah, it's a simple solution that can dynamically scale resources.
upvoted 0 times
...
Tammy
11 months ago
User 1: I think option A with the elastic pool is the way to go.
upvoted 0 times
...
Cletus
11 months ago
I agree, option A with the elastic pool seems like the best choice for dynamic scaling.
upvoted 0 times
...
...
Daron
12 months ago
Hmm, I'm not sure about option A. What if my databases have different scaling requirements? Wouldn't it be better to go with option D and have two single Azure SQL databases instead?
upvoted 0 times
...
Stephaine
1 year ago
I think option A is the way to go. Elastic pools allow me to dynamically scale resources based on workloads, and minimize downtime during scaling operations. Sounds like the perfect fit for my databases.
upvoted 0 times
Thora
11 months ago
User 4: It's settled then, option A it is for moving those 100-GB databases to Azure.
upvoted 0 times
...
Cherry
11 months ago
User 3: Elastic pools definitely provide the flexibility to scale resources as needed without causing downtime. Option A is the way to go.
upvoted 0 times
...
Brittani
11 months ago
User 2: I agree, using two Azure SQL Databases in an elastic pool seems like the best choice for your scenario.
upvoted 0 times
...
Elli
11 months ago
User 1: I think option A is the way to go. Elastic pools allow me to dynamically scale resources based on workloads, and minimize downtime during scaling operations. Sounds like the perfect fit for my databases.
upvoted 0 times
...
...
Lelia
1 year ago
I'm not sure about that. I think we should use two databases in an Azure SQL Managed instance for better scalability and performance.
upvoted 0 times
...
Jaime
1 year ago
I agree with Oneida. Using an elastic pool will allow us to dynamically scale resources based on workloads.
upvoted 0 times
...
Oneida
1 year ago
I think we should use two Azure SQL Databases in an elastic pool.
upvoted 0 times
...

Save Cancel