MENU
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?
Suggested Answer: A
Get Premium DP-300 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
36 comments · newest first
LE
Lemuel
11 months ago
D is just basic, not ideal for dynamic scaling needs.
JA
Jaclyn
11 months ago
Wait, can elastic pools really minimize downtime? Sounds too good to be true!
DA
Dalene
11 months ago
B is too heavy for this, virtual machines add unnecessary complexity.
GE
Gertude
12 months ago
I think C is better for managed instances, more control.
SL
Slyvia
12 months ago
Definitely go with A, elastic pools are great for scaling!
AM
Amie
1 year 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.
JO
Jovita
1 year 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.
LE
Leila
1 year ago
I remember practicing a similar question, and I think SQL Server on Azure VMs might not minimize downtime as effectively as the others.
JA
Jaclyn
1 year 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.
DA
Daron
1 year 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.
FL
Flo
1 year 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.
AR
Argelia
1 year 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.
LE
Lennie
1 year 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.
GE
German
1 year ago
This is a good test of my SQL knowledge. I feel confident I can work through this and identify the two correct queries.
AV
Avery
1 year ago
I'm a bit unsure, but I think it's actually 15 or more employees. That sounds familiar from my notes.
VA
Valentine
1 year ago
Option D, huh? Guess they forgot to include the 'Azure' part in the name. I'll stick with the real deal, thanks.
WI
William
1 year 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!
BU
Bulah
1 year ago
Definitely going with option A!
AV
Avery
1 year ago
I want the full power of the cloud, not some half-baked solution.
SH
Shantay
1 year ago
Option B? Are you kidding me? Hosting SQL Server on a VM? That's so 2010.
LE
Leah
2 years 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.
LI
Lisha
1 year ago
I prefer option A as well, simplicity is key when it comes to minimizing downtime during scaling operations.
AL
Albina
1 year ago
User 3: I agree, minimizing downtime is key when moving databases to Azure.
ST
Stephanie
1 year ago
I think option C could be worth considering for better performance, even with the added complexity.
DA
Danilo
1 year ago
User 2: Yeah, it's a simple solution that can dynamically scale resources.
TA
Tammy
1 year ago
User 1: I think option A with the elastic pool is the way to go.
CL
Cletus
1 year ago
I agree, option A with the elastic pool seems like the best choice for dynamic scaling.
DA
Daron
2 years 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?
ST
Stephaine
2 years 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.
TH
Thora
1 year ago
User 4: It's settled then, option A it is for moving those 100-GB databases to Azure.
CH
Cherry
1 year ago
User 3: Elastic pools definitely provide the flexibility to scale resources as needed without causing downtime. Option A is the way to go.
BR
Brittani
1 year ago
User 2: I agree, using two Azure SQL Databases in an elastic pool seems like the best choice for your scenario.
EL
Elli
1 year 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.
LE
Lelia
2 years 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.
JA
Jaime
2 years ago
I agree with Oneida. Using an elastic pool will allow us to dynamically scale resources based on workloads.
ON
Oneida
2 years ago
I think we should use two Azure SQL Databases in an elastic pool.