AZ-200 Azure Storage Solutions 1 — Questions and Answers
Question 1: Which Azure Blob Storage access tier is optimized for data that is rarely accessed and stored for at least 180 days?
- Hot
- Cool
- Cold
- Archive (Correct answer)
Correct 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.
Question 2: What is the maximum size of a single block blob in Azure Blob Storage?
- 1 TB
- 4.77 TB
- 190.7 TB (Correct answer)
- 500 GB
Correct 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.
Question 3: Which Shared Access Signature (SAS) type is associated with a stored access policy on a container?
- Account SAS
- Service SAS (Correct answer)
- User delegation SAS
- Delegation SAS
Correct 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.
Question 4: What is the difference between LRS and ZRS redundancy options in Azure Storage?
- LRS replicates across zones; ZRS replicates within one datacenter
- LRS replicates within one datacenter; ZRS replicates across availability zones in a region (Correct answer)
- LRS is geo-redundant; ZRS is locally redundant
- LRS costs more; ZRS is free
Correct 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.
Question 5: Which Azure Storage feature allows immutable, time-limited locks on blobs to prevent modification or deletion?
- Blob snapshots
- Immutability policies (WORM) (Correct answer)
- Soft delete
- Azure Backup integration
Correct 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.
Question 6: How do you use Azure Queue Storage to implement a poison-message handler?
- Enable dead-letter queue in Queue Storage settings
- Detect messages that have exceeded the maximum dequeue count and move them to a separate queue (Correct answer)
- Set a TTL of zero on unwanted messages
- Use Azure Service Bus instead since Queue Storage has no poison handling
Correct 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.
AZ-200 Azure Storage Solutions 1
Which Azure Blob Storage access tier is optimized for data that is rarely accessed and stored for at least 180 days?