Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
You have an Azure Cosmos DB for NoSQL account that contains a container named customers.
You have an application named App1 that caches customers and must be notified when the list of customers changes.
You implement a change feed. The Time to Live settings have the default values.
You discover the following:
* Notifications for INSERT and UPDATE operations are received within 10 seconds.
* Notifications for DELETE operations are NOT received.
Which two actions should you perform to ensure that App1 receives notifications for DELETE operations? Each correct answer present part of the solution.
NOTE: Each correct selection is worth one point.
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure Cosmos DB Core (SQL) API account named account 1 that uses autoscale throughput.
You need to run an Azure function when the normalized request units per second for a container in account1 exceeds a specific value.
Solution: You configure an application to use the change feed processor to read the change feed and you configure the application to trigger the function.
Does this meet the goal?
Instead configure an Azure Monitor alert to trigger the function.
You can set up alerts from the Azure Cosmos DB pane or the Azure Monitor service in the Azure portal.
You have an Azure Cosmos DB for NoSQL account that uses a custom conflict resolution policy. The account has a registered merge procedure that throws a runtime exception. The runtime exception prevents conflicts from being resolved.
You need to use an Azure function to resolve the conflicts. What should you use?
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result1 these questions will not appear in the review screen.
You have a database in an Azure Cosmos DB for NoSQL account that is configured for multi-region writes.
You need to use the Azure Cosmos OB SDK to implement the conflict resolution policy for a container. The solution must ensure that any conflicts are sent to the conflicts feed.
Solution: You set ConflictResolutionMode to Laswriterwins and you use the default settings for the policy.
Does this meet the goal?
You have a container named container1 in an Azure Cosmos DB Core (SQL) API account. Upserts of items in container1 occur every three seconds.
You have an Azure Functions app named function1 that is supposed to run whenever items are inserted or replaced in container1.
You discover that function1 runs, but not on every upsert.
You need to ensure that function1 processes each upsert within one second of the upsert.
Which property should you change in the Function.json file of function1?
With an upsert operation we can either insert or update an existing record at the same time.
FeedPollDelay: The time (in milliseconds) for the delay between polling a partition for new changes on the feed, after all current changes are drained. Default is 5,000 milliseconds, or 5 seconds.
Incorrect Answers:
A: checkpointInterval: When set, it defines, in milliseconds, the interval between lease checkpoints. Default is always after each Function call.
C: maxItemsPerInvocation: When set, this property sets the maximum number of items received per Function call. If operations in the monitored collection are performed through stored procedures, transaction scope is preserved when reading items from the change feed. As a result, the number of items received could be higher than the specified value so that the items changed by the same transaction are returned as part of one atomic batch.
You need to identify which connectivity mode to use when implementing App2. The solution must support the planned changes and meet the business requirements.
Which connectivity mode should you identify?
Scenario: Develop an app named App2 that will run from the retail stores and query the data in account2. App2 must be limited to a single DNS endpoint when accessing account2.
By using Azure Private Link, you can connect to an Azure Cosmos account via a private endpoint. The private endpoint is a set of private IP addresses in a subnet within your virtual network.
When you're using Private Link with an Azure Cosmos account through a direct mode connection, you can use only the TCP protocol. The HTTP protocol is not currently supported.
https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-configure-private-endpoints
You have an Azure Cosmos DB database that hosts a container named container1.
You need to ensure that the items stored in contained will NOT expire unless their TTL value is set explicitly. What should you do?
Exam domains verified against: Official Microsoft DP-420 exam guide, last checked October 2026.
Evaluate resource models and SDK solutions; Evaluate consistency levels; Evaluate Request Unit (RU) consumption requirements; Evaluating and configuring appropriate throughput; Configure account-level and container-level settings; Create and manage database and containers; Initialize SDK clients and connections; Implement database operations; Implement queries, parameterized queries, paging, and continuation tokens; Implement point read operations; Implement create, replace, update, patch and delete operations; Implement bulk, batch, and transactional operations; Configure Time to Live (TTL); Implement concurrency control mechanisms; Design and implement data models and partitioning strategies; Design data models for access patterns and operational requirements; Design and select partition keys based on cardinality, access patterns, and write distribution requirements; Determine when to embed or reference related data; Evaluate the impact of partition key selection on scalability and performance; Implement hierarchical partition keys (HPKs) and multi-tenant partitioning strategies; Implement synthetic partition keys; Identify partitioning anti-patterns and partitioning issues during solution reviews; Estimate workload cost requirements; Implement change feed; Implement change feed operations; Differentiate between change feed processor and pull mode models; Configure lease containers; Implement change feed processing using latest mode or all versions and delete; Implement copy container jobs; Design and implement Azure Cosmos DB solutions by using AI-assisted tools; Implement Agent Kit to follow Azure Cosmos DB development recommended solutions; Implement Agent Kit to accelerate AI application development
Implement database security controls; Configure authentication mechanisms; Configure authorization controls; Configure network security; Configure dynamic data masking; Implement availability and recovery solutions; Configure backup and restore solutions; Implement multi-region read and write configurations; Configure partition failover solutions; Optimize and remediate database performance; Optimize query performance; Analyze query performance metrics; Analyze index performance metrics; Monitor end-to-end latency against service objectives; Configure Azure Monitor alerts; Analyze diagnostic logs in Log Analytics; Implement Fleet management and monitoring across multiple accounts and subscriptions; Configure Fleet level throughput management; Configure Fleet monitoring with fleet analytics
Design and implement AI retrieval; Design and implement full-text search; Design for vector data, including vector data type, vector indexes, and size; Design and implement vector partitioning and sharded DiskANN implementations; Implement vector search; Design and implement hybrid search; Optimize full-text and vector performance; Design and implement Retrieval-Augmented Generation (RAG); Design and implement agent memory stores; Design durable memory stores; Implement conversation state; Implement semantic memory; Design and implement operational analytics on Azure Cosmos DB; Choose between Azure Cosmos DB and Cosmos DB in Microsoft Fabric; Configure and monitor data mirroring into Microsoft Fabric; Query Azure Cosmos DB mirrored JSON data in Microsoft Fabric with T-SQL and Spark; Read and write data into Azure Cosmos DB from Microsoft Fabric with Cosmos DB Spark connector
Common questions about the exam itself