Overview
Domain 1 sets up everything else on DP-300. Microsoft lists three functional groups. The first, planning and deploying Azure SQL solutions, covers recommending an offering, choosing an automated deployment method, use cases for Azure Arc-enabled SQL services and Azure SQL Database in Microsoft Fabric, partitioning and sharding plans, hybrid deployments, and patching IaaS and hybrid servers.
The second group configures Azure SQL Database, Azure SQL Managed Instance and SQL Server on Azure Virtual Machines for scale and performance, together with table partitioning and data compression. The third group is migration: judging requirements, choosing offline or online approaches, migrating into Azure and between Azure SQL services, copying or moving Managed Instance databases, and troubleshooting failed migrations. As of October 31, 2026 the exam is active with no retirement announced, and the skills outline was refreshed on October 27, 2026.
How it's tested
Questions in this domain describe a workload with compatibility needs, size, downtime tolerance and budget, then ask which platform, tier, purchasing model or migration method fits. Expect to weigh instance-level features against management overhead, and to pick online migration only when the scenario limits downtime.
-
Pick the platform
Instance features such as SQL Server Agent, cross-database queries or CLR point to Managed Instance, while OS access points to a VM.
-
Size the tier
Storage size, IO latency, read replicas or unpredictable usage decide between General Purpose, Business Critical, Hyperscale and serverless.
-
Match the migration
Allowed downtime, source version and target platform decide between backup and restore, Managed Instance link, Log Replay Service or DMS.
A retailer runs a 6 TB SQL Server 2019 database that uses cross-database queries and SQL Server Agent jobs, and can accept only minutes of downtime. Azure SQL Database lacks cross-database queries and Agent, so Managed Instance is the target. Because downtime must be minimal, an online method such as the Managed Instance link, which replicates through a distributed availability group, beats a native backup and restore that would need a long outage.
Functional groups 3
Official functional groups from the Microsoft outline, in outline order.
1.1 Plan and deploy Azure SQL solutionsOffering choice, deployment method, Arc and Fabric use cases, partitioning, sharding, hybrid deployment and patching.
- What it means
- This group covers recommending Azure SQL Database, Azure SQL Managed Instance or SQL Server on Azure VMs from requirements, choosing an automated deployment method, identifying use cases for Azure Arc-enabled SQL services and Azure SQL Database in Microsoft Fabric, planning table partitioning, recommending a sharding solution, deploying offerings and hybrid SQL Server solutions, and applying patches to IaaS and hybrid servers.
- What to understand
- Azure SQL Database is a managed single database or elastic pool with DTU or vCore purchasing and General Purpose, Business Critical or Hyperscale tiers. Managed Instance adds instance features such as SQL Server Agent, cross-database queries and Database Mail. A VM gives full OS control, but you own patching, aided by the SQL IaaS Agent extension. Arc-enabled SQL Server projects on-premises or multicloud instances into Azure for inventory, Defender, Entra authentication and pay-as-you-go licensing. SQL database in Fabric is a SaaS option whose data is mirrored to OneLake for analytics. Sharding across databases uses the elastic database client library and a shard map.
- How it shows up
- Expect a requirements list with one decisive feature or constraint that eliminates all but one offering or deployment approach.
- Common confusion
- Choosing Azure SQL Database for a workload that needs SQL Server Agent or cross-database queries, which only Managed Instance or a VM provide.
1.2 Configure resources for scale and performanceTier, compute and storage settings for each platform, plus partitioning and compression.
- What it means
- This group covers configuring Azure SQL Database, Azure SQL Managed Instance and SQL Server on Azure Virtual Machines for scale and performance, and configuring table partitioning and data compression inside the database.
- What to understand
- In Azure SQL Database you scale vCores or DTUs, choose serverless with auto-pause for intermittent use, use elastic pools for many small databases with uneven peaks, and pick Hyperscale for very large databases with fast scaling and named replicas. Business Critical adds local SSD storage and a free readable secondary. Managed Instance scales vCores and storage per instance. On VMs, choose memory-optimized sizes, Premium SSD or Premium SSD v2, separate data and log disks, read caching on data disks only, and tempdb on the local SSD. Partitioning uses a partition function and scheme. Row and page compression trade CPU for less IO and storage.
- How it shows up
- Expect scenarios about bursty workloads, many tenant databases, slow disk IO on a VM, or large tables that need sliding-window maintenance.
- Common confusion
- Treating partitioning as a query speed feature; its main gains are manageability and partition elimination, not automatic faster queries.
1.3 Plan and implement a migration strategyRequirements, online and offline methods, migrations into and between Azure SQL services, and troubleshooting.
- What it means
- This group covers evaluating migration requirements, comparing offline and online strategies, implementing both, migrating to Azure and between Azure SQL services, copying and moving Azure SQL Managed Instance databases, and troubleshooting a migration.
- What to understand
- Offline methods include native backup to URL and restore on Managed Instance or a VM, and BACPAC export and import for Azure SQL Database. Online methods keep the source live: Azure Database Migration Service, the Managed Instance link based on distributed availability groups, Log Replay Service for Managed Instance, and transactional replication into Azure SQL Database. Assessment tools flag blocking features before you move. Managed Instance database copy and move transfer a database between instances, with move removing the source after cutover. Troubleshooting usually involves network access to storage, SAS or credential errors, unsupported features and log chain gaps.
- How it shows up
- Expect a downtime limit, source version and target platform, and you choose the method or diagnose why a restore or sync failed.
- Common confusion
- Using a BACPAC for a large online migration; BACPAC export is offline and slow for big databases.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Azure SQL Database
Managed single database or elastic pool database.
- Remember
- No SQL Server Agent or cross-database queries.
- Tested as
- Platform choice questions.
- Trap
- Assuming full instance compatibility.
-
Azure SQL Managed Instance
Managed instance with near-complete SQL Server engine compatibility.
- Remember
- Supports Agent, Database Mail and cross-database queries.
- Tested as
- Lift-and-shift questions.
- Trap
- Expecting OS-level access.
-
SQL Server on Azure VMs
IaaS VM running SQL Server.
- Remember
- You own patching, backups setup and HA design.
- Tested as
- Full-control questions.
- Trap
- Forgetting the SQL IaaS Agent extension benefits.
-
Hyperscale
Tier with distributed storage scaling to 128 TB and fast backups.
- Remember
- Named replicas and fast scale-out reads.
- Tested as
- Very large database questions.
- Trap
- Assuming it is only for analytics.
-
Serverless compute
Auto-scaling compute billed per second with optional auto-pause.
- Remember
- Best for intermittent, unpredictable use.
- Tested as
- Cost optimization questions.
- Trap
- Using it for steady heavy load.
-
Elastic pool
Shared compute for many databases with varied peaks.
- Remember
- Good when peaks do not overlap.
- Tested as
- Multitenant SaaS questions.
- Trap
- Pooling databases that peak together.
-
Azure Arc-enabled SQL Server
On-premises or multicloud SQL Server managed through Azure.
- Remember
- Inventory, Defender, Entra auth, pay-as-you-go licensing.
- Tested as
- Hybrid questions.
- Trap
- Thinking Arc migrates the data.
-
SQL database in Microsoft Fabric
SaaS operational database inside Fabric.
- Remember
- Data is mirrored to OneLake automatically.
- Tested as
- Analytics integration questions.
- Trap
- Treating it as a replacement for Managed Instance.
-
Managed Instance link
Distributed availability group replication to Managed Instance.
- Remember
- Supports near-zero downtime cutover.
- Tested as
- Online migration questions.
- Trap
- Using it to target Azure SQL Database.
-
Log Replay Service
Restores a chain of backups from blob storage into Managed Instance.
- Remember
- Final cutover restores the last log.
- Tested as
- Migration questions.
- Trap
- Breaking the log chain with ad hoc backups.
-
Data compression
Row or page compression on tables and indexes.
- Remember
- Saves IO and storage at CPU cost.
- Tested as
- Storage optimization questions.
- Trap
- Compressing heavily updated hot tables blindly.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Azure SQL deployment options
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Azure SQL Database | Fully managed database or pool | Least admin effort, fewest instance features | Picking it when Agent jobs are required |
| Azure SQL Managed Instance | Managed instance in a VNet | Instance features without OS access | Expecting third-party software install |
| SQL Server on Azure VMs | SQL Server on an IaaS VM | Full control and any SQL version or feature | Ignoring patching and HA ownership |
Azure SQL Database service tiers
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| General Purpose | Remote storage, balanced compute | Budget-friendly, higher IO latency | Expecting a readable secondary |
| Business Critical | Local SSD with Always On replicas | Lowest latency, free read replica | Overpaying for low-IO workloads |
| Hyperscale | Distributed page servers up to 128 TB | Fast scaling and near-instant backups | Assuming the size limit of other tiers |
Migration approaches
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Offline | Source stops during the move | Simpler but longer downtime | Choosing it with a minutes-only window |
| Online | Continuous replication then cutover | Minimal downtime | Forgetting the cutover step |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Arc as a migration tool
- What candidates pick
- Enable Azure Arc to move the on-premises database to Azure.
- Why it looks right
- Arc puts the server in the Azure portal.
- Why it's wrong
- Arc manages SQL Server where it runs; data stays on-premises until you use a migration method.
Clue to watch for The goal is governance or licensing, not relocating data.
-
BACPAC for everything
- What candidates pick
- Export a BACPAC to migrate a 4 TB database with minimal downtime.
- Why it looks right
- BACPAC is simple and familiar.
- Why it's wrong
- BACPAC is offline, slow for large databases and creates long downtime.
Clue to watch for Size in terabytes and a short downtime window.
-
Hyperscale for small bursty apps
- What candidates pick
- Move a small intermittent database to Hyperscale.
- Why it looks right
- Hyperscale sounds most scalable.
- Why it's wrong
- Serverless General Purpose with auto-pause fits intermittent small workloads at lower cost.
Clue to watch for Usage is sporadic with idle periods.
-
Read caching on the log disk
- What candidates pick
- Enable read caching on the log disk for speed.
- Why it looks right
- Caching sounds universally faster.
- Why it's wrong
- Log writes are sequential; Microsoft guidance is no caching on log disks.
Clue to watch for A disk layout question for SQL Server on a VM.
-
Managed Instance link to SQL Database
- What candidates pick
- Use the Managed Instance link to reach Azure SQL Database.
- Why it looks right
- Link sounds generic.
- Why it's wrong
- The link targets Azure SQL Managed Instance only.
Clue to watch for The target named in the scenario is Azure SQL Database.
-
Partitioning for speed
- What candidates pick
- Partition a table to fix a slow query.
- Why it looks right
- Partitioning sounds like performance tuning.
- Why it's wrong
- Without partition elimination or maintenance gains, an index change is usually the fix.
Clue to watch for The query does not filter on the partitioning column.
Answer framework
Use these steps to pick a platform, size it and plan the move for a DP-300 scenario.
- List required engine features such as SQL Server Agent, cross-database queries, CLR, OS access or a specific SQL Server version, and note any hard limits on database size or compliance location.
- Map features to the least-managed platform that supports them: Azure SQL Database, then Managed Instance, then a VM.
- Choose tier and compute from size, IO latency, read scale-out and usage pattern, including serverless and elastic pools, and decide between DTU and vCore purchasing for licensing flexibility.
- Note hybrid needs such as Arc-enabled management, analytics in Fabric, or patching ownership for IaaS servers.
- Select the migration method from downtime tolerance and target, then plan assessment, cutover and validation steps, keeping a rollback path until the new platform is confirmed healthy.
Practice question
Want more like this? The DP-300 practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Build a one-page feature matrix first: Azure SQL Database, Managed Instance and SQL Server on Azure VMs as columns, and features such as SQL Server Agent, cross-database queries, CLR, Database Mail, active geo-replication and OS access as rows. Most platform questions become lookups once that matrix is memorized. Add the tier rows next: General Purpose, Business Critical, Hyperscale, serverless and elastic pools, with the clue words that point to each.
Then deploy a small database in each model, ideally with Bicep or the Azure CLI, and change its tier to see what scaling feels like. On a SQL Server VM, review the storage configuration the marketplace image creates. For migration, restore a native backup from blob storage to Managed Instance and read the Managed Instance link and Log Replay Service documentation until you can describe each cutover step. Finish with Arc-enabled SQL Server and SQL database in Fabric, focusing on when each is the right answer rather than on setup detail.
FAQ
How much of DP-300 is Domain 1, Plan and implement data platform resources?
Microsoft weights it at 15–20% of the exam, with three functional groups covering deployment planning, scale and performance configuration, and migration strategy.
Is DP-300 being retired or replaced?
As of October 31, 2026 Microsoft lists no retirement or replacement. The skills outline was updated on October 27, 2026 with a minor change in the security area.
When should I choose Managed Instance over Azure SQL Database?
Choose Managed Instance when the workload needs instance-scoped features such as SQL Server Agent, cross-database queries, Database Mail or CLR, but you still want a managed service.
What is SQL database in Microsoft Fabric used for?
It is a SaaS operational database inside Fabric whose data is replicated to OneLake, which suits apps that need near real-time analytics without building pipelines.
Does Azure Arc move my databases to Azure?
No. Arc connects existing SQL Server instances to Azure for management, security and licensing while the data stays where it is.
Which migration methods keep downtime minimal?
Online methods such as the Managed Instance link, Log Replay Service in continuous mode, Azure Database Migration Service online migrations and transactional replication.
Do I need to know DTU sizing in detail?
Know what DTU bundles and when vCore is preferred, such as for Azure Hybrid Benefit or independent compute and storage choices. Exact DTU numbers are rarely the point.
Other Data & Analytics certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
You have covered Azure SQL offerings, scaling, partitioning, compression and migration methods. Check whether you can match workloads to the right platform and move them safely.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the DP-300 AI tutor Get any concept explained your way