Microsoft Certified: Azure Developer Associate (AZ-204)Develop for Azure storageMedium
A developer needs to implement a solution to store configuration settings for a microservices application. These settings are small, frequently updated, and require fast read access. The data structure is simple, consisting of key-value pairs with a few additional properties per setting. Which Azure storage service is the MOST suitable for this scenario?
- AAzure Queue Storage
- BAzure Table Storage
- CAzure Blob Storage
- DAzure Cosmos DB (SQL API)
Show answer & explanationAnswer & explanation
Correct answer: B. Azure Table Storage
Azure Table Storage is a NoSQL key-value store optimized for storing large amounts of structured, non-relational data. It's highly scalable, cost-effective, and provides fast access for simple key-value lookups, making it ideal for configuration settings.
Why the other options are wrong
- A. Azure Queue Storage is for messages, not for persistent configuration data storage.
- C. Azure Blob Storage is for unstructured large objects, not small, structured key-value configurations.
- D. Azure Cosmos DB (SQL API) is a powerful document database but might be overkill and more expensive for simple key-value configuration settings where Azure Table Storage suffices.
Azure Table Storage
A NoSQL key-value store service in Azure for storing large amounts of structured, non-relational data, offering high scalability and low cost.
- Stores entities with PartitionKey and RowKey.
- Schemaless design, allowing flexible properties.
- Cost-effective for large volumes of simple data with fast lookups.
Memory trick: Choosing a NoSQL store is about matching data shape to speed needs.