Free DP-300 Exam Braindumps
Administering Microsoft Azure SQL Solutions Questions 146–150 (page: 31)

Updated On: 10-Feb-2026
View Related Case Study

You need to recommend a solution to meet the security requirements and the business requirements for DB3.

What should you recommend as the first step of the solution?

  1. Run the sp_addarticle stored procedure.
  2. Run the ALTER TABLE statement and specify the ENABLE CHANGE_TRACKING Clause.
  3. Run the ALTER DATABASE statement and specify the SET CHANGE_TRACKING = ON Clause.
  4. Run the sys.sp_cdc_enable_db stored procedure.

Answer(s): D



View Related Case Study

You need to recommend a solution to ensure that the performance of DB3 is optimized after the migration to Azure SQL Database. The solution must meet availability requirements.

What should you include in the recommendation?

  1. vertical scaling
  2. a custom resource pool
  3. Resource Governor
  4. horizontal scaling

Answer(s): A

Explanation:

Vertical scaling: Increase or decrease computer power or databases as needed.
Vertical scaling is accomplished using Azure PowerShell cmdlets to change the service tier, or by placing databases in an elastic pool.
Scenario:
For DB3, manage potential performance issues caused by resource demand changes by App2 and App3.
Existing:
DB3 stores compliance data used by two applications named App2 and App3.
DB3 performance is monitored by using Extended Events sessions, with the event_file target set to a file share on a local disk of SVR3.
Resource allocation for DB3 is managed by using Resource Governor.
Planned change: Migrate DB3 to Azure SQL Database.

Incorrect:
* horizontal scaling
Add or remove database as needed.
* Resource Governor
Resource governance in Azure SQL Database
A SQL Server instance has multiple consumers of resources, including user requests and system tasks. SQL Server Resource Governor was introduced to ensure fair sharing of resources and prevent out-of-control requests from starving other requests. This feature was introduced in SQL Server years ago and over time was extended to help govern several resources including CPU, physical IO, memory, and more for a SQL Server instance. We use this functionality in Azure SQL Database as well to help govern IOPs both local and remote, CPU caps, memory, worker counts, session counts, memory grant limits, and the maximum number of concurrent requests.
* a custom resource pool
Resource Pool is a logical grouping of management servers and/or gateway servers used to distribute work among themselves and take over work from a failed member. In other words, they provide high availability and scalability for workflows.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-scale-introduction



View Related Case Study

You need to identify the event_file target for monitoring DB3 after the migration to Azure SQL Database. The solution must meet the management requirements.

What should you use as the event_file target?

  1. a SQL Server filegroup
  2. an Azure SQL database
  3. an Azure Files share
  4. an Azure Blob Storage container

Answer(s): D

Explanation:

Extended Events in Azure SQL Database and Azure SQL Managed Instance Applies to: Azure SQL Database Azure SQL Managed Instance
The feature set, functionality, and usage scenarios for Extended Events in Azure SQL Database and Azure SQL Managed Instance are similar to what is available in SQL Server. The main differences are:
*-> The event_file target always uses blobs in Azure Storage, rather than files on disk.
* In Azure SQL Database, event sessions are always database-scoped. This means that:
An event session in one database can't collect events from another database.
An event must occur in the context of a user database to be included in a session.
* In Azure SQL Managed Instance, you can create both server-scoped and database-scoped event sessions.
We recommend using server-scoped event sessions for most scenarios.
Scenario:
Requirements. Management Requirements
Continue using Extended Events to monitor DB3.
Existing Environment. Database Environment
DB3 stores compliance data used by two applications named App2 and App3.
DB3 performance is monitored by using Extended Events sessions, with the event_file target set to a file share on a local disk of SVR3.
Requirements. Planned Changes
*-> Migrate DB3 to Azure SQL Database.
Following the migration of DB3, configure the database to be part of an auto-failover group.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/xevent-db-diff-from-sv



View Related Case Study

HOTSPOT (Drag and Drop is not supported)

You need to implement the monitoring of SalesSQLDb1. The solution must meet the technical requirements.

How should you collect and stream metrics? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:





Box 1: The server, the elastic pool, and the database
Senario:
SalesSQLDb1 is in an elastic pool named SalesSQLDb1Pool.
Litware technical requirements include: all SQL Server and Azure SQL Database metrics related to CPU and storage usage and limits must be analyzed by using Azure built-in functionality.

Box 2: Azure Event hubs
Scenario: Migrate ManufacturingSQLDb1 to the Azure virtual machine platform.
Event hubs are able to handle custom metrics.

Incorrect Answers:
Azure Log Analytics
Azure metric and log data are sent to Azure Monitor Logs, previously known as Azure Log Analytics, directly by Azure. Azure SQL Analytics is a cloud only monitoring solution supporting streaming of diagnostics telemetry for all of your Azure SQL databases.

However, because Azure SQL Analytics does not use agents to connect to Azure Monitor, it does not support monitoring of SQL Server hosted on-premises or in virtual machines.



View Related Case Study

Based on the PaaS prototype, which Azure SQL Database compute tier should you use?

  1. Business Critical 4-vCore
  2. Hyperscale
  3. General Purpose v-vCore
  4. Serverless

Answer(s): D

Explanation:

Scenario: Exhibit show idle periods with intermittent spikes.
Serverless is a compute tier for single databases in Azure SQL Database that automatically scales compute based on workload demand and bills for the amount of compute used per second. The serverless compute tier also automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns.
Incorrect Answers:
B: Hyperscale is for large databases


Reference:

https://docs.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview



Viewing page 31 of 85
Viewing questions 151 - 155 out of 470 questions


Post your Comments and Discuss Microsoft DP-300 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!