The partition specifies how Azure storage load balances entities, messages, and blobs across servers to achieve the traffic requirements of these objects.
Which of the following represents the partition key for a blob?
Click on the arrows to vote for the correct answer
A. B. C. D. E.Correct Answer: B
For a blob, the partition key consists of account name + container name + blob name.
Data is partitioned into ranges using these partition keys and these ranges are load balanced throughout the system.
Option A is incorrect.
For a blob, the partition key includes account name + container name + blob name.
Option B is correct.
For a blob, the partition key includes account name + container name + blob name.
Option C is incorrect.
Account name + Queue name + blob name is not the right partition key for a blob.
Option D is incorrect.
For an entity in a table, the partition key includes the table name and the partition key.
Option E is incorrect.
For a message in a queue, the queue name is the partition key itself.
Reference:
To know more about Partitioning Azure Blob Storage, please visit the below-given link:
The correct answer is B. Account name + container name + blob name.
In Azure Storage, blobs are stored in containers, and the partition key for a blob is determined by the container it belongs to. The partition specifies how Azure storage load balances entities, messages, and blobs across servers to achieve the traffic requirements of these objects.
Option A and D are incorrect because they refer to table partitions, which are used for Azure Table Storage, not for blobs. Option C is also incorrect because it combines a queue name with a blob name, which is not a valid way to partition blobs.
Option E only includes the account name and the queue name, which is not sufficient to identify a blob partition. A blob partition also requires the container name.
Therefore, the correct answer is B. Account name + container name + blob name. This combination allows Azure Storage to load balance the blobs within a container and distribute the load across servers as needed to meet traffic requirements.