Microsoft Azure Database Administrator Associate
225 practice questions
Last reviewed: April 2026
Personal notes and resource links for your study journey
Filter by Certification
DP-300 validates the day-to-day skills of a database administrator running SQL workloads on Azure: deploying and configuring Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VMs; securing data; tuning performance; automating routine tasks; and engineering high availability and disaster recovery. The audience is working DBAs migrating from on-premises SQL Server to Azure, and cloud engineers picking up DBA responsibilities. The exam runs 50 questions in 120 minutes — longer than most associate exams — including drag-and-drops, scenario items, and case studies. Expect a heavy T-SQL component for tuning and security questions.
About 22%. Deployment options across Azure SQL Database, SQL MI, and SQL on VMs; provisioning, sizing, vCore vs. DTU, hyperscale, serverless tier, migrations with DMS / DMA, and IaC.
About 18%. Microsoft Entra authentication, RBAC, contained users, TDE, Always Encrypted, dynamic data masking, row-level security, auditing, and Microsoft Defender for SQL.
About 22%. Query Store, Intelligent Query Processing, automatic tuning, indexes (rowstore / columnstore), execution plans, blocking / deadlocks, and Azure-side metrics with Log Analytics.
About 18%. Elastic jobs, SQL Agent on MI / VM, Azure Automation runbooks, Logic Apps for ops, alerts, and PowerShell / Azure CLI scripting for DBA tasks.
About 20%. Active geo-replication, auto-failover groups, Always On AGs on VMs, backups (PITR, LTR), and RPO / RTO planning.
Services you'll encounter on the exam and why each one matters.
Fully managed PaaS SQL Server engine with DTU/vCore purchasing models, serverless and Hyperscale tiers, auto-tuning, and built-in automatic backups.
Why it's on the exam: Domain 1 (Plan and implement data platform resources) anchors most scenario questions on SQL Database tier/SKU selection and provisioning patterns.
Near-100% SQL Server instance-level compatibility surface — SQL Agent, cross-DB queries, CLR, Service Broker — delivered as a managed VNet-injected service.
Why it's on the exam: Domain 1 + Domain 5 contrast Managed Instance against Azure SQL DB and SQL-on-VM — picking the right platform by feature-parity and HA pattern is a recurring exam scenario.
IaaS SQL Server with full OS control, custom storage layouts, SQL IaaS Agent extension for automated patching/backup, and BYOL/Azure-Hybrid-Benefit licensing.
Why it's on the exam: Domain 1 expects you to choose SQL-on-VM when on-prem feature parity (cross-instance jobs, custom CLR, third-party agents) outweighs PaaS simplicity.
Managed Postgres with zone-redundant HA, read replicas, server-parameter customization, scheduled maintenance windows, and pgvector / extension support.
Why it's on the exam: Domain 1 + Domain 3 test the open-source platforms — Flexible Server is the canonical Postgres answer for parameter tuning and HA configuration questions.
Managed MySQL with zone-redundant HA, burstable/general-purpose/business-critical SKUs, server parameters, stop/start, and audit/slow-query logging.
Why it's on the exam: Domain 3 (Monitor, configure, and optimize) tests MySQL slow-query and parameter tuning; Domain 5 covers MySQL HA and PITR scenarios.
Globally distributed multi-model database — Core (NoSQL), MongoDB, Cassandra, Gremlin, Table, and Cosmos for PostgreSQL — with five consistency levels and per-region failover.
Why it's on the exam: Domain 1 includes Cosmos DB API selection and partition-key design; Domain 5 covers multi-region writes and automatic/manual failover priority.
High-availability primitives — Always On availability groups inside Managed Instance/SQL-on-VM and auto-failover groups across regions for Azure SQL DB/MI.
Why it's on the exam: Domain 5 (HA/DR) is dominated by failover-group setup, listener endpoints, and RTO/RPO trade-offs between sync vs. async secondaries.
Long-term retention (LTR) and geo-restore for Azure SQL DB/MI plus Azure Backup vaults for SQL-on-VM workloads, with policy-driven RPO and immutable backups.
Why it's on the exam: Domain 5 tests PITR window, LTR retention design, and cross-region geo-restore as the canonical SQL recovery pattern.
Windows-native admin client for SQL Server, Azure SQL DB/MI — Activity Monitor, Query Store, Maintenance Plans, Always On dashboards, and Extended Events.
Why it's on the exam: Domain 3 + Domain 4 reference SSMS as the tool for performance investigation (DMVs, plan inspection) and scheduled-job authoring on Managed Instance.
Cross-platform notebook-style admin client with extensions for SQL Server, PostgreSQL, dashboard widgets, schema compare, and integrated terminal.
Why it's on the exam: Domain 4 (Automation) cites Azure Data Studio notebooks as the way to author and version SQL runbooks for ops handoffs.
In-instance job scheduler (SQL Server, Managed Instance) with T-SQL/PowerShell steps; Elastic Jobs cover the same surface for Azure SQL Database fleets.
Why it's on the exam: Domain 4 is anchored on automated maintenance — index rebuilds, statistics updates, integrity checks — scheduled via Agent or Elastic Jobs.
Telemetry hub for SQL workloads — Database Watcher, Query Store integration, Query Performance Insight, Intelligent Insights, and KQL-queryable diagnostic logs.
Why it's on the exam: Domain 3 (Monitor, configure, and optimize) tests Query Store + QPI as the primary path for identifying regressed plans and runaway queries.
Threat-detection layer for Azure SQL DB/MI and SQL-on-VM — vulnerability assessment, SQL injection alerts, anomalous-access detection, and remediation guidance.
Why it's on the exam: Domain 2 (Implement a secure environment) names Defender for SQL as the AWS-equivalent of GuardDuty-for-databases — required reading for any security scenario.
Unified data-governance suite — automated scanning + classification of SQL DB/MI/Synapse, sensitivity labels, lineage, and data-map glossary.
Why it's on the exam: Domain 2 references Purview classification + sensitivity labels as the answer to "discover and protect sensitive columns at scale".
DR orchestrator that replicates SQL-on-VM workloads cross-region/cross-on-prem and runs scripted failover plans with replication health and recovery-point tracking.
Why it's on the exam: Domain 5 contrasts ASR (VM-level DR for SQL-on-VM) with failover groups (engine-level DR for PaaS) — knowing the boundary is a recurring exam pattern.
Per-subscription view of planned maintenance, health advisories, and service issues affecting SQL DB/MI/Postgres/MySQL, with Resource Health for per-instance status.
Why it's on the exam: Domain 3 + Domain 5 cite Service Health alerts as the canonical mechanism for catching planned-maintenance windows and incident notifications before they bite.
Cloud identity directory; Azure SQL DB/MI and Postgres/MySQL Flexible Server authenticate via Entra ID — token-based, password-less, with group-based access.
Why it's on the exam: Domain 2 expects Entra-based authentication (groups, managed identities, contained users) as the default over SQL logins.
Managed store for customer-managed keys (CMK), used for SQL Transparent Data Encryption (TDE) Bring-Your-Own-Key, Always Encrypted column keys, and connection-string secrets.
Why it's on the exam: Domain 2 (security) tests TDE-with-CMK rotation, Always Encrypted setup, and secret retrieval via managed identity — all anchored in Key Vault.
Declarative governance with built-in initiatives for SQL (audit, TDE, public-endpoint deny, allowed SKU) and custom policies via deny/audit/deployIfNotExists effects.
Why it's on the exam: Domain 1 + Domain 2 cite Azure Policy as the enforcement mechanism for TDE-on, public-network-access-off, and approved SKU baselines across SQL fleets.
CSPM + workload-protection umbrella that aggregates Defender for SQL findings, scores SQL workloads against the Microsoft Cloud Security Benchmark, and tracks remediation.
Why it's on the exam: Domain 2 references Defender for Cloud as the dashboard for tracking SQL secure-score compliance and acting on vulnerability-assessment results.
$95k–$130k–$175k USD annual
Range covers US-based mid-to-senior DBAs where Azure SQL proficiency is required. Senior data-platform engineers at FAANG / fintech often clear $200k TC. Non-coastal US markets and traditional enterprise DBAs trend lower; cloud-migration specialists trend higher.
Source: levels.fyi 2025 DBA / data engineer roles, U.S. BLS OEWS May 2024 (15-1242 database administrators, 15-1245 database architects), Glassdoor 2025. Figures are approximate; actual compensation depends on role, region, and experience.
DP-300 demand is steady, driven by ongoing migration of on-premises SQL Server estates onto Azure SQL Database and SQL Managed Instance — a multi-year enterprise trend. Recruiters use it as the canonical proof of Azure SQL operational competence. It pairs commonly with AZ-104 for cross-functional cloud admins, with DP-203 / DP-700 for engineers who span DBA and data-engineering work, and with DP-100 / DP-600 for data-platform generalists. Demand is especially strong in financial services, healthcare, government, and ISVs running heavy SQL Server estates.
There are no formal prerequisites. Microsoft recommends one to two years of database administration experience and working knowledge of T-SQL and SQL Server internals. Candidates without that background should plan extra study time. AZ-900 and DP-900 are useful conceptual on-ramps but not required.
The official Microsoft Learn path covers all five domains in roughly 35–45 hours, focused on Azure SQL family operations, security, and HA/DR. Hands-on lab time is essentially required: a personal Azure subscription with at least one Azure SQL DB, one SQL MI (or trial), and a SQL VM is ideal for practicing failovers, security configurations, and Query Store. Many candidates supplement with Microsoft's official practice assessment plus a third-party video course (Pluralsight, Udemy, Tutorials Dojo).
DP-300 sits in the Associate tier and is broadly considered moderately challenging — easier than AZ-204 for experienced DBAs, but harder than DP-900 by a wide margin. Plan on 70–110 hours of study over 7–10 weeks with prior SQL Server DBA background; substantially longer if SQL is new. The exam runs about 120 minutes — longer than typical associate exams — with 40–60 questions in multiple-choice, multiple-response, drag-and-drop, hot-area, and case-study formats. Case studies are timed separately and cannot be revisited once you move past them.
The most common stumbling block is the breadth across three deployment models — Azure SQL DB, SQL MI, and SQL on VMs each have different security, HA, and backup behavior, and the exam expects you to know which features apply where. T-SQL fluency for Always Encrypted, dynamic data masking, and row-level security examples is also frequently underestimated.
Most recent skills-measured update. Refreshed Microsoft Entra authentication coverage, expanded Hyperscale and serverless content, modernized Defender for SQL framing. Microsoft refreshes DP-300 approximately every 12–18 months without changing the exam code.
Restructured into the current five-domain layout, rebalanced weights toward security and automation, and renamed Azure AD references to Microsoft Entra ID.
Initial GA, replacing the retired Microsoft Database track exams. Original outline focused on Azure SQL DB and SQL MI day-to-day administration.
DP-300 (Microsoft Azure Database Administrator Associate) is a a moderately difficult exam expecting practical hands-on experience plus solid understanding of best practices Associate-level exam. Most candidates need 80–150 hours of study spread over 6–12 weeks for associate-level exams. Most candidates who score consistently above the passing threshold on practice exams pass on their first attempt.
Most candidates need 80–150 hours of study spread over 6–12 weeks for associate-level exams. Time-to-pass varies widely by prior experience. Engineers with hands-on production experience in the underlying technology typically need less; candidates new to the platform should plan toward the upper end of that range.
DP-300 is a recognized credential in the Azure ecosystem and signals validated knowledge to employers, recruiters, and clients. Whether it is worth the time and fee for you depends on your role and goals — it tends to pay off most for cloud engineers, architects, and consultants who work with Azure day-to-day or want to move into roles that do.
The passing score for DP-300 is 700 / 1000. The exam contains 50 questions and lasts 2 hr.
The DP-300 exam fee is $165 USD. Fees are set by Azure and may vary by region; always confirm the current price on the official Azure certification page before booking.
Microsoft role-based certifications expire after 1 year but can be renewed for free via an unproctored online assessment on Microsoft Learn, starting 6 months before expiration.
Yes. You can take the exam online (proctored via the provider's secure browser, available 24/7 in most regions) or at an in-person Pearson VUE test center during business hours. Both formats use the same questions, time limit, and passing score.
CertLabPro provides 15 study modes across the practice question bank for DP-300. The exam-simulation mode mirrors the real exam: 50 questions in 2 hr, with the same passing threshold of 700 / 1000. Browse mode lets you read every Q&A statically.