Exam DP-201 topic 1 question 6 discussion

Actual exam question from Microsoft's DP-201

Question #: 6
Topic #: 1

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 shards by using horizontal partitioning.
Does the solution meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: A 🗳️
Horizontal Partitioning - Sharding: Data is partitioned horizontally to distribute rows across a scaled out data tier. With this approach, the schema is identical on all participating databases. This approach is also called ג€shardingג€. Sharding 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.
Reference:
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-elastic-query-overview

by syu31svc at Dec. 8, 2020, 2:33 p.m.

Comments

Submit Cancel

sjain91

Highly Voted 4 years, 1 month ago

Yes is the answer

upvoted 6 times

...

Pdpj

Most Recent 3 years, 11 months ago

No is the answer This solution does not meet the requirements. You need to use sharding, which is partitioning data horizontally to distribute data across multiple databases in a scaled-out design, but CustomerID is not the best choice in this scenario. Sharding by RegionalID will make sorting by geographic location more efficient. Sharding requires that the schema is the same on all of the databases involved. Sharding helps to minimize the size of individual databases, which in turn helps to improve transactional process performance. Hardware support requirements are minimized, which helps to reduce related costs. Elastic queries let you run queries across multiple shards. You can configure and manage sharding through the elastic database tools libraries or through self-sharding

upvoted 3 times

...

syu31svc

4 years, 6 months ago

This is the correct solution

upvoted 4 times

JohnCrawford

4 years, 1 month ago

I disagree. CustomerID will be unique and that means you would have as many shards as you have customers. This would be a poor design. The question is poorly worded and given the wording the answer might be correct, but it is lousy design.

upvoted 2 times

Wisenut

4 years ago

I agree sharding based on region would be a better fit

upvoted 1 times

cadio30

4 years ago

this would only be correct if compound shard is created for customerid and region

upvoted 1 times

...

suvenk

4 years ago

Well, the more the shards, the lesser is the likelihood of you facing the hot partition problem. The region will create a hot partition problem.

upvoted 3 times

...