Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. DP-300

Microsoft DP-300 Exam Questions
Administering Microsoft Azure SQL Solutions (Page 14 )

Updated On: 17-Feb-2026
Page 14 of 85
PDF with 430 Questions

HOTSPOT (Drag and Drop is not supported)

You are working on two projects named Project1 and Project2 that will each migrate an on-premises app to Azure. Project1 must meet the following requirements:

Have access to the operating system of the database server that hosts the app.

Have 25 TB of storage.

Project2 must meet the following requirements:

Have change data capture (CDC) enabled.

Support instance-level SQL auditing.

Support managed backups.

Have 10 TB of storage.

Offload reports.

You need to recommend an Azure SQL solution for the projects. The solution must minimize costs.

What should you include in the recommendation for each project? 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: SQL Server on Azure Virtual Machines
Project1
Project1 must meet the following requirements:
Have access to the operating system of the database server that hosts the app.
Have 25 TB of storage.

* SQL Server on Azure Virtual Machines
If your application needs access to the operating system (OS) of the database server, you should use Azure SQL Server on Azure Virtual Machines. This solution allows you to install and manage SQL Server within a virtual machine, giving you complete control over the OS and database engine.

Why SQL Server on Azure VMs?
OS-level access:
You have full control over the virtual machine's operating system, including updates, patching, and configuration.

Lift-and-shift scenarios:
It's ideal for migrating existing SQL Server applications to Azure with minimal changes, allowing you to maintain your current environment and infrastructure.

The maximum size for a single data disk attached to an Azure Virtual Machine is 32 TB. However, the total size of all data disks attached to a single VM can be up to 256 TB.

Incorrect:
* Azure SQL Database:
This is a fully managed PaaS service where Microsoft handles OS patching, backups, and maintenance. You don't have direct access to the OS or the database engine.

* Azure SQL Managed Instance:
This is a fully managed PaaS service that offers a high degree of SQL Server compatibility but still doesn't provide OS-level access.

Box 2: Azure SQL Managed Instance General Purpose Service
Project2
Project2 must meet the following requirements:
Have change data capture (CDC) enabled.
Support instance-level SQL auditing.
Support managed backups.
Have 10 TB of storage.
Offload reports.

Azure SQL Database and Azure SQL Managed Instance are Azure database solutions that support managed backups.

Azure SQL Managed Instance and Azure SQL Database Hyperscale both support 10 TB of storage. Azure SQL Managed Instance can store up to 32 TB, while Hyperscale can scale to 100 TB.

Azure SQL Managed Instance Max instance reserved storage
*-> General Purpose: up to 32 TB
Business Critical: up to 4 TB

Hardware generations have different characteristics, as described in the following table from 2025:



For Change Data Capture (CDC) within Azure, Azure SQL Database is a suitable choice, particularly when using Azure Data Factory or Azure Synapse Analytics. Both Azure SQL Database and SQL Server offer native CDC support.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what- is-overview https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/resource-limits



You have an on-premises Microsoft SQL Server database named DB1.

You plan to migrate DB1 to an Azure SQL database named DB2 by using the Data Migration Assistant (DMA).

What will be migrated?

  1. functions, roles, trace flags, and views
  2. functions, stored procedures, views, and roles
  3. agent jobs, functions, stored procedures, and views
  4. functions, operators, stored procedures, and views

Answer(s): B

Explanation:

The Data Migration Assistant (DMA) primarily migrates SQL Server databases. It helps assess and migrate on- premises SQL Server databases to newer versions of SQL Server or to Azure SQL Database. Specifically, DMA moves the schema, data, and uncontained objects from a source server to a target server.
Here's a more detailed breakdown of what DMA handles:
Schema: This includes database structures like tables, views, stored procedures, and user-defined functions.
Data: This refers to the actual information stored within the database tables.

Uncontained Objects: These are objects that are not part of a specific database schema, such as logins and roles.
--
The migration workflow helps you to migrate the following components:
Schema of databases
Data and users
Server roles
SQL Server and Windows logins
Incorrect:
Not A: Not trace flags.
Not C: Not agent jobs. SQL Server Agent Jobs require separate handling during migration.
Not D: Not Operators


Reference:

https://learn.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-ver17



You have an on-premises Microsoft SQL Server instance named SQL1 that hosts multiple databases.

You have an Azure subscription that contains an Azure SQL managed instance named SQLMI1.

You need to perform an offline migration of the SQL1 databases to SQLMI1 by using Azure Data Studio.

What should you install on SQL1?

  1. Data Migration Assistant (DMA)
  2. SQL Server Data Tools (SSDT)
  3. a self-hosted integration runtime
  4. an Azure Migrate appliance

Answer(s): C

Explanation:

Migrate SQL Server to Azure SQL Managed Instance with DMS
You can use Azure Database Migration Service (DMS) and the Azure SQL migration extension in Azure Data Studio to migrate databases from a SQL Server instance to Azure SQL Managed Instance with minimum downtime.
Prerequisites include:
* Provide an SMB network share, Azure storage account file share, or Azure storage account blob container that contains your full database backup files and subsequent transaction log backup files. Database Migration Service uses the backup location during database migration.
* If your database backups are on a network file share, provide a computer on which you can install a self- hosted integration runtime to access and migrate database backups. The migration wizard gives you the download link and authentication keys to download and install your self-hosted integration runtime.
* If you use a self-hosted integration runtime, make sure that the computer on which the runtime is installed can connect to the source SQL Server instance and the network file share where backup files are located.
* Etc.


Reference:

https://learn.microsoft.com/en-us/data-migration/sql-server/managed-instance/database-migration-service?
tabs=offline-with-extension



You have an Azure subscription that contains an Azure SQL database named DB1.

You configure a new data sync group as shown in the exhibit. (Click the Exhibit tab.)



You need to minimize how long it takes to perform the first sync.

What should you do?

  1. From Private endpoint connections, approve the private endpoint connection.
  2. From Private endpoint connections, create a new private endpoint connection.
  3. From Database Sync Group, select Sync.
  4. From Create Data Sync Group, change the sync frequency to 60 seconds.

Answer(s): A

Explanation:

Private endpoint connections for Azure SQL Database in a data sync group need to be manually approved.
This approval process ensures that the connection from the data sync service to your database is secure and authorized. You'll need to approve the service-managed private endpoint connection within the "Private endpoint connections" section in the Azure portal or through PowerShell during the sync group configuration.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/sql-data-sync-sql-server-configure



HOTSPOT (Drag and Drop is not supported)

You have an on-premises Microsoft SQL Server instance named SQLSVR1 that hosts a database named DB1.

You have an Azure subscription that contains an Azure SQL database named SQLDB1.

You need to migrate the data stored in DB1 to SQLDB1 by using SQL Server replication. The solution must minimize the performance impact on DB1.

How should you configure the replication? 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: As a push subscriber and a distributor
Configure SQLDB 1

To migrate a SQL Server database to Azure SQL Database using replication, you'll need to set up transactional replication with the on-premises SQL Server as the publisher and distributor and the Azure SQL Database as the subscriber. This process involves configuring the replication topology, including the publication, subscription, and the distributor. You'll also need to ensure proper authentication and firewall rules are set up.

Replication Configuration:
Distribution:
Configure the on-premises SQL Server as the distributor. This can be the same instance as the publisher or a separate one.

Publication:
Create a publication on the on-premises SQL Server, specifying the database and tables to be replicated.

Subscription:
Configure the Azure SQL Database as a push subscriber to the publication.

Incorrect:
* To use a pull subscription only
Only push subscriptions to Azure SQL Database are supported.

Box 2: Transactional with updatable subscriptions
Type of replication

Snapshot and one-way transactional replication are supported. Peer-to-peer transactional replication and merge replication aren't supported.

Incorrect:
* Snapshot
Data Migration and Synchronization:

Initial Snapshot:
The initial data transfer to the subscriber is typically done via a snapshot, but here we want minimize the performance impact on DB1.

Transactional Replication:
After the initial snapshot, transactional replication ensures that subsequent changes (inserts, updates, deletes) on the source database are replicated to the Azure SQL Database in near real-time.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database






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

Join the DP-300 Discussion