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 4Question 28
    Hard1 markMultiple Choice
    Domain 2.3: Recommend a Data Storage SolutionDatabaseCosmos DBPartitioning

    AZ-305 · Question 28 · Domain 2.3: Recommend a Data Storage Solution

    You are designing an Azure Cosmos DB database for a global IoT application.

    Millions of devices will write telemetry data continuously. The data will be queried heavily by a dashboard that filters by DeviceId and Date. You need to select a partition key that ensures even distribution of storage and throughput (Request Units) to avoid 'hot partitions'.

    Which TWO partition key strategies would be effective? (Select TWO)

    Answer options:

    A.

    Date

    B.

    A synthetic key combining DeviceId and Date

    C.

    DeviceId

    D.

    DeviceType

    E.

    TenantId (assuming all devices belong to one tenant)

    How to approach this question

    Look for high cardinality (many unique values) and even write distribution. Avoid properties that group all current writes together (like Date).

    Full Answer

    A synthetic key combining DeviceId and Date, DeviceId
    In Cosmos DB, the partition key determines how data is distributed across physical partitions. `DeviceId` is a good choice because with millions of devices, it has high cardinality and spreads writes evenly. A synthetic key combining `DeviceId` and `Date` is also excellent, as it prevents any single device's partition from growing too large over time while still supporting the dashboard's query pattern.

    Common mistakes

    Selecting 'Date'. Partitioning by date is an anti-pattern for write-heavy workloads because all writes for the current day hit a single physical partition, causing throttling.
    Question 27All questionsQuestion 29

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

    55 questions · hints · full answers · grading

    Sign up freeTake the exam

    More questions from this exam

    Q01CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...MediumQ02CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...MediumQ03CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...HardQ04CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...MediumQ05CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...Hard
    View all 55 questions →