Correct Answer: Use 'tenantId' as the partition key so all tenant data is in the same logical partition
Using tenantId as the partition key ensures all data for a tenant is in the same logical partition, enabling efficient, cross-item queries within a tenant without cross-partition f...
Correct Answer
Use 'tenantId' as the partition key so all tenant data is in the same logical partition
Why This Answer Is Correct
Using tenantId as the partition key ensures all data for a tenant is in the same logical partition, enabling efficient, cross-item queries within a tenant without cross-partition fan-out. This provides tenant isolation and predictable query performance, ideal for multi-tenant patterns.
This question evaluates your knowledge of Azure Cosmos DB — a core concept tested in Microsoft Certified: Azure Developer Associate (AZ-204). Understanding Azure Cosmos DB is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
Your application reads Azure Cosmos DB data globally across three regions. The marketing team needs data to eventually be the same across all regions, and can tolerate reading slightly stale data (up to 5 minutes old) in exchange for lower latency reads. Which consistency level should you configure?
You are designing a multi-tenant SaaS application where each tenant's data must be isolated and queries must be highly efficient for per-tenant reads. The application will have thousands of tenants. Which Cosmos DB partition key design is most appropriate?
You are developing a high-throughput shopping cart service using Azure Cosmos DB for NoSQL. The service needs to update a customer's shopping cart document by adding an item. To ensure high efficiency, minimize RU/s consumption, and prevent concurrent modification conflicts without loading the entire document first, which feature should you use?
You are building a microservices architecture. You need a data sync solution where changes to documents in your primary Azure Cosmos DB database automatically trigger a downstream search index service to update its records in real-time. Which Cosmos DB feature allows you to listen for changes without polling the database?