Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. DP-420

Free DP-420 Exam Braindumps (page: 8)

Page 7 of 23
PDF with 175 Questions

HOTSPOT (Drag and Drop is not supported).
You provision Azure resources by using the following Azure Resource Manager (ARM) template.



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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: No
An alert is triggered when the DB key is regenerated, not when it is used.
Note: The az cosmosdb keys regenerate command regenerates an access key for a Azure Cosmos DB database account.

Box 2: No
Only an SMS action will be taken.
Emailreceivers is empty so no email action is taken.

Box 3: Yes
Yes, an alert is triggered when the DB key is regenerated.


Reference:

https://docs.microsoft.com/en-us/cli/azure/cosmosdb/keys



You plan to store order data in an Azure Cosmos DB Core (SQL) API 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 of requests.
What should you do?

  1. Create a database for orders and a database for order items.
  2. Create a single database that contains a container for orders and a container for order items.
  3. Create a single database that contains one container. Store orders and order items in separate documents in the container.
  4. Create a single database that contains one container. Create a separate document for each order and embed the order items into the order documents.

Answer(s): D

Explanation:

By denormalizing data, your application may need to issue fewer queries and updates to complete common operations.
Typically denormalized data models provide better read performance.
Note: In general, use embedded data models when:
There are contained relationships between entities.
There are one-to-few relationships between entities.
There's embedded data that changes infrequently.
There's embedded data that will not grow without bound.
There's embedded data that is queried frequently together.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/modeling-data



You have a container in an Azure Cosmos DB Core (SQL) API account. The container stores telemetry data from IoT devices. The container uses telemetryId as the partition key and has a throughput of 1,000 request units per second (RU/s). Approximately 5,000 IoT devices submit data every ve minutes by using the same telemetryId value.
You have an application that performs analytics on the data and frequently reads telemetry data for a single IoT device to perform trend analysis.
The following is a sample of a document in the container.



You need to reduce the amount of request units (RUs) consumed by the analytics application.
What should you do?

  1. Decrease the offerThroughput value for the container.
  2. Increase the offerThroughput value for the container.
  3. Move the data to a new container that uses a partition key of deviceId.
  4. Move the data to a new container that uses a partition key of temp.

Answer(s): C

Explanation:

The analytics application would frequently read from the same partition of Device ID is used as partition key.
Note: The partition key determines how Azure Cosmos DB routes data in partitions. The IoT Device ID is the usual partition key for IoT applications.


Reference:

https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/iot-using-cosmos-db Topic 2 - Question Set 2



DRAG DROP (Drag and Drop is not supported).
You have an Azure Cosmos DB Core (SQL) API account that is con gured for multi-region writes. The account contains a database that has two containers named container1 and container2.
The following is a sample of a document in container1:
{
"customerId": 1234,
" rstName": "John",
"lastName": "Smith",
"policyYear": 2021
}
The following is a sample of a document in container2:
{
"gpsId": 1234,
"latitude": 38.8951,
"longitude": -77.0364
}
You need to con gure con ict resolution to meet the following requirements:
For container1 you must resolve con icts by using the highest value for policyYear. For container2 you must resolve con icts by accepting the distance closest to latitude: 40.730610 and longitude: -73.935242.
Administrative effort must be minimized to implement the solution.
What should you con gure for each container? To answer, drag the appropriate con gurations to the correct containers. Each con guration may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Last Write Wins (LWW) (default) mode
Last Write Wins (LWW): This resolution policy, by default, uses a system-de ned timestamp property. It's based on the time-synchronization clock protocol.
Box 2: Merge Procedures (custom) mode
Custom: This resolution policy is designed for application-de ned semantics for reconciliation of con icts. When you set this policy on your Azure Cosmos container, you also need to register a merge stored procedure. This procedure is automatically invoked when con icts are detected under a database transaction on the server. The system provides exactly once guarantee for the execution of a merge procedure as part of the commitment protocol.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/con ict-resolution-policies https://docs.microsoft.com/en-us/azure/cosmos-db/sql/how- to-manage-con icts






Post your Comments and Discuss Microsoft DP-420 exam with other Community members: