DP-900 · Question #102
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?
The correct answer is B. Graph. Graph databases model entities as nodes and relationships as edges, making them ideal for analyzing how changes in one network area propagate through interconnected components.
Question
Options
- AKey/value
- BGraph
- CDocument
- Dcolumnar
How the community answered
(32 responses)- A3% (1)
- B72% (23)
- C16% (5)
- D9% (3)
Why each option
Graph databases model entities as nodes and relationships as edges, making them ideal for analyzing how changes in one network area propagate through interconnected components.
Key/value stores are optimized for fast lookups by a unique key and have no native mechanism to model or traverse relationships between entities.
Graph databases store data as nodes (entities) and edges (relationships), enabling efficient traversal of how one network component affects others. This makes them the natural choice for modeling network topologies, dependency chains, and impact analysis - queries like 'which devices are affected if this router fails' map directly to graph traversal algorithms.
Document stores organize semi-structured data (e.g., JSON) and are suited for flexible schemas and hierarchical data, not for querying relationship propagation across a network.
Columnar stores are optimized for analytical aggregations over large datasets organized by column, not for traversing entity relationships or modeling network topology.
Concept tested: Graph database use cases for network relationship modeling
Source: https://learn.microsoft.com/en-us/azure/cosmos-db/graph/introduction
Topics
Community Discussion
No community discussion yet for this question.