You are working on an Azure-based application that utilizes Azure Cosmos DB for data storage. You've noticed scalability issues attributed to hot partitioning. What is the likely cause of this hot partitioning issue in Azure Cosmos DB?
Failing to set an indexing policy
Designing a partition key that leads to uneven request distribution
Running queries focused on a single partition key
Executing queries that don't use the partition key
Hot partitioning typically arises when there is an uneven distribution of requests or data across logical partitions. This imbalance prevents Azure Cosmos DB from scaling effectively. The ideal partition key should ensure a balanced distribution of both storage and throughput across partitions.