Question: 1/50
You are designing an Azure Cosmos DB for NoSQL container to store user profiles. Each profile is frequently retrieved by userId, and the application occasionally filters by country. Most requests read a single profile by id and partition key. Which partition key choice is recommended to optimize point reads and scalability?
Use /userId as the partition key
Use /country as the partition key
Use /id as the partition key and also store userId in a separate property
Do not define a partition key to avoid choosing the wrong one