Microsoft Certified: Azure Developer Associate (AZ-204)Develop for Azure storageMedium
A developer needs to implement a solution to store configuration settings for a microservice. The settings are small, structured key-value pairs (e.g., `featureToggle: true`, `apiEndpoint: 'https://...'`). The solution requires high availability, strong consistency within a single region, and low cost for small data volumes. The data will be frequently read by the microservice instances.
- AAzure Blob Storage
- BAzure Table Storage
- CAzure Cosmos DB for NoSQL (Core) API
- DAzure Queue Storage
Show answer & explanationAnswer & explanation
Correct answer: B. Azure Table Storage
Azure Table Storage is a NoSQL key-value store designed for storing large amounts of structured, non-relational data. It offers high availability, strong consistency within a partition, and is very cost-effective for small data volumes with frequent reads, making it suitable for microservice configuration settings.
Why the other options are wrong
- A. Azure Blob Storage is for unstructured object data, not structured key-value configuration settings.
- C. Azure Cosmos DB offers more advanced features and higher cost for this simple key-value scenario, which can be handled more cost-effectively by Table Storage.
- D. Azure Queue Storage is for message queuing, not persistent configuration storage.
Azure Table Storage for Configuration
Azure Table Storage is a NoSQL data store that offers a cost-effective way to store structured, non-relational data in the cloud. It's ideal for small, frequently read key-value data like application configuration settings due to its high availability and low cost.
- Key-value store for structured data.
- Highly available and scalable.
- Very cost-effective for large volumes of small data.
- Strong consistency within a partition.
Memory trick: Tables are Tiny, Tidy, and Terrific for Config.