Microsoft Certified: Azure Solutions Architect ExpertDesign data storage solutionsEasy
An online gaming company stores player profile data, including usernames, scores, and game preferences. This data needs to be highly available with low-latency access for millions of concurrent players globally. The data model is relatively simple (key-value pairs) and does not require complex relational queries. Occasional eventual consistency for some non-critical fields is acceptable, but high throughput is essential. Which Azure data storage solution is most appropriate?
- AAzure Cosmos DB (Gremlin API)
- BAzure Database for PostgreSQL
- CAzure Table Storage
- DAzure SQL Database
Show answer & explanationAnswer & explanation
Correct answer: C. Azure Table Storage
Azure Table Storage is a NoSQL key-value store that is highly scalable, cost-effective, and provides low-latency access for simple data models. It offers high availability and can handle millions of entities with eventual consistency, making it suitable for player profiles where complex relational queries are not needed.
Why the other options are wrong
- A. Azure Cosmos DB (Gremlin API) is for graph databases, suitable for highly connected data, which is not the primary requirement for simple player profiles.
- B. Azure Database for PostgreSQL is a relational database and is not optimized for simple key-value data models requiring massive scale, high throughput, and eventual consistency at the cost-point of Table Storage.
- D. Azure SQL Database is a relational database and is overkill for a simple key-value data model, and might be more expensive and complex to manage for global scale and high throughput with eventual consistency needs.
Azure Table Storage
Azure Table Storage is a NoSQL key-value store that enables you to store large amounts of structured, non-relational data. It is highly scalable, inexpensive, and provides fast access to data, making it suitable for applications requiring massive scale and flexible schema for simple entities.
- NoSQL key-value store
- Stores structured, non-relational data (entities with properties)
- Highly scalable (millions of entities, TBs of data)
- Inexpensive storage costs
- Low-latency access, eventual consistency
Memory trick: Player profiles in Table Storage, simple and fast.