Q: 2
Which Azure Cosmos DB API should you use for a graph database?
Options
Discussion
A. official docs and practice tests both point to Gremlin API for graph databases.
A . Lot of folks get tripped up thinking NoSQL (B) covers everything, but Gremlin (A) is the actual graph API here.
Option A matches what I saw on a similar practice test. Gremlin API is built for graph.
Feels like A, since Gremlin is made for graph queries. B is tempting but doesn't actually support true graph features.
Its A
Option A fits here. The Gremlin API is meant for graph scenarios, while B and C are for document and column models. D is more for key-value, not graph. I think some might mix up B but A is right for this use case.
I don’t think B works here. The NoSQL API is flexible but not designed for graph traversal, which is key in a graph database scenario. Pretty sure A (Gremlin) is the intended use, though NoSQL can trip people up.
Pretty sure A here. Gremlin API is purpose-built for graph work like nodes and edges, while NoSQL (B) isn't optimized for graph queries. Used this in labs a few times, so I'm pretty sure A is the right fit, but open to other takes.
A , seen this in official docs and practice questions. Review the Microsoft docs or a practice exam if unsure.
I don’t think it’s B. A is designed for graph databases since Gremlin handles nodes and edges directly. B can store data but doesn’t support true graph queries. Pretty sure A, let me know if I’m missing something.
Be respectful. No spam.
