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: 6)

Page 5 of 23
PDF with 175 Questions

You have a container in an Azure Cosmos DB Core (SQL) API account that stores data about orders.
The following is a sample of an order document.



Documents are up to 2 KB.
You plan to receive one million orders daily.
Customers will frequently view their past order history.
You are the evaluating whether to use orderDate as the partition key.
What are two effects of using orderDate as the partition key? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.

  1. You will exceed the maximum number of partition key values
  2. You will exceed the maximum storage per partition
  3. There will always be a hot partition
  4. Queries will run cross-partition

Answer(s): C,D

Explanation:

Not C: But the problem is that " when the application writes new data, the writes will always be directed to the same partition, based on whatever day it is. This results in what's called a hot partition, where we have a bottleneck that's going to quickly consume a great deal more of the reserved throughput you've provisioned for the container. Speci cally, Cosmos DB evenly distributes your provisioned throughput across all the physical partitions in the container.
D: Customers will frequently view their past order history. OrderID will be used. Queries will run cross-partition Incorrect:
Not B: 1 million a day x 2KB -> 2 GB of data/day while maximum storage across all items per (logical) partition: 20 GB


Reference:

https://www.tallan.com/blog/2019/04/30/horizontal-partitioning-in-azure-cosmos-db https://docs.microsoft.com/en-us/azure/cosmos- db/concepts-limits



You have a container in an Azure Cosmos DB Core (SQL) API account. The container stores data about families. Data about parents, children, and pets are stored as separate documents.
Each document contains the address of each family. Members of the same family share the same partition key named familyId. You need to update the address for each member of the same family that share the same address. The solution must meet the following requirements:
Be atomic, consistent, isolated, and durable (ACID).
Provide the lowest latency.
What should you do?

  1. Update the document of each family member separately by using a patch operation
  2. Update the document of each family member separately and set the consistency level to strong
  3. Update the document of each family member by using a transactional batch operation

Answer(s): C

Explanation:

Each transaction provides ACID (Atomicity, Consistency, Isolation, Durability) property guarantees.
Transactional batch operations offer reduced latency on equivalent operations.
Note: Transactional batch describes a group of point operations that need to either succeed or fail together with the same partition key in a container. In the .NET
SDK, the TransactionalBatch class is used to de ne this batch of operations. If all operations succeed in the order they are described within the transactional batch operation, the transaction will be committed. However, if any operation fails, the entire transaction is rolled back.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/transactional-batch



You are designing an Azure Cosmos DB Core (SQL) API solution to store data from IoT devices. Writes from the devices will be occur every second.
The following is a sample of the data.



You need to select a partition key that meets the following requirements for writes:
Minimizes the partition skew
Avoids capacity limits
Avoids hot partitions
What should you do?

  1. Create a new synthetic key that contains deviceId and timestamp
  2. Use timestamp as the partition key
  3. Use deviceManufacturer as the partition key
  4. Use sensor1Value as the partition key

Answer(s): A

Explanation:

Concatenate multiple properties of an item.
You can form a partition key by concatenating multiple property values into a single arti cial partitionKey property. These keys are referred to as synthetic keys.
For example, consider the following example document:
{
"deviceId": "abc-123",
"date": 2018
}
For the previous document, one option is to set /deviceId or /date as the partition key. Use this option, if you want to partition your container based on either device
ID or date. Another option is to concatenate these two values into a synthetic partitionKey property that's used as the partition key.
{
"deviceId": "abc-123",
"date": 2018,
"partitionKey": "abc-123-2018"
}
Incorrect:
Not B: But the problem is that " when the application writes new data, the writes will always be directed to the same partition, based on whatever day it is. This results in what's called a hot partition, where we have a bottleneck that's going to quickly consume a great deal more of the reserved throughput you've provisioned for the container. Speci cally, Cosmos DB evenly distributes your provisioned throughput across all the physical partitions in the container.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/synthetic-partition-keys https://docs.microsoft.com/en-us/azure/cosmos- db/concepts-limits



You need to create a data store for a directory of small and medium-sized businesses (SMBs). The data store must meet the following requirements:
Store companies and the users employed by them. Each company will have less than 1,000 users.
Some users have data that is greater than 2 KB.
Associate each user to only one company.
Provide the ability to browse by company.
Provide the ability to browse the users by company.
Whenever a company or user pro le is selected, show a details page for the company and all the related users.
Be optimized for reading data.
Which design should you implement to optimize the data store for reading data?

  1. In a directory container, create a document for each company and a document for each user. Use the company ID as the partition key.
  2. Create a user container that uses the user ID as the partition key and a company container that uses the company ID as the partition key.
    Add the company ID to each user document.
  3. In a user container, create a document for each user. Embed the company into each user document. Use the user ID as the partition key.
  4. In a company container, create a document for each company. Embed the users into company documents. Use the company ID as the partition key.

Answer(s): D

Explanation:

All employees within a company would nicely t within a single document (document size 2 MB).
Note: An Azure Cosmos container is the unit of scalability both for provisioned throughput and storage. A container is horizontally partitioned and then replicated across multiple regions. The items that you add to the container are automatically grouped into logical partitions, which are distributed across physical partitions, based on the partition key.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/set-throughput






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