[Nov 14, 2023] DP-420 Exam Dumps PDF Guaranteed Success with Accurate & Updated Questions
Pass DP-420 Exam - Real Test Engine PDF with 113 Questions
The DP-420 exam is intended for solution architects, developers, and database administrators who have experience working with Azure Cosmos DB and want to showcase their skills in designing and implementing cloud-native applications using this technology. Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB certification exam tests the candidate's ability to design and implement containers, partitions, and indexes in Azure Cosmos DB to optimize performance, scalability, and cost.
Microsoft DP-420 (Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB) Exam is a certification exam that validates the skills and knowledge of developers in designing and implementing cloud-native applications using Microsoft Azure Cosmos DB. DP-420 exam is intended for individuals who have experience in developing and deploying applications on Microsoft Azure and are looking to enhance their skills in designing and implementing cloud-native applications using Cosmos DB.
The DP-420 certification exam consists of multiple-choice questions that cover a range of topics related to designing and implementing cloud-native applications using Azure Cosmos DB. Candidates will be tested on their ability to design containers and partitions, implement data modeling best practices, optimize query performance, and configure and manage Azure Cosmos DB instances.
NEW QUESTION # 59
You have an Azure Cosmos DB Core (SQL) API account named account1.
In account1, you run the following query in a container that contains 100GB of data.
SELECT *
FROM c
WHERE LOWER(c.categoryid) = "hockey"
You view the following metrics while performing the query.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation
Box 1: No
Each physical partition should have its own index, but since no index is used, the query is not cross-partition.
Box 2: No
Index utilization is 0% and Index Look up time is also zero.
Box 3: Yes
A partition key index will be created, and the query will perform across the partitions.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/how-to-query-container
NEW QUESTION # 60
You have an Azure Cosmos DB for NoSQL account named account1 that has a single read-write region and one additional read region. Account1 uses the strong default consistency level.
You have an application that uses the eventual consistency level when submitting requests to account1.
How will writes from the application be handled?
- A. Azure Cosmos DB will reject writes from the application.
- B. Writes will use the eventual consistency level.
- C. The write order is not guaranteed during replication.
- D. Writes will use the strong consistency level.
Answer: D
Explanation:
This is because the write concern is mapped to the default consistency level configured on your Azure Cosmos DB account, which is strong in this case. Strong consistency ensures that every write operation is synchronously committed to every region associated with your Azure Cosmos DB account. The eventual consistency level that the application uses only applies to the read operations. Eventual consistency offers higher availability and better performance, but it does not guarantee the order or latency of the reads.
NEW QUESTION # 61
You have a database named db1 in an Azure Cosmos DB f You have a third-party application that is exposed thro You need to migrate data from the application to a What should you use?
- A. Database Migration Assistant
- B. Azure Migrate
- C. Azure Data Factory
Answer: C
Explanation:
you can migrate data from various data sources to Azure Cosmos DB using different tools and methods. The choice of the migration tool depends on factors such as the data source, the Azure Cosmos DB API, the size of data, and the expected migration duration1. Some of the common migration tools are:
Azure Cosmos DB Data Migration tool: This is an open source tool that can import data to Azure Cosmos DB from sources such as JSON files, MongoDB, SQL Server, CSV files, and Azure Cosmos DB collections. This tool supports the SQL API and the Table API of Azure Cosmos DB2.
Azure Data Factory: This is a cloud-based data integration service that can copy data from various sources to Azure Cosmos DB using connectors. This tool supports the SQL API, MongoDB API, Cassandra API, Gremlin API, and Table API of Azure Cosmos DB3.
Azure Cosmos DB live data migrator: This is a command-line tool that can migrate data from one Azure Cosmos DB container to another container within the same or different account. This tool supports live migration with minimal downtime and works with any Azure Cosmos DB API4.
For your scenario, if you want to migrate data from a third-party application that is exposed through an OData endpoint to a container in Azure Cosmos DB for NoSQL, you should use Azure Data Factory. Azure Data Factory has an OData connector that can read data from an OData source and write it to an Azure Cosmos DB sink using the SQL API5. You can create a copy activity in Azure Data Factory that specifies the OData source and the Azure Cosmos DB sink, and run it on demand or on a schedule.
NEW QUESTION # 62
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?
- A. Create a container for Author and a container for Book. In each Author document, embed booked for each book by the author. In each Book document embed author of each author.
- B. Create a container that contains a document for each Author and a document for each Book. In each Book document, embed authorId.
- C. Create a container for Author and a container for Book. In each Author document and Book document embed the data from Bookauthorlnk.
- D. Create Author, Book, and Bookauthorlnk documents in the same container.
Answer: A
Explanation:
Explanation
Store multiple entity types in the same container.
NEW QUESTION # 63
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.
Answer:
Explanation:
NEW QUESTION # 64
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.
Answer:
Explanation:
NEW QUESTION # 65
You have a container in an Azure Cosmos DB Core (SQL) API account.
You need to use the Azure Cosmos DB SDK to replace a document by using optimistic concurrency.
What should you include in the code? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Reference:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.itemrequestoptions
https://cosmosdb.github.io/labs/dotnet/labs/10-concurrency-control.html
NEW QUESTION # 66
You have an application named App1 that reads the data in an Azure Cosmos DB Core (SQL) API account.
App1 runs the same read queries every minute. The default consistency level for the account is set to eventual.
You discover that every query consumes request units (RUs) instead of using the cache.
You verify the IntegratedCacheiteItemHitRate metric and the IntegratedCacheQueryHitRate metric. Both metrics have values of 0.
You verify that the dedicated gateway cluster is provisioned and used in the connection string.
You need to ensure that App1 uses the Azure Cosmos DB integrated cache.
What should you configure?
- A. the default consistency level of the Azure Cosmos DB account
- B. the indexing policy of the Azure Cosmos DB container
- C. the connectivity mode of the App1 CosmosClient
- D. the consistency level of the requests from App1
Answer: C
Explanation:
Explanation
Because the integrated cache is specific to your Azure Cosmos DB account and requires significant CPU and memory, it requires a dedicated gateway node. Connect to Azure Cosmos DB using gateway mode.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/integrated-cache-faq
NEW QUESTION # 67
You configure multi-region writes for account1.
You need to ensure that App1 supports the new configuration for account1. The solution must meet the business requirements and the product catalog requirements.
What should you do?
- A. Set the default consistency level of accountl to bounded staleness.
- B. Increase the number of request units per second (RU/s) allocated to the con-product and con-productVendor containers.
- C. Create a private endpoint connection.
- D. Modify the connection policy of App1.
Answer: B
Explanation:
Explanation
App1 queries the con-product and con-productVendor containers.
Note: Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.
Scenario:
Develop an app named App1 that will run from all locations and query the data in account1.
Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
Whenever there are multiple solutions for a requirement, select the solution that provides the best performance, as long as there are no additional costs associated.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
NEW QUESTION # 68
You need to create a database in an Azure Cosmos DB for NoSQL account. The database will contain three containers named coll1, coll2 and coll3. The coll1 container will have unpredictable read and write volumes. The col!2 and coll3 containers will have predictable read and write volumes. The expected maximum throughput for coll1 and coll2 is 50,000 request units per second (RU/s) each.
How should you provision the collection while minimizing costs?
- A. Create a serverless account.
- B. Create a provisioned throughput account. Set the throughput for coll1 to Manual. Set the throughput for coll2 and coll3 to Autoscale.
- C. Create a provisioned throughput account. Set the throughput for call1 to Autoscale. Set the throughput for call2 and coll3 to Manual.
Answer: C
Explanation:
Azure Cosmos DB offers two different capacity modes: provisioned throughput and serverless1. Provisioned throughput mode allows you to configure a certain amount of throughput (expressed in Request Units per second or RU/s) that is provisioned on your databases and containers. You get billed for the amount of throughput you've provisioned, regardless of how many RUs were consumed1. Serverless mode allows you to run your database operations without having to configure any previously provisioned capacity. You get billed for the number of RUs that were consumed by your database operations and the storage consumed by your data1.
To create a database that minimizes costs, you should consider the following factors:
The read and write volumes of your containers
The predictability and variability of your traffic
The latency and throughput requirements of your application
The geo-distribution and availability needs of your data
Based on these factors, one possible option that you could choose is B. Create a provisioned throughput account. Set the throughput for coll1 to Autoscale. Set the throughput for coll2 and coll3 to Manual.
This option has the following advantages:
It allows you to handle unpredictable read and write volumes for coll1 by using Autoscale, which automatically adjusts the provisioned throughput based on the current load1.
It allows you to handle predictable read and write volumes for coll2 and coll3 by using Manual, which lets you specify a fixed amount of provisioned throughput that meets your performance needs1.
It allows you to optimize your costs by paying only for the throughput you need for each container1.
It allows you to enable geo-distribution for your account if you need to replicate your data across multiple regions1.
This option also has some limitations, such as:
It may not be suitable for scenarios where all containers have intermittent or bursty traffic that is hard to forecast or has a low average-to-peak ratio1.
It may not be optimal for scenarios where all containers have low or sporadic traffic that does not justify provisioned capacity1.
It may not support availability zones or multi-master replication for your account1.
Depending on your specific use case and requirements, you may need to choose a different option. For example, you could use a serverless account if all containers have low or sporadic traffic that does not require predictable performance or geo-distribution1. Alternatively, you could use a provisioned throughput account with Manual for all containers if all containers have stable and consistent traffic that requires predictable performance or geo-distribution1.
NEW QUESTION # 69
You need to configure an Apache Kafka instance to ingest data from an Azure Cosmos DB Core (SQL) API account. The data from a container named telemetry must be added to a Kafka topic named iot. The solution must store the data in a compact binary format.
Which three configuration items should you include in the solution? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
- A. "connect.cosmos.containers.topicmap": "iot"
- B. "connector.class": "com.azure.cosmos.kafka.connect.source.CosmosDBSinkConnector"
- C. "key.converter": "org.apache.kafka.connect.json.JsonConverter"
- D. "key.converter": "io.confluent.connect.avro.AvroConverter"
- E. "connect.cosmos.containers.topicmap": "iot#telemetry"
- F. "connector.class": "com.azure.cosmos.kafka.connect.source.CosmosDBSourceConnector"
Answer: B,D,E
Explanation:
Explanation
C: Avro is binary format, while JSON is text.
F: Kafka Connect for Azure Cosmos DB is a connector to read from and write data to Azure Cosmos DB. The Azure Cosmos DB sink connector allows you to export data from Apache Kafka topics to an Azure Cosmos DB database. The connector polls data from Kafka to write to containers in the database based on the topics subscription.
D: Create the Azure Cosmos DB sink connector in Kafka Connect. The following JSON body defines config for the sink connector.
Extract:
"connector.class": "com.azure.cosmos.kafka.connect.sink.CosmosDBSinkConnector",
"key.converter": "org.apache.kafka.connect.json.AvroConverter"
"connect.cosmos.containers.topicmap": "hotels#kafka"
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/sql/kafka-connector-sink
https://www.confluent.io/blog/kafka-connect-deep-dive-converters-serialization-explained/
NEW QUESTION # 70
You have an Azure Cosmos DB for NoSQL container named Contacts that is configured as shown in the following exhibit.
Contacts contains the items shown in the following table.
To Contacts, you plan to insert the items 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.
Answer:
Explanation:
NEW QUESTION # 71
You have a container named container1 in an Azure Cosmos DB Core (SQL) API account. The container1 container has 120 GB of data.
The following is a sample of a document in container1.
The orderId property is used as the partition key.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
NEW QUESTION # 72
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.
Answer:
Explanation:
Explanation
Box 1: incorrect connection URLs
400 Bad Request: Returned when there is an error in the request URI, headers, or body. The response body will contain an error message explaining what the specific problem is.
The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing).
Box 2: 6 thousand
201 Created: Success on PUT or POST. Object created or updated successfully.
Note:
200 OK: Success on GET, PUT, or POST. Returned for a successful response.
404 Not Found: Returned when a resource does not exist on the server. If you are managing or querying an index, check the syntax and verify the index name is specified correctly.
Reference: https://docs.microsoft.com/en-us/rest/api/searchservice/http-status-codes
NEW QUESTION # 73
You have an Azure Cosmos DB for NoSQL account.
You plan 10 create a container named container1. The container1 container will store items that include two properties named nm and age The most commonly executed queries will query container1 for a specific name. The following is a sample of the query.
You need to define an opt-in Indexing policy for container1. The solution must meet the following requirements:
* Minimize the number of request units consumed by the queries.
* Ensure that the _etag property is excluded from indexing.
How should you define the indexing poky? To answer, select the appropriate options in the answer are a. NOTE: Each correct selection Is worth one point.
Answer:
Explanation:
NEW QUESTION # 74
You have an Azure Cosmos DB for NoSQL account.
You plan 10 create a container named container1. The container1 container will store items that include two properties named nm and age The most commonly executed queries will query container1 for a specific name. The following is a sample of the query.
You need to define an opt-in Indexing policy for container1. The solution must meet the following requirements:
* Minimize the number of request units consumed by the queries.
* Ensure that the _etag property is excluded from indexing.
How should you define the indexing poky? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection Is worth one point.
Answer:
Explanation:
Explanation
NEW QUESTION # 75
You have a database named db1 in an Azure Cosmos DB f You have a third-party application that is exposed thro You need to migrate data from the application to a What should you use?
- A. Database Migration Assistant
- B. Azure Migrate
- C. Azure Data Factory
Answer: C
Explanation:
Explanation
you can migrate data from various data sources to Azure Cosmos DB using different tools and methods. The choice of the migration tool depends on factors such as the data source, the Azure Cosmos DB API, the size of data, and the expected migration duration . Some of the common migration tools are:
* Azure Cosmos DB Data Migration tool: This is an open source tool that can import data to Azure Cosmos DB from sources such as JSON files, MongoDB, SQL Server, CSV files, and Azure Cosmos DB collections. This tool supports the SQL API and the Table API of Azure Cosmos DB2.
* Azure Data Factory: This is a cloud-based data integration service that can copy data from various sources to Azure Cosmos DB using connectors. This tool supports the SQL API, MongoDB API, Cassandra API, Gremlin API, and Table API of Azure Cosmos DB
* Azure Cosmos DB live data migrator: This is a command-line tool that can migrate data from one Azure Cosmos DB container to another container within the same or different account. This tool supports live migration with minimal downtime and works with any Azure Cosmos DB API4.
For your scenario, if you want to migrate data from a third-party application that is exposed through an OData endpoint to a container in Azure Cosmos DB for NoSQL, you should use Azure Data Factory. Azure Data Factory has an OData connector that can read data from an OData source and write it to an Azure Cosmos DB sink using the SQL API5. You can create a copy activity in Azure Data Factory that specifies the OData source and the Azure Cosmos DB sink, and run it on demand or on a schedule.
NEW QUESTION # 76
You have an Azure Cosmos DB account named account1.
You have several apps that connect to account1 by using the account's secondary key.
You then configure the apps to authenticate by using service principals.
You need to ensure that account1 will only allow apps to connect by using an Azure AD identity.
Which account property should you modify?
- A. disableLocalAuth
- B. userAssignedldentatxe
- C. disableKeyBasedMetadataWriteAccess ,
- D. allowedOrxgins
Answer: A
Explanation:
The disableLocalAuth property is a boolean flag that indicates whether local authentication methods such as primary/secondary keys are disabled for the Azure Cosmos DB account. Setting this property to true improves security by ensuring that Azure Cosmos DB accounts exclusively require Azure Active Directory identities for authentication1.
NEW QUESTION # 77
You need to implement a trigger in Azure Cosmos DB Core (SQL) API that will run before an item is inserted into a container.
Which two actions should you perform to ensure that the trigger runs? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
- A. For each create request, set the trigger name in RequestOptions.
- B. Append pre to the name of the JavaScript function trigger.
- C. Register the trigger as a pre-trigger.
- D. For each create request, set the access condition in RequestOptions.
- E. For each create request, set the consistency level to session in RequestOptions.
Answer: B,C
Explanation:
C: When triggers are registered, you can specify the operations that it can run with.
F: When executing, pre-triggers are passed in the RequestOptions object by specifying PreTriggerInclude and then passing the name of the trigger in a List object.
NEW QUESTION # 78
The following is a sample of a document in orders.
The orders container uses customer 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?
- A. Configure the report to query orders by using a SQL query.
- B. Configure the report to query a new aggregate container. Populate the aggregates by using SQL queries that run daily.
- C. Configure the report to query a new aggregate container. Populate the aggregates by using the change feed.
- D. Configure the report to query orders by using a SQL query through a dedicated gateway.
Answer: B
Explanation:
Explanation
You can facilitate aggregate data by using Change Feed and Azure Functions, and then use it for reporting.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed
NEW QUESTION # 79
......
Get New DP-420 Certification Practice Test Questions Exam Dumps: https://www.actualpdf.com/DP-420_exam-dumps.html
Real DP-420 Exam Dumps Questions Valid DP-420 Dumps PDF: https://drive.google.com/open?id=1X-c9gS4VCf0nYQ6ahhbLooBJVNAapMAV
