โ† All Microsoft Certified: Azure Developer Associate Flashcard Decks

Azure Cosmos DB Development Flashcards

7 cards from real Microsoft Certified: Azure Developer Associate practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Azure Cosmos DB Development flashcards as text
  1. Which consistency level in Azure Cosmos DB provides the strongest consistency guarantee?

    Answer: Strong

    Strong consistency ensures linearizability, meaning reads always return the most recent committed version of an item.

  2. What is the unit used to measure provisioned throughput in Azure Cosmos DB?

    Answer: RU/s (Request Units per second)

    Azure Cosmos DB uses Request Units per second (RU/s) as the abstracted currency for CPU, IOPS, and memory consumed by operations.

  3. Which Azure Cosmos DB API is designed for working with graph data and relationships?

    Answer: Gremlin API

    The Gremlin API (Graph API) supports the Apache TinkerPop Gremlin graph traversal language for modeling and querying graph data.

  4. What is the maximum size of a single document (item) in Azure Cosmos DB?

    Answer: 4 MB

    Azure Cosmos DB supports individual item (document) sizes up to 2 MB.

  5. Which partition key choice would result in the BEST throughput distribution in a Cosmos DB container storing IoT sensor readings?

    Answer: deviceId

    Using deviceId distributes data evenly across logical partitions since each device generates a unique stream of readings, avoiding hot partitions.

  6. Which Azure Cosmos DB consistency level guarantees that within a single client session, reads always reflect that client's own writes?

    Answer: Session

    Session consistency is scoped to a client session and guarantees monotonic reads, monotonic writes, and read-your-writes within that session.

  7. What happens when you set Time to Live (TTL) to -1 on an Azure Cosmos DB container?

    Answer: TTL is disabled and items never expire

    Setting TTL to -1 on the container enables TTL at the container level but items only expire if they have an explicit _ttl property set on them; without it they live forever.