What should you recommend?

You are designing a Windows Azure application that will use Windows Azure Table storage. The application will allow teams of users to collaborate on projects. Each user is a member of only one team. You have the following requirements:

-Ensure that each user can efficiently query records related to his or her team’s projects.

-Minimize data access latency.

You need to recommend an approach for partitioning table storage entities.

What should you recommend?
A . Partition by user
B . Partition by team
C . Partition by project
D . Partition by the current date

Answer: B


Partitions represent a collection of entities with the same PartitionKey values. Partitions are always served from one partition server and each partition server can serve one or more partitions. A partition server has a rate limit of the number of entities it can serve from one partition over time.

Explanation: https://docs.microsoft.com/en-us/rest/api/storageservices/Designing-a-Scalable-Partitioning-Strategy-for-Azure-Table-Storage?redirectedfrom=MSDN

Latest 70-535 Dumps Valid Version with 458 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Notify of
Inline Feedbacks
View all comments