DP-300 Practice Questions

Box 1: Move to cool storage

The cool access tier has lower storage costs and higher access costs compared to hot storage. This tier is intended for data that will remain in the cool tier for at least 30 days. Example usage scenarios for the cool access tier include:

Short-term backup and disaster recovery

Older data not used frequently but expected to be available immediately when accessed

Large data sets that need to be stored cost effectively, while more data is being gathered for future processing

Note: Hot - Optimized for storing data that is accessed frequently.

Cool - Optimized for storing data that is infrequently accessed and stored for at least 30 days.

Archive - Optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements, on the order of hours.

Box 2: Move to archive storage

Example usage scenarios for the archive access tier include:

Long-term backup, secondary backup, and archival datasets

Original (raw) data that must be preserved, even after it has been processed into final usable form

Compliance and archival data that needs to be stored for a long time and is hardly ever accessed

Basic Concept: This question tests choosing the correct Azure migration approach by matching the source platform, target service, downtime tolerance, and administrative effort.

Why the selected answer is Correct: The selected values fit this scenario because they apply the required Azure SQL configuration at the correct scope and sequence: You need to ensure that the migrated environment can be managed by using multiserver administration and supports master/target (MSX/TSX) jobs.

Why the alternate choices are Wrong: The alternate selections would either use a migration tier that does not match the downtime requirement, choose a network resource that does not support the migration path, or add an unnecessary deployment component.

Box 1: Full and log backups only

Make sure to take every backup on a separate backup media (backup files). Azure Database Migration Service doesn ' t support backups that are appended to a single backup file. Take full backup and log backups to separate backup files.

Box 2: WITH CHECKSUM

Azure Database Migration Service uses the backup and restore method to migrate your on-premises databases to SQL Managed Instance. Azure Database Migration Service only supports backups created using checksum.

Basic Concept: This question tests identity and authentication for Azure SQL and SQL Server workloads, including when to use contained users, directory identities, certificate validation, or authentication profiles.

Why A and C is Correct: Active Directory or Microsoft Entra integration centralizes identity and group membership so database access can be managed through directory accounts. In this scenario, the important constraint is: You need to create the required Automation accounts. From the Azure Active Directory admin center, create a service principal. satisfies that constraint without adding an unrelated service or manual process. On SQL1. create a SQL user in the databases. matches the expected DP-300 administration action. On SQL1. create a SQL user in the databases. is a security-related control, but its value depends on whether the requirement is identity, encryption, auditing, network isolation, or data exposure reduction. The question is not asking for a general Azure capability; it is asking for the feature that produces this result: You need to create the required Automation accounts.

Why B is Wrong: A managed identity gives an Azure resource an identity in Microsoft Entra ID so it can access services such as Key Vault without embedding credentials in code. It is not the right enforcement point for this case; the scenario needs the control that governs the data or identity path being tested.

Why D is Wrong: On SQL1, create a SQL login. is a security-related control, but its value depends on whether the requirement is identity, encryption, auditing, network isolation, or data exposure reduction. It protects or manages a different security layer, so the required database access or protection behavior would still be incomplete.

Why E is Wrong: Active Directory or Microsoft Entra integration centralizes identity and group membership so database access can be managed through directory accounts. It is not the right enforcement point for this case; the scenario needs the control that governs the data or identity path being tested.

Azure RBAC is used to manage who can create, update, or delete the Synapse workspace and its SQL pools, Apache Spark pools, and Integration runtimes.

Define and implement network security configurations for resources related to your dedicated SQL pool with Azure Policy.

For rowstore tables and indexes, use the data compression feature to help reduce the size of the database. In addition to saving space, data compression can help improve performance of I/O intensive workloads because the data is stored in fewer pages and queries need to read fewer pages from disk.

Use columnstore archival compression to further reduce the data size for situations when you can afford extra time and CPU resources to store and retrieve the data.

Basic Concept: This question tests Azure monitoring and performance management, including which metric, log destination, or alerting behavior fits the operational requirement.

Why B and E is Correct: Queries that use the index will retrieve fewer data pages. matches the expected DP-300 administration action. Queries that use the index will retrieve fewer data pages. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. The question is not asking for a general Azure capability; it is asking for the feature that produces this result: Each correct answer presents a complete solution. CPU percentage is important for database compute monitoring, but it is not the Stream Analytics sizing metric when the question is about streaming units. The scenario asks for: Each correct answer presents a complete solution. That makes Queries that use the index will consume more CPU resources. the option that satisfies the required Azure SQL layer and operational outcome.

Why A is Wrong: Queries that use the index will consume more disk I/O. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It would produce a different operational signal than the one needed to investigate, alert, or tune the workload in this question.

Why C is Wrong: The index will consume more disk space. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It is useful in other troubleshooting paths, but this scenario requires a more specific monitoring or optimization feature.

Why D is Wrong: The index will consume more memory. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It would produce a different operational signal than the one needed to investigate, alert, or tune the workload in this question.

Basic Concept: This question tests identity and authentication for Azure SQL and SQL Server workloads, including when to use contained users, directory identities, certificate validation, or authentication profiles.

Why A and D is Correct: Assign the database user the db.ddladmm role. is a security-related control, but its value depends on whether the requirement is identity, encryption, auditing, network isolation, or data exposure reduction. In this scenario, the important constraint is: You need to provide User1 with the ability to add and remove columns from the tables inDBV The solution must use the principle of least privilege. Assign the database user the db.ddladmm role. satisfies that constraint without adding an unrelated service or manual process. Create a login and an associated database user. is a security-related control, but its value depends on whether the requirement is identity, encryption, auditing, network isolation, or data exposure reduction. The scenario asks for: You need to provide User1 with the ability to add and remove columns from the tables inDBV The solution must use the principle of least privilege. That makes Create a login and an associated database user. the option that satisfies the required Azure SQL layer and operational outcome.

Why B is Wrong: Assign the database user the db.owner role. is a security-related control, but its value depends on whether the requirement is identity, encryption, auditing, network isolation, or data exposure reduction. It does not satisfy the required identity, encryption, firewall, auditing, or data-exposure boundary described in the scenario: You need to provide User1 with the ability to add and remove columns from the tables inDBV The solution must use the principle of least privilege.

Why C is Wrong: Create a contained database user. is a security-related control, but its value depends on whether the requirement is identity, encryption, auditing, network isolation, or data exposure reduction. It protects or manages a different security layer, so the required database access or protection behavior would still be incomplete.