Exam AZ-304 topic 4 question 24 discussion

The correct answer should be C. The cosmos DB table api is compatible with Azure Table Storage api, just need to change few lines of code. and the Azure table storage api has uncertain latency and 20000 operation per second limitation.

Should be C. The text solution is right

Isn't it confusing how they choose D & write a comment that support C option? the funny thing, I've seen this in another forum and they also made the exact mistake. I wonder what is going on? Somebody is cheating and they are doing it very badly

If I have offices in 4 countries, I wouldn't care and will just pass the task to someone who already cleared the AZ-305/304 certification.

The correct answer should be C.

The correct answer should be C. The cosmos DB table api is compatible with Azure Table Storage api, just need to change few lines of code. and the Azure table storage api has uncertain latency and 20000 operation per second limitation.

bad answer but a good explanation. it should be C

"Azure Cosmos DB" fulfills the requirements, the answer is wrong but the associated explanation is correct.

"Azure Cosmos DB" fulfills the requirements, the answer is wrong but the associated explanation is correct.

Azure Cosmos DB Table API has - ✑ Single-digit millisecond latency for reads and writes, backed with <10-ms latency reads and <15-ms latency writes at the 99th percentile, at any scale, anywhere in the world. ✑ Automatic and complete indexing on all properties, no index management. ✑ Turnkey global distribution from one to 30+ regions. Support for automatic and manual failovers at any time, anywhere in the world.

The answer is wrong but the explanation is correct.

Why is not corrected 😞?

Answer..."C." "Azure Cosmos DB supports two indexing modes: Consistent: The index is updated synchronously as you create, update or delete items. This means that the consistency of your read queries will be the consistency configured for the account. None: Indexing is disabled on the container. This is commonly used when a container is used as a pure key-value store without the need for secondary indexes. It can also be used to improve the performance of bulk operations. After the bulk operations are complete, the index mode can be set to Consistent and then monitored using the IndexTransformationProgress until complete." Link: https://docs.microsoft.com/en-us/azure/cosmos-db/index-policy

The correct answer should be C. Cosmos DB latency for reads and writes, backed with <10-ms latency reads and <15-ms latency writes. Azure table storage is Fast, but no upper bounds on latency. https://docs.microsoft.com/en-us/azure/cosmos-db/table/table-support

Correct Answer C. Azure Cosmos DB

https://docs.microsoft.com/en-us/azure/cosmos-db/table-support Answer is C

IMHO Should Be C.