You are designing an Azure application that stores data.
You have the following requirements:
The data storage system must support storing more than 500 GB of data.
Data retrieval must be possible from a large number of parallel threads.
Threads must not block each other.
You need to recommend an approach for storing data.
What should you recommend?
A.
Azure Notification Hubs
B.
A single SQL database in Azure
C.
Azure Queue storage
D.
Azure Table storage
Explanation:
* Azure Table Storage can be useful for applications that must store large amounts of nonrelational
data, and need additional structure for that data. Tables offer key-based access to unschematized
data at a low cost for applications with simplified data-access patterns. While Azure Table Storage
stores structured data without schemas, it does not provide any way to represent relationships
between the data.
* As a solution architect/developer, consider using Azure Table Storage when:
/ Your application stores and retrieves large data sets and does not have complex relationships that
require server-side joins, secondary indexes, or complex server-side logic.
/ You need to achieve a high level of scaling without having to manually shard your dataset.
Azure Table Storage and Windows Azure SQL Database – Compared and Contrasted
https://msdn.microsoft.com/en-us/library/azure/jj553018.aspx
Ans: D is correct
Explanation:
* Blob Leases allow you to claim ownership to a Blob. Once you have the lease you can then update the Blob or delete the Blob without worrying about another process changing it underneath you. When a Blob is leased, other processes can still read it, but any attempt to update it will fail. You can update Blobs without taking a lease first, but you do run the chance of another process also attempting to modify it at the same time.
Using Blob Leases to Manage Concurrency with Table Storage
http://www.azurefromthetrenches.com/?p=1371
Using Blob Leases to Manage Concurrency with Table Storage
http://www.azurefromthetrenches.com/?p=1371