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.
Answer(s): C
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.
https://docs.microsoft.com/en-us/azure/cosmos-db/sql/how-to-use-stored-procedures-triggers-udfs
HOTSPOT (Drag and Drop is not supported).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.Hot Area:
Answer(s): A
Box 1: ConsistencyLevelThe ItemRequestOptions Class ConsistencyLevel property gets or sets the consistency level required for the request in the Azure Cosmos DB service.Azure Cosmos DB offers 5 different consistency levels. Strong, Bounded Staleness, Session, Consistent Pre x and Eventual - in order of strongest to weakest consistency.Box 2: _etagThe ItemRequestOptions class helped us implement optimistic concurrency by specifying that we wanted the SDK to use the If-Match header to allow the server to decide whether a resource should be updated. The If-Match value is the ETag value to be checked against. If the ETag value matches the server ETag value, the resource is updated.
https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.itemrequestoptions https://cosmosdb.github.io/labs/dotnet/labs/10- concurrency-control.html
HOTSPOT (Drag and Drop is not supported).You are creating a database in an Azure Cosmos DB Core (SQL) API account. The database will be used by an application that will provide users with the ability to share online posts. Users will also be able to submit comments on other users' posts.You need to store the data shown in the following table.The application has the following characteristics:Users can submit an unlimited number of posts.The average number of posts submitted by a user will be more than 1,000.Posts can have an unlimited number of comments from different users.The average number of comments per post will be 100, but many posts will exceed 1,000 comments.Users will be limited to having a maximum of 20 interests.For each of the following statements, select Yes if the statement is true. Otherwise, select No.NOTE: Each correct selection is worth one point.Hot Area:
Box 1: YesNon-relational data increases write costs, but can decrease read costs.Box 2: YesNon-relational data increases write costs, but can decrease read costs.Box 3: NoNon-relational data increases write costs, but can decrease read costs.
DRAG DROP (Drag and Drop is not supported).You have an app that stores data in an Azure Cosmos DB Core (SQL) API account The app performs queries that return large result sets. You need to return a complete result set to the app by using pagination. Each page of results must return 80 items. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.Select and Place:
Step 1: Con gure the MaxItemCount in QueryRequestOptionsYou can specify the maximum number of items returned by a query by setting the MaxItemCount. The MaxItemCount is speci ed per request and tells the query engine to return that number of items or fewer.Box 2: Run the query and provide a continuation tokenIn the .NET SDK and Java SDK you can optionally use continuation tokens as a bookmark for your query's progress. Azure Cosmos DB query executions are stateless at the server side and can be resumed at any time using the continuation token. If the query returns a continuation token, then there are additional query results.Step 3: Append the results to a variable
https://docs.microsoft.com/en-us/azure/cosmos-db/sql/sql-query-pagination
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 speci c value.Solution: You con gure an Azure Monitor alert to trigger the function.Does this meet the goal?
You can set up alerts from the Azure Cosmos DB pane or the Azure Monitor service in the Azure portal.Note: Alerts are used to set up recurring tests to monitor the availability and responsiveness of your Azure Cosmos DB resources. Alerts can send you a noti cation in the form of an email, or execute an Azure Function when one of your metrics reaches the threshold or if a speci c event is logged in the activity log.
https://docs.microsoft.com/en-us/azure/cosmos-db/create-alerts
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 speci c value.Solution: You con gure the function to have an Azure CosmosDB trigger.Does this meet the goal?
Answer(s): B
Instead con gure 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.
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 speci c value. Solution: You con gure an application to use the change feed processor to read the change feed and you con gure the application to trigger the function.Does this meet the goal?
You have a database named db1 in an Azure Cosmos DB Core (SQL) API account.You are designing an application that will use db1.In db1, you are creating a new container named coll1 that will store online orders.The following is a sample of a document that will be stored in coll1.The application will have the following characteristics:New orders will be created frequently by different customers.Customers will often view their past order history.You need to select the partition key value for coll1 to support the application. The solution must minimize costs.To what should you set the partition key?
If most of your workload's requests are queries and most of your queries have an equality lter on the same property, this property can be a good partition key choice. For example, if you frequently run a query that lters on UserID, then selecting UserID as the partition key would reduce the number of cross-partition queries.
https://docs.microsoft.com/en-us/azure/cosmos-db/partitioning-overview
Share your comments for Microsoft DP-420 exam with other users:
explanations for the answers are to the point.
how can rea next
question: 128 d is the wrong answer...should be c
thanks for az 700 dumps
thank you for this tableau dumps . it will helpfull for tableau certification
good content
just testing if the comments are real
very helpful for exam preparation
question 11: https://help.salesforce.com/s/articleview?id=sf.admin_lead_to_patient_setup_overview.htm&type=5
i think the answer to question 42 is b not c
thanks for the dump
fantastic assessments
i find the xengine test engine simulator to be more fun than reading from pdf.
nice document
thank you for making the questions and answers intractive and selectable.
answers are correct?
can i belive this dump
great site to practice for sitecore exam
good for students
nice practice dumps
nokia 4a0-114 dumps
great content and wonderful to have the answers with explanation
for question #118, the answer is option c. the screen shot is showing the drop down, but the answer is marked incorrectly please update . thanks for sharing such nice questions.
the correct answer for the question 29 is d.
question no 22: correct answers: bc, 1 per session 1 per page 1 per component always
these are pretty useful
awesome
yes please upload
great job whoever put this together, for the greater good! thanks!
just started to view all questions for the exam
helpful material
hope for the best
will post exam has finished
really correct and good analyze!