Based on my understanding of Cosmos DB, I believe the two levels where you can set throughput are container and database. That seems like the most logical answer.
I'm a bit confused by this question. I know Cosmos DB has different levels, but I'm not sure if it's container and item, or container and database. I'll have to think about this one.
Okay, let me think this through. I know Cosmos DB has containers and databases, so those are probably the two levels. I'll go with container and database.
Oof, multiple levels for throughput? Sounds like a cosmic DB-sized headache to me. I'm just going to go with C) database and hope for the best. Fingers crossed!
This one's a no-brainer! B) item and D) partition, hands down. Cosmos DB is all about scaling to the max, and these options let you do just that. *chef's kiss*
Hmm, let's see. I'm going with A) container and C) database. Gotta keep that data flowing, even if it means setting the throughput at multiple levels. Classic Cosmos DB, am I right?
Ah, the power of Azure Cosmos DB's throughput settings! I'd say C) database and D) partition are the correct answers here. Gotta love that fine-tuned control over performance, right?
Richelle
4 months agoPaul
4 months agoRaymon
4 months agoJudy
4 months agoColetta
5 months agoMicheal
5 months agoDick
5 months agoAnika
5 months agoDella
5 months agoYan
5 months agoLonna
5 months agoRobt
5 months agoLyndia
5 months agoCarri
5 months agoGlendora
10 months agoMarvel
11 months agoAleisha
9 months agoGlendora
9 months agoLavera
10 months agoDorathy
11 months agoGretchen
9 months agoErnest
10 months agoLouisa
10 months agoCarlee
11 months agoMollie
9 months agoDan
9 months agoIzetta
10 months agoLarae
11 months agoAron
11 months agoThomasena
11 months agoJoesph
11 months agoThomasena
11 months ago