DP-300 Plan and implement data platform resources Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure SQL Database hyperscale

  Why it's wrong here

  Hyperscale is a service tier for Azure SQL Database that supports large databases up to 100 TB and rapid scale-out, but it does not support SQL Server Agent or cross-database queries. It also does not provide the same level of network isolation as a managed instance. It is not a separate deployment option but a service tier within Azure SQL Database.

• ✗

  Azure SQL Database elastic pool

  Why it's wrong here

  Elastic pools allow multiple databases to share a set of resources, which can be cost-effective for multiple databases with varying usage, but they do not provide dedicated compute and storage per database. They also do not support SQL Server Agent or cross-database queries. Isolation is at the database level, not at the network or tenant level.

• ✓

  Azure SQL Managed Instance

  Why this is correct

  Azure SQL Managed Instance provides a near-100% compatible SQL Server surface area, including support for SQL Server Agent, cross-database queries, and CLR. It is deployed into a dedicated subnet within an Azure virtual network, providing network isolation. It also offers dedicated compute and storage resources per instance. This meets all the stated requirements for isolation, SQL Server Agent, and cross-database queries.

• ✗

  Azure SQL Database single database

  Why it's wrong here

  Azure SQL Database single database provides a fully managed database, but it does not support SQL Server Agent or cross-database queries. It is isolated at the database level but not at the network or tenant level in the same way as a managed instance. It also does not provide dedicated compute and storage resources in the same sense; resources are shared within the service tier.

Go deeper

Related to this question