Exam DP-300 topic 6 question 1 discussion

Option is correct because he is asking for Two Databases, and to reduce the resource the best is to use an elastic pool with a certain number of eDTUs that are shared among multiple databases in the pool Note: Dynamic scalability is different from autoscale. Autoscale is when a service scales automatically based on criteria, whereas dynamic scalability allows for manual scaling with a minimal downtime.

A should be correct. The two database can share resources of the elastic pool.

If it had been "Azure SQL Database serverless" then I would pick it. But it is just "Azure SQL Database". So go with A. "Elastic pool"

A. An Azure SQL Database elastic pool

You should use Azure SQL Database elastic pools for the two 100-GB databases to dynamically scale resources consumption based on workloads and minimize downtime during scaling operations. Azure SQL Database elastic pools enable you to manage multiple databases as a single unit and share resources dynamically based on the workload of each database, reducing the administrative overhead of managing individual databases and minimizing downtime during scaling operations.

The elastic pool will dynamically scale each database based on the demand. https://mattou07.net/posts/reduce-your-azure-sql-server-costs-with-elastic-pools/

I'm not convinced we need Elastic Pool. Elastic Pool is good to use when we want two or more DBs to share resources (especially if they don't peak at the same time). Elastic Pool DOES NOT support Auto Scaling . I think we should use Azure SQL DBs (two DBs). it supports auto scaling and with minimal downtime. The correct Answer is D. https://learn.microsoft.com/en-us/azure/azure-sql/database/scale-resources?view=azuresql

Correct answer A

The correct Answer is A. not b/c we are planning to migrate TWO dbs. b/c "dynamically scale resources consumption based on workloads." only works for option A.

Answer: A, C and D are correct. Azure SQL Database and SQL Managed Instance enable you to dynamically add more resources to your database with minimal downtime. Azure SQL Database offers the ability to dynamically scale your databases: • With a single database, you can use either DTU or vCore models to define maximum amount of resources that will be assigned to each database. • Elastic pools enable you to define maximum resource limit per group of databases in the pool. Azure SQL Managed Instance allows you to scale as well: • SQL Managed Instance uses vCores mode and enables you to define maximum CPU cores and maximum of storage allocated to your instance. All databases within the managed instance will share the resources allocated to the instance https://docs.microsoft.com/en-us/azure/azure-sql/database/scale-resources

I really dislike questions like this. You'd almost always choose Azure SQL over MI unless there's a compat reason. Putting 2 databases in an elastic pool is typically counterproductive cost-wise, but since the question is only about downtime, both A and D have similar latency in scaling. SQL MI can scale also, but not as fast as Azure SQL DB. Finally, Azure SQL DB using serverless (no elastic pool) can be considered since we don't know the workload. Staying within the same service level (standard to standard or gp to gp) will be the fastest for 100GB databases, as data is not copied and detached/attached. Moving between tiers is quite a bit slower (gp -> bc). Here, hyperscale offers the all around fastest rescale time, so even though you don't *need* hyperscale for size, the only thing being asked is, "which scales fastest?" Since hyperscale is a service tier of Azure SQL DB, I think D is correct as it offers the most options. Refer to latency chart: https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-scale

For me it's A, since they stated two databases

Azure SQL Managed Instance allows you to scale as well: SQL Managed Instance uses vCores mode and enables you to define maximum CPU cores and maximum of storage allocated to your instance. All databases within the managed instance will share the resources allocated to the instance

Azure SQL Database offers the ability to dynamically scale your databases: With a single database, you can use either DTU or vCore models to define maximum amount of resources that will be assigned to each database. Elastic pools enable you to define maximum resource limit per group of databases in the pool.

I would say D since you need Hyperscale which is type of Azure SQL DB