Microsoft • DP-420
Write efficient queries, create indexing policies, manage, and provision resources in the SQL API and SDK with Microsoft Azure Cosmos DB.
Questions
677
Duration
100 minutes
Passing Score
700/1000
Difficulty
SpecialtyLast Updated
Jan 2025
The Microsoft Certified: Azure Cosmos DB Developer Specialty (DP-420) validates subject matter expertise in designing, implementing, and monitoring cloud-native applications that store and manage data using Azure Cosmos DB. The certification covers the full development lifecycle: modeling non-relational data, selecting partition keys, managing throughput and scaling, implementing the SQL API and .NET/Java SDKs, writing server-side JavaScript (stored procedures, triggers, user-defined functions), and integrating Cosmos DB with other Azure services such as Azure Functions, Azure Synapse Link, and Event Hubs.
The exam was last updated on January 27, 2025, and reflects current platform capabilities including hierarchical partition keys, the integrated cache, Always Encrypted, and Azure Synapse Link with Change Data Capture. Candidates are assessed on their ability to optimize query performance through indexing strategies and cost analysis, implement change feeds, configure backup and restore, enforce security controls using Microsoft Entra ID and Azure RBAC, and automate operations using Azure Resource Manager templates and PowerShell/CLI.
This certification is intended for developers and data engineers with hands-on experience building Azure applications that rely on Azure Cosmos DB for NoSQL as their primary data store. Suitable job titles include Azure Developer, Cloud Application Developer, and Data Engineer. Candidates typically have two or more years of experience working with Azure services and are comfortable reading C# or Java application code, writing SQL queries for the Cosmos DB NoSQL API, and interpreting JSON documents.
Professionals pursuing this certification often work in roles where they are responsible for both the data modeling decisions and the operational health of a Cosmos DB solution—including security, availability, resilience, and performance. It is particularly relevant for those building globally distributed, high-throughput applications such as IoT platforms, e-commerce systems, and real-time analytics pipelines.
Microsoft does not enforce formal prerequisites for DP-420, but candidates are expected to have practical experience developing applications for Azure and working with Azure Cosmos DB database technologies. Specifically, candidates should be proficient with the Azure Cosmos DB for NoSQL API, able to write efficient SQL queries against it, create and tune indexing policies, and use the Azure Cosmos DB SDK (C# or Java). Familiarity with JSON structure and the ability to write server-side JavaScript for stored procedures and triggers is also required.
A solid understanding of Azure fundamentals—including resource provisioning, Azure role-based access control (RBAC), Azure Monitor, and ARM templates—is strongly recommended. Candidates who have completed the AZ-900 (Azure Fundamentals) or AZ-204 (Azure Developer Associate) certification will find much of this background knowledge directly applicable. Microsoft's free learning path DP-420T00 (Design and Implement Cloud-Native Applications with Azure Cosmos DB) is the official preparatory course.
Exam DP-420 is a proctored assessment delivered through Pearson VUE, available both online (remote proctored) and at Pearson VUE test centers. Candidates are given 100 minutes to complete the exam. The number of questions is not publicly disclosed and may vary, but the exam may include multiple question types such as multiple choice, drag-and-drop, build-list, case studies, and interactive lab components. A score of 700 or higher on a scale of 100–1000 is required to pass.
The exam is available in English, Japanese, Chinese (Simplified), Chinese (Traditional), Korean, German, French, Spanish, Portuguese (Brazil), and Italian. If taking the exam in a non-English localization, candidates may request an additional 30 minutes. The certification expires annually and can be renewed at no cost by passing a free online assessment on Microsoft Learn. The exam price is approximately $165 USD, varying by country or region of the testing location.
Earning the Azure Cosmos DB Developer Specialty positions professionals for roles such as Senior Azure Developer, Cloud-Native Application Architect, and Data Platform Engineer—positions that command premium salaries due to the specialized nature of globally distributed database design. According to industry surveys, Azure-certified developers with specialty credentials typically earn between $120,000 and $165,000 USD annually in North American markets, with variation by region and total experience. Demand for Cosmos DB expertise is driven by enterprises building IoT, gaming, retail, and financial services applications that require low-latency, multi-region access at scale.
Compared to the broader AZ-204 (Azure Developer Associate), DP-420 demonstrates deep, focused expertise in a specific high-value technology—making it particularly compelling on a resume for organizations heavily invested in the Azure data platform. The certification is recognized globally and renewable annually at no cost, ensuring that credential holders remain current with platform evolution. It also pairs well with certifications such as DP-203 (Azure Data Engineer Associate) for professionals who straddle application development and data engineering responsibilities.
5 sample questions with correct answers and explanations. Start a practice session to test yourself across all 677 questions.
1. CrossPlatformIntegration Corp has a hybrid architecture with on-premises Apache Kafka clusters and Azure-based data processing. They need to integrate their existing Kafka infrastructure with Azure Cosmos DB for NoSQL while maintaining their current streaming architecture. What integration approach should they implement?
Explanation
The open-source Kafka Connect connector for Azure Cosmos DB allows integration with existing Kafka infrastructure without requiring migration to Azure services. This approach preserves their current architecture while adding Cosmos DB integration capabilities. Migrating to Event Hubs would require significant infrastructure changes and may not provide equivalent functionality. Stream Analytics could work as a bridge but adds complexity compared to direct Kafka Connect integration. Replacing Kafka with Data Factory would eliminate their streaming architecture and require complete re-architecting of their data pipeline.
2. IndexStrategy Corp needs to adjust indexes on their Azure Cosmos DB database to optimize query performance for their content management system. They have articles, tags, categories, and user interactions with various query patterns: full-text search, category browsing, tag filtering, and user activity tracking. Current queries are consuming excessive RUs. What indexing adjustment strategy should they implement?
Explanation
Implementing composite indexes for multi-property queries and excluding infrequently queried properties provides targeted optimization that reduces RU consumption while maintaining query performance for important operations. This approach addresses the specific query patterns without over-indexing. Removing all unnecessary indexes and creating only minimal indexes might over-optimize and could negatively impact query flexibility. Maintaining default indexing ignores the opportunity to optimize for specific query patterns and reduce RU consumption. Separate indexing policies per document type within the same container is not supported in Cosmos DB - indexing policies apply to the entire container.
3. CloudFirst Analytics wants to understand the RU cost difference between point reads and queries in Azure Cosmos DB. They have a 1KB document and want to know the most cost-effective way to retrieve it when they know both the id and partition key. What should they expect?
Explanation
Point reads are significantly more cost-effective than queries when you know the exact item coordinates. A point read for a 1KB document costs only 1 RU because it directly accesses the item without using the query engine. Queries have a minimum cost of 2.3 RUs and can cost more depending on complexity and the number of items returned, making point reads the preferred method for single-item retrieval.
4. MultiWorkload Corp runs different types of operations on their Azure Cosmos DB container: point reads for user sessions, complex analytical queries for reporting, and bulk write operations for data imports. Each operation type has different RU consumption patterns. How should they approach RU planning for this mixed workload?
Explanation
Different operation types have dramatically different RU consumption patterns, so accurate planning requires analyzing each type separately. Point reads typically consume 1 RU, complex queries can consume hundreds of RUs, and bulk writes consume 6+ RUs per KB plus additional overhead. The content shows examples of creating spreadsheets with different operation types, frequencies, and RU costs per operation. Average calculations mask important variations and can lead to under-provisioning during heavy query periods or over-provisioning during simple read periods. Using the highest RU rate for all operations leads to significant over-provisioning and cost waste. The most frequent operations might not be the most RU-intensive, so focusing only on frequency misses high-cost, low-frequency operations that could cause throttling.
5. TransactionProcessor Inc needs to design stored procedures that work with multiple documents transactionally for their financial trading system. They process trade orders that must update account balances, trade history, and compliance records atomically. If any part of the transaction fails, all changes must be rolled back. What stored procedure design should they implement?
Explanation
A single stored procedure operating on multiple documents within the same logical partition provides true ACID transaction guarantees in Azure Cosmos DB. All operations within the stored procedure execute atomically, with automatic rollback if any operation fails. Separate procedures with application coordination cannot provide atomic guarantees across multiple calls. Cross-partition transactions are not supported in Azure Cosmos DB stored procedures - they can only operate within a single logical partition. Event-driven architecture with eventual consistency doesn't meet the requirement for atomic updates in financial trading scenarios where immediate consistency is critical.
One-time access to this exam