DP-201 Exam QuestionsBrowse all questions from this exam
Go to Exam

DP-201 Exam - Question 5

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 are designing an Azure SQL Database that will use elastic pools. You plan to store data about customers in a table. Each record uses a value for

CustomerID.

You need to recommend a strategy to partition data based on values in CustomerID.

Proposed Solution: Separate data into customer regions by using horizontal partitioning.

Does the solution meet the goal?

Show Answer
Correct Answer: B

The proposed solution suggests separating data into customer regions using horizontal partitioning. However, the goal is to partition data based on values in CustomerID, not on regions. Horizontal partitioning, also known as sharding, should be used to partition the data based on the customer ID values to ensure efficient distribution and management of data across databases. Therefore, the proposed solution does not meet the goal as stated.

Discussion

4 comments
Sign in to comment
fmunozse
Aug 23, 2020

I don't understand why is not recommend horizontal ... Each shard could be the region, no?

stijn5454
Aug 24, 2020

Horizontal partitioning splits one or more tables by row, usually within a single instance of a schema and a database server. Sharding goes beyond this: it partitions the problematic table(s) in the same way, but it does this across potentially multiple instances of the schema. The obvious advantage would be that search load for the large partitioned table can now be split across multiple servers (logical or physical), not just multiple indexes on the same logical server. Ref: https://en.wikipedia.org/wiki/Shard_(database_architecture)#Shards_compared_to_horizontal_partitioning

redalarm2000
Jan 15, 2021

Ok i am confused as to the difference between question 4 and question 5 on this site. Question 4 says to use horizontal partitioning but Question 5 says it recommends to use horizontal partition and the wording is the same but they say that answer should be No still why?

Shanmahi
Jan 25, 2021

Answer : No Applicable solution : Horizontal partitioning (based on customerID not region i.e. using sharding concept) Reference : https://docs.microsoft.com/en-us/azure/architecture/best-practices/data-partitioning

osoroshi
Mar 3, 2021

harding can be performed and managed using (1) the elastic database tools libraries or (2) self-sharding. An elastic query is used to query or compile reports across many shards. Shards are typically databases within an elastic pool. You can think of elastic query as an efficient way for querying all databases of elastic pool at once, as long as databases share the common schema.

Ankush1994
Aug 15, 2021

Correct answer is No becuase Separate data into shards by using horizontal partitioning