Cosmos DB Interview Questions and Answers
Question - 61 : - Is A Default Table Throughput Set For Newly Provisioned Tables?
Answer - 61 : - Yes, in case you do not override the Table Throughput thru app.Config and do not use a pre-created container in Azure Cosmos DB
Question - 62 : - Is There Any Change Of Pricing For Existing Customers Of The Azure Table Storage Service?
Answer - 62 : - None. There isn't any trade in fee for existing Azure Table garage clients.
Question - 63 : - How Is The Price Calculated For The Table Api?
Answer - 63 : - The fee depends at the allocated Table Throughput.
Question - 64 : - How Do I Handle Any Throttling On The Tables In Table Api Offering?
Answer - 64 : - If the request charge exceeds the potential of the provisioned throughput for the underlying container, you get an mistakes, and the SDK retries the call via applying the retry coverage.
Question - 65 : - Why Do I Need To Choose A Throughput Apart From Partition Key And Rowkey To Take Advantage Of The Table Api Offering Of Azure Cosmos Db?
Answer - 65 : - Azure Cosmos DB units a default throughput for your field if you do no longer provide one inside the app.Config file or through the portal.
Azure Cosmos DB affords guarantees for performance and latency, with higher bounds on operation. This guarantee is possible whilst the engine can implement governance on the tenant's operations. Setting Table Throughput ensures which you get the guaranteed throughput and latency, due to the fact the platform reserves this capacity and ensures operational achievement.
By the usage of the throughput specification, you can elastically exchange it to benefit from the seasonality of your application, meet the throughput needs, and store expenses.
Question - 66 : - Azure Table Storage Has Been Very Inexpensive For Me, Because I Pay Only To Store The Data, And I Rarely Query. The Azure Cosmos Db Table Api Offering Seems To Be Charging Me Even Though I Have Not Performed A Single Transaction Or Stored Anything. Can You Please Explain?
Answer - 66 : - Azure Cosmos DB is designed to be a globally distributed, SLA-based totally machine with guarantees for availability, latency, and throughput. When you reserve throughput in Azure Cosmos DB, it's miles guaranteed, unlike the throughput of other structures. Azure Cosmos DB offers additional abilties that customers have requested, inclusive of secondary indexes and international distribution.
Question - 67 : - So Partition Key And Rowkey Are Still Required With The Table Api?
Answer - 67 : - Yes. Because the floor area of the Table API is much like that of the Azure Table storage SDK, the partition key offers an efficient manner to distribute the information. The row key's particular within that partition. The row key desires to be gift and can't be null as inside the general SDK. The period of RowKey is 255 bytes and the length of Partition Key is 1 KB.
Question - 68 : - How Can I Apply The Functionality Of Graph Api (preview) To Azure Cosmos Db?
Answer - 68 : - You can use an extension library to use the capability of Graph API (Preview). This library is called Microsoft Azure Graphs, and it is to be had on NuGet.
Question - 69 : - It Looks Like You Support The Gremlin Graph Traversal Language. Do You Plan To Add More Forms Of Query?
Answer - 69 : - Yes, we plan to feature different mechanisms for question within the destiny.
Question - 70 : - How Can I Use The New Graph Api (preview) Offering?
Answer - 70 : - To get started out, complete the Graph API brief-start article.