Practice Test GeeksAZ-200 - Microsoft Azure Developer Practice Test
← All AZ-200 Flashcard Decks

Azure Storage Solutions Flashcards

6 cards from real AZ-200 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 6 Azure Storage Solutions flashcards as text

  1. Which Azure Blob Storage access tier is optimized for data that is rarely accessed and stored for at least 180 days?

    Answer: Archive

    The Archive tier is the lowest-cost storage tier, designed for data that can tolerate retrieval latency of hours and is kept for at least 180 days.

  2. What is the maximum size of a single block blob in Azure Blob Storage?

    Answer: 190.7 TB

    A block blob can be up to approximately 190.7 TB in size, composed of up to 50,000 blocks each up to 4,000 MiB.

  3. Which Shared Access Signature (SAS) type is associated with a stored access policy on a container?

    Answer: Service SAS

    A Service SAS can be linked to a stored access policy defined on a container, allowing you to revoke or modify permissions without regenerating the SAS token.

  4. What is the difference between LRS and ZRS redundancy options in Azure Storage?

    Answer: LRS replicates within one datacenter; ZRS replicates across availability zones in a region

    LRS keeps three copies within a single datacenter, while ZRS synchronously replicates data across three availability zones in the same region.

  5. Which Azure Storage feature allows immutable, time-limited locks on blobs to prevent modification or deletion?

    Answer: Immutability policies (WORM)

    Immutability policies (Write Once, Read Many) on Azure Blob Storage lock blobs so they cannot be modified or deleted for a specified retention period.

  6. How do you use Azure Queue Storage to implement a poison-message handler?

    Answer: Detect messages that have exceeded the maximum dequeue count and move them to a separate queue

    Azure Queue Storage exposes a dequeue count on each message, allowing application code to detect repeated failures and move the message to a separate 'poison' queue.