For IndividualsFor Educators
ExpertMinds LogoExpertMinds
ExpertMinds

Ace your certifications with Practice Exams and AI assistance.

  • Browse Exams
  • For Educators
  • Blog
  • Privacy Policy
  • Terms of Service
  • Cookie Policy
  • Support
  • AWS SAA Exam Prep
  • PMI PMP Exam Prep
  • CPA Exam Prep
  • GCP PCA Exam Prep

© 2026 TinyHive Labs. Company number 16262776.

    PracticeAzure Solutions Architect Expert (AZ-305)Azure Solutions Architect Expert AZ-305 Practice Exam 5Question 27
    Medium1 markMultiple Choice
    Domain 2.4: Non-Relational Data StorageDomain 2Cosmos DBPartitioningPerformance

    AZ-305 · Question 27 · Domain 2.4: Non-Relational Data Storage

    You are designing an Azure Cosmos DB (NoSQL API) database for an IoT fleet management system.

    The system receives telemetry from 100,000 vehicles. Each vehicle sends a JSON document every minute. The most common query run by the application is: SELECT * FROM c WHERE c.VehicleId = 'V-12345' AND c.Timestamp > '2023-01-01'.

    You need to select a partition key that ensures even distribution of storage and throughput, and minimizes cross-partition queries.

    Which property should you choose as the partition key?

    Answer options:

    A.

    /Timestamp

    B.

    /VehicleId

    C.

    /FleetRegion

    D.

    /id

    How to approach this question

    A good partition key needs high cardinality (many unique values) for write distribution, and should be present in the WHERE clause of common queries for read efficiency.

    Full Answer

    B./VehicleId✓ Correct
    In Cosmos DB, choosing the right partition key is critical. `/VehicleId` is the best choice. It has high cardinality (100,000 vehicles), meaning writes will be evenly distributed across physical partitions, avoiding hot spots. Furthermore, the most common query filters by `VehicleId`. By partitioning on `VehicleId`, Cosmos DB can route the query to a single physical partition, making the read highly efficient. Partitioning by `/Timestamp` would cause all current writes to hit a single partition (hot spot).

    Common mistakes

    Choosing `/id`. While it distributes writes perfectly, it ruins read performance because querying by `VehicleId` would require scanning every single partition (cross-partition query).
    Question 26All questionsQuestion 28

    Practice the full Azure Solutions Architect Expert AZ-305 Practice Exam 5

    55 questions · hints · full answers · grading

    Sign up freeTake the exam

    More questions from this exam

    Q01Contoso Ltd has 50 subscriptions across 3 business units. Each business unit manages its own IT o...EasyQ02You are designing a monitoring solution for a hybrid environment. The environment consists of 200...MediumQ03Your company uses Microsoft Sentinel integrated with a Log Analytics workspace. The workspace ing...HardQ04You are designing an application monitoring strategy using Application Insights. The application ...MediumQ05A highly regulated financial institution is migrating to Microsoft 365 and Azure. They currently ...Hard
    View all 55 questions →