Notifications
Clear all
Topic starter
28/09/2022 12:30 am
Your company needs to design a database that shows how changes traffic in one area of a network affect other components on the network.
Which type of data store should you use?
- A . Key/value
- B . Graph
- C . Document
- D . columnar
Suggested Answer: B
Explanation:
Data as it appears in the real world is naturally connected. Traditional data modeling focuses on defining entities separately and computing their relationships at runtime. While this model has its advantages, highly connected data can be challenging to manage under its constraints.
A graph database approach relies on persisting relationships in the storage layer instead, which leads to highly efficient graph retrieval operations. Azure Cosmos DB's Gremlin API supports the property graph model.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/graph-introduction#introduction-to-graph-databases
Explanation:
Data as it appears in the real world is naturally connected. Traditional data modeling focuses on defining entities separately and computing their relationships at runtime. While this model has its advantages, highly connected data can be challenging to manage under its constraints.
A graph database approach relies on persisting relationships in the storage layer instead, which leads to highly efficient graph retrieval operations. Azure Cosmos DB's Gremlin API supports the property graph model.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/graph-introduction#introduction-to-graph-databases