An application uses Windows Azure Table storage.
The application uses five tables.
One table used by the application is approaching the limit for storage requests per second. You need to
recommend an approach for avoiding data access throttling.
What should you recommend?
A.
Use a single partition key for the table.
B.
Compress data before storing it in the table.
C.
Create additional partition keys for the table.
D.
Continually remove unnecessary data from the table.
Partitions are limited to 500 entities per second. If the throughput exceeds 500 entities per second for a partition, the server may run too hot in a production setting. In this case, the PartitionKey values may be too coarse, so that there are not enough partitions or the partitions are too large. You may need to modify the PartitionKey value so that the partitions can be distributed among more servers.
https://docs.microsoft.com/en-us/rest/api/storageservices/designing-a-scalable-partitioning-strategy-for-azure-table-storage#trea