This page was exported from Top Exam Collection [ http://blog.topexamcollection.com ] Export date:Sat Apr 5 20:59:02 2025 / +0000 GMT ___________________________________________________ Title: Latest 2024 Realistic Verified DP-420 Dumps - 100% Free DP-420 Exam Dumps [Q45-Q64] --------------------------------------------------- Latest 2024 Realistic Verified DP-420 Dumps - 100% Free DP-420 Exam Dumps Get 2024 Updated Free Microsoft DP-420 Exam Questions and Answer Microsoft DP-420 exam is designed for professionals who want to learn how to design and implement cloud-native applications using Microsoft Azure Cosmos DB. DP-420 exam is ideal for developers, architects, and IT professionals who have experience in building and deploying applications on Azure and want to deepen their knowledge of cloud-native application development. Passing the DP-420 exam demonstrates that you have the skills and knowledge needed to design and implement cloud-native applications using Azure Cosmos DB. Microsoft DP-420 exam, also known as "Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB," is a certification exam that focuses on designing and implementing cloud-native applications using Azure Cosmos DB. Azure Cosmos DB is Microsoft's globally distributed, multi-model database service designed for building highly scalable and available applications. The DP-420 exam is intended for candidates who are familiar with Azure and have experience developing, debugging, and maintaining cloud-native applications.   NO.45 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 a container named container1 in an Azure Cosmos DB Core (SQL) API account.You need to make the contents of container1 available as reference data for an Azure Stream Analytics job.Solution: You create an Azure function that uses Azure Cosmos DB Core (SQL) API change feed as a trigger and Azure event hub as the output.Does this meet the goal?  Yes  No The Azure Cosmos DB change feed is a mechanism to get a continuous and incremental feed of records from an Azure Cosmos container as those records are being created or modified. Change feed support works by listening to container for any changes. It then outputs the sorted list of documents that were changed in the order in which they were modified.The following diagram represents the data flow and components involved in the solution:Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/changefeed-ecommerce-solutionNO.46 You are designing a data model for an Azure Cosmos DB for NoSQL account.What are the partition limits for request units per second (RU/s) and storage? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point. Explanation:NO.47 The following is a sample of a document in orders.The orders container uses customerId as the partition key.You need to provide a report of the total items ordered per month by item type. The solution must meet the following requirements:Ensure that the report can run as quickly as possible.Minimize the consumption of request units (RUs).What should you do?  Configure the report to query orders by using a SQL query.  Configure the report to query a new aggregate container. Populate the aggregates by using the change feed.  Configure the report to query orders by using a SQL query through a dedicated gateway.  Configure the report to query a new aggregate container. Populate the aggregates by using SQL queries that run daily. You can facilitate aggregate data by using Change Feed and Azure Functions, and then use it for reporting.NO.48 You plan to store order data in Azure Cosmos DB for NoSQL account. The data contains information about orders and their associated items.You need to develop a model that supports order read operations. The solution must minimize the number or requests.  Create a single database that contains one container. Store orders and order items in separate documents in the container.  Create a single database that contains one container. Create a separate document for each order and embed the order items into the order documents.  Create a database for orders and a database for order items.  Create a single database that contains a container for order and a container for order items. ExplanationAzure Cosmos DB is a multi-model database that supports various data models, such as documents, key-value, graph, and column-family3. The core content-model of Cosmos DB’s database engine is based on atom-record-sequence (ARS), which allows it to store and query different types of data in a flexible and efficient way3.To develop a model that supports order read operations and minimizes the number of requests, you should consider the following factors:The size and shape of your dataThe frequency and complexity of your queriesThe latency and throughput requirements of your applicationThe trade-offs between storage efficiency and query performanceBased on these factors, one possible model that you could implement is B. Create a single database that contains one container. Create a separate document for each order and embed the order items into the order documents.This model has the following advantages:It stores orders and order items as self-contained documents that can be easily retrieved by order ID1.It avoids storing redundant data or creating additional containers for order items1.It allows you to view the order history of a customer with simple queries1.It leverages the benefits of embedding data, such as reducing the number of requests, improving query performance, and simplifying data consistency2.This model also has some limitations, such as:It may not be suitable for some order items that have data that is greater than 2 KB, as it could exceed the maximum document size limit of 2 MB2.It may not be optimal for scenarios where order items need to be queried independently from orders or aggregated by other criteria2.It may not support transactions across multiple orders or customers, as transactions are scoped to a single logical partition2.Depending on your specific use case and requirements, you may need to adjust this model or choose a different one. For example, you could use a hybrid data model that combines embedding and referencing data2, or you could use a graph data model that expresses entities and relationships as vertices and edges.NO.49 You have an Azure Cosmos DB for NoSQL account named account that has the disablekeyBasedletadatwriteAccess property enabled.You are developing an app named App1 that will be used by a use1 named DevUser1 to create containers in account1. DevUser1 has a non-privileged user account in the Azure AD tenant.You need to ensure that DevUser1 can use App1 to create containers in account1.What should you do? To answer, select the appropriate options in the answer area.NOTE Each correct selection is worth one point. ExplanationNO.50 You have an Azure Cosmos DB for NoSQL account.The change feed is enabled on a container named invoice.You create an Azure function that has a trigger on the change feed.What is received by the Azure function?  all the properties of the updated items  only the partition key and the changed properties of the updated items  all the properties of the original items and the updated items  only the changed properties and the system-defined properties of the updated items According to the Azure Cosmos DB documentation12, the change feed is a persistent record of changes to a container in the order they occur. The change feed outputs the sorted list of documents that were changed in the order in which they were modified.The Azure function that has a trigger on the change feed receives all the properties of the updated items2. The change feed does not include the original items or only the changed properties. The change feed also includes some system-defined properties such as _ts (the last modified timestamp) and _lsn (the logical sequence number)3.Therefore, the correct answer is:A: all the properties of the updated itemsNO.51 You have an Azure Cosmos DB Core (SQL) API account used by an application named App1.You open the Insights pane for the account and see the following chart.Use the drop-down menus to select the answer choice that answers each question based on the information presented in the graphic.NOTE: Each correct selection is worth one point. NO.52 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 DB SDK to implement the conflict resolution policy for a container. The solution must ensure that any conflict sent to the conflict feed.Solution: You set ConfilictResolutionMode to Custom. You Set ResolutionProcedures to a custom stored procedure. You configure the custom stored procedure to use the conflictingItems parameter to resolve conflict.Does this meet the goal?  Yes  No Setting ConflictResolutionMode to Custom and configuring a custom stored procedure with the “conflictingItems” parameter will allow you to implement a custom conflict resolution policy. This will ensure that any conflicts are sent to the conflict feed for resolution.NO.53 You have a container named container1 in an Azure Cosmos DB Core (SQL) API account.The following is a sample of a document in container1.{“studentId”: “631282”,“firstName”: “James”,“lastName”: “Smith”,“enrollmentYear”: 1990,“isActivelyEnrolled”: true,“address”: {“street”: “”,“city”: “”,“stateProvince”: “”,“postal”: “”,}}The container1 container has the following indexing policy.{“indexingMode”: “consistent”,“includePaths”: [{“path”: “/*”},{“path”: “/address/city/?”}],“excludePaths”: [{“path”: “/address/*”},{“path”: “/firstName/?”}]}For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point. Explanation:Box 1: Yes“path”: “/*” is in includePaths.Include the root path to selectively exclude paths that don’t need to be indexed. This is the recommended approach as it lets Azure Cosmos DB proactively index any new property that may be added to your model.Box 2: No“path”: “/firstName/?” is in excludePaths.Box 3: Yes“path”: “/address/city/?” is in includePathsReference: https://docs.microsoft.com/en-us/azure/cosmos-db/index-policyNO.54 You have three containers in an Azure Cosmos DB Core (SQL) API account as shown in the following table.You have the following Azure functions:A function named Fn1 that reads the change feed of cn1A function named Fn2 that reads the change feed of cn2A function named Fn3 that reads the change feed of cn3You perform the following actions:Delete an item named item1 from cn1.Update an item named item2 in cn2.For an item named item3 in cn3, update the item time to live to 3,600 seconds.For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point. Explanation:Box 1: NoAzure Cosmos DB’s change feed is a great choice as a central data store in event sourcing architectures where all data ingestion is modeled as writes (no updates or deletes).Note: The change feed does not capture deletes. If you delete an item from your container, it is also removed from the change feed. The most common method of handling this is adding a soft marker on the items that are being deleted. You can add a property called “deleted” and set it to “true” at the time of deletion. This document update will show up in the change feed. You can set a TTL on this item so that it can be automatically deleted later.Box 2: NoThe _etag format is internal and you should not take dependency on it, because it can change anytime.Box 3: YesChange feed support in Azure Cosmos DB works by listening to an Azure Cosmos container for any changes.Reference:https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-design-patternshttps://docs.microsoft.com/en-us/azure/cosmos-db/change-feedNO.55 You have an Azure Cosmos DB account named account1 that has a default consistency level of session.You have an app named App1.You need to ensure that the read operations of App1 can request either bounded staleness or consistent prefix consistency.What should you modify for each consistency level? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point. ExplanationBox 1 = The request level optionsAzure Cosmos DB offers five well-defined consistency levels: strong, bounded staleness, session, consistent prefix and eventual. You can configure the default consistency level on your Azure Cosmos DB account at any time2. The default consistency level applies to all databases and containers under that account1. You can also override the default consistency level for a specific request by using the request options2.Box 2 = The request level optionsTo modify the consistency level of a read operation in Azure Cosmos DB, you can use request-level options to override the account’s default consistency setting. Therefore, to ensure that the read operations of App1 can request either consistent prefix or session consistency, you need to modify the request-level options for each operation. Reference: – https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levelsNO.56 You have an Azure Cosmos DB Core (SQL) API account named storage1 that uses provisioned throughput capacity mode.The storage1 account contains the databases shown in the following table.The databases contain the containers shown in the following table.For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point. ExplanationBox 1: NoFour containers with 1000 RU/s each.Box 2: NoMax 8000 RU/s for db2. 8 containers, so 1000 RU/s for each container.Box 3: YesMax 8000 RU/s for db2. 8 containers, so 1000 RU/s for each container. Can very well add an additional container.Reference:https://docs.microsoft.com/en-us/azure/cosmos-db/plan-manage-costshttps://azure.microsoft.com/en-us/pricing/details/cosmos-db/NO.57 You have a database in an Azure Cosmos DB SQL API Core (SQL) account that is used for development.The database is modified once per day in a batch process.You need to ensure that you can restore the database if the last batch process fails. The solution must minimize costs.How should you configure the backup settings? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point. Explanation:NO.58 You have a database named db1in an Azure Cosmos DB for NoSQL account named account 1.You need to write JSON data to db1 by using Azure Stream Analytics. The solution must minimize costs.Which should you do before you can use db1 as an output of Stream Analytics?  in account, add a private endpoint.  In db1, create containers that have a custom indexing policy and analytical store disabled.  In account, enable a dedicated gateway.  In db1, create containers that have an automatic indexing policy and analytical store enabled. NO.59 You have an Azure Cosmos DB Core (SQL) API account named account1 that has the disableKeyBasedMetadataWriteAccess property enabled.You are developing an app named App1 that will be used by a user named DevUser1 to create containers in account1. DevUser1 has a non-privileged user account in the Azure Active Directory (Azure AD) tenant.You need to ensure that DevUser1 can use App1 to create containers in account1.What should you do? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point. Explanation:Box 1: Resource tokensResource tokens provide access to the application resources within a database. Resource tokens:Provide access to specific containers, partition keys, documents, attachments, stored procedures, triggers, and UDFs.Box 2: Azure Resource Manager APIYou can use Azure Resource Manager to help deploy and manage your Azure Cosmos DB accounts, databases, and containers.Reference:https://docs.microsoft.com/en-us/azure/cosmos-db/secure-access-to-datahttps://docs.microsoft.com/en-us/rest/api/resources/NO.60 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 a container named container1 in an Azure Cosmos DB Core (SQL) API account.You need to make the contents of container1 available as reference data for an Azure Stream Analytics job.Solution: You create an Azure Data Factory pipeline that uses Azure Cosmos DB Core (SQL) API as the input and Azure Blob Storage as the output.Does this meet the goal?  Yes  No Instead create an Azure function that uses Azure Cosmos DB Core (SQL) API change feed as a trigger and Azure event hub as the output.The Azure Cosmos DB change feed is a mechanism to get a continuous and incremental feed of records from an Azure Cosmos container as those records are being created or modified. Change feed support works by listening to container for any changes. It then outputs the sorted list of documents that were changed in the order in which they were modified.The following diagram represents the data flow and components involved in the solution:Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/changefeed-ecommerce-solutionNO.61 You have an Azure Cosmos DB for NoSQL account that has multiple write regions.You need to receive an alert when requests that target the database exceed the available request units per second (RU/s).Which Azure Monitor signal should you use?  Region Removed  Provisioned Throughput  Metadata Requests  Data Usage Azure Monitor is a service that provides comprehensive monitoring for Azure resources, including Azure Cosmos DB. You can use Azure Monitor to collect, analyze, and alert on metrics and logs from your Azure Cosmos DB account. You can create alerts for Azure Cosmos DB using Azure Monitor based on the metrics, activity log events, or Log Analytics logs on your account1.For your scenario, if you want to receive an alert when requests that target the database exceed the available request units per second (RU/s), you should use the Document Quota metric. This metric measures the percentage of RU/s consumed by your account or container. You can create an alert rule on this metric from the Azure portal by following these steps2:In the Azure portal, select the Azure Cosmos DB account you want to monitor.Under the Monitoring section of the sidebar, select Alerts, and then select New alert rule.In the Create alert rule pane, fill out the Scope section by selecting your subscription name and resource type (Azure Cosmos DB accounts).In the Condition section, select Add condition and choose Document Quota from the list of signals.In the Configure signal logic pane, specify the threshold value and operator for your alert condition. For example, you can choose Greater than or equal to 90 as the threshold value and operator to receive an alert when your RU/s consumption reaches 90% or more of your provisioned throughput.In the Alert rule details section, specify a name and description for your alert rule.In the Actions section, select Add action group and choose how you want to receive notifications for your alert. For example, you can choose Email/SMS/Push/Voice as an action type and enter your email address or phone number as a receiver.Review your alert rule settings and select Create alert rule to save it.NO.62 You plan to create an Azure Cosmos DB container named account that will contain items in the following format.You need to define a query that will return the ids of all accounts that have ever recorded a negative value for balance.How should you complete the query? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point. ExplanationNO.63 You maintain a relational database for a book publisher. The database contains the following tables.The most common query lists the books for a given authorId.You need to develop a non-relational data model for Azure Cosmos DB Core (SQL) API that will replace the relational database. The solution must minimize latency and read operation costs.What should you include in the solution?  Create a container for Author and a container for Book. In each Author document, embed bookId for each book by the author. In each Book document embed authorId of each author.  Create Author, Book, and Bookauthorlnk documents in the same container.  Create a container that contains a document for each Author and a document for each Book. In each Book document, embed authorId.  Create a container for Author and a container for Book. In each Author document and Book document embed the data from Bookauthorlnk. ExplanationStore multiple entity types in the same container.NO.64 You have an Azure Cosmos DB for NoSQL account named account1 that supports an application named App1. App1 uses the consistent prefix consistency level.You configure account1 to use a dedicated gateway and integrated cache.You need to ensure that App1 can use the integrated cache.Which two actions should you perform for APP1? Each correct answer presents part of the solution.NOTE: Each correct selection is worth one point.  Change the connection mode to direct  Change the account endpoint to https://account1.sqlx.cosmos.azure.com.  Change the consistency level of requests to strong.  Change the consistency level of requests to session.  Change the account endpoint to https://account1.documents.azure.com the Azure Cosmos DB integrated cache is an in-memory cache that is built-in to the Azure Cosmos DB dedicated gateway. The dedicated gateway is a front-end compute that stores cached data and routes requests to the backend database. You can choose from a variety of dedicated gateway sizes based on the number of cores and memory needed for your workload1. The integrated cache can reduce the RU consumption and latency of read operations by serving them from the cache instead of the backend containers2.For your scenario, to ensure that App1 can use the integrated cache, you should perform these two actions:Change the account endpoint to https://account1.sqlx.cosmos.azure.com. This is the dedicated gateway endpoint that you need to use to connect to your Azure Cosmos DB account and leverage the integrated cache. The standard gateway endpoint (https://account1.documents.azure.com) will not use the integrated cache2.Change the consistency level of requests to session. This is the highest consistency level that is supported by the integrated cache. If you use a higher consistency level (such as strong or bounded staleness), your requests will bypass the integrated cache and go directly to the backend containers Loading … DP-420 Dumps PDF and Test Engine Exam Questions: https://www.topexamcollection.com/DP-420-vce-collection.html --------------------------------------------------- Images: https://blog.topexamcollection.com/wp-content/plugins/watu/loading.gif https://blog.topexamcollection.com/wp-content/plugins/watu/loading.gif --------------------------------------------------- --------------------------------------------------- Post date: 2024-10-03 14:39:44 Post date GMT: 2024-10-03 14:39:44 Post modified date: 2024-10-03 14:39:44 Post modified date GMT: 2024-10-03 14:39:44