Shortest Path in DAG
A medium Graph problem included in Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Graph
- Sheets
- 1
- Core for
- 11 roles
- Platform
- GeeksforGeeks
The problem
Given a directed acyclic graph with n vertices and a list of weighted edges [u, v, weight], and a source vertex, find the shortest path distances from the source to all other vertices using topological sorting.
Example 1
- Input
- n = 6, edges = [[0,1,5],[0,2,3],[1,3,6],[2,4,4],[3,5,1],[4,5,1]], source = 0
- Output
- [0,5,3,11,7,5]
- Why
- Shortest paths from 0 to all nodes using topological order.
Example 2
- Input
- n = 3, edges = [[0,1,2],[1,2,3]], source = 0
- Output
- [0,2,5]
- Why
- Path 0->1->2 gives distances 2 and 5.
Constraints
- 1 <= n <= 100
- 0 <= edges.length <= n * (n - 1)
- 1 <= edge weight <= 1000
How to think about it
Updated 2026-09-09In a directed acyclic graph, cycles are impossible, which means vertices can be sorted in strict topological order. If you process vertices in topological order, by the time you arrive at vertex u, its shortest path distance is permanently finalized because no subsequent vertex can ever loop back to affect it. This achieves shortest path in linear time without priority queues.
Approaches, worst first
Standard Bellman-Ford relaxation
time O(V * E) · space O(V)
Relax all edges repeatedly across V - 1 full passes starting from the source vertex. While Bellman-Ford correctly finds shortest paths even with negative edge weights, it ignores topological ordering and requires O(V * E) time instead of a single linear pass.
Topological order single-pass relaxationWrite this one
time O(V + E) · space O(V + E)
Find a topological ordering of the DAG using DFS or Kahn's algorithm. Initialize `dist` array to infinity with `dist[source] = 0`. Iterate through the topological ordering: for each vertex u, if `dist[u] !== inf`, relax all outgoing edges `(u, v, weight)` setting `dist[v] = min(dist[v], dist[u] + weight)`.
Where people lose marks · 3
- Skipping the check `dist[u] !== inf` before relaxing outgoing edges; relaxing from unreachable nodes propagates invalid arithmetic.
- Vertices that appear before `source` in the topological sort order cannot be reached from `source` and must remain at infinity.
- Assuming the graph has a source with in-degree 0; the given starting node may have incoming edges from predecessor components.
The theory behind it
Graph — the ground this problem stands on. All Graph problems
What Graph is
A graph is a network of individual points, called vertices or nodes, connected by lines called edges. Think of a subway transit map, an electrical circuit, or a web of social friends. Unlike a tree, a graph has no designated top node and no parent-child hierarchy. Connections can run one-way or both ways, and paths can loop back on themselves to form closed cycles.
When to reach for it
Reach for graph algorithms when inputs describe relationships, networks, flights between cities, course prerequisites, or clone networks. Signals include finding the shortest route across unweighted connections, ordering tasks that depend on earlier tasks, counting isolated clusters, or checking whether a path contains an infinite loop. Whenever problems present pairs of related entities and ask for reachability, distances, or dependencies, graph representations apply.
How the pattern works
First convert edge lists into an adjacency list, mapping each node to an array of its neighbors. Choose your exploration strategy based on the goal: use a queue and breadth-first search to find the shortest path in unweighted networks, or use recursion and depth-first search to explore full paths and detect cycles. Because graphs can have loops, always track visited nodes in a set or boolean array. Add nodes to the visited set at the moment they enter the queue so they are never visited twice.
What each operation costs
| Operation | Time |
|---|---|
| visit all nodes and edges via search | O(v + e) |
| topological sort using in-degree counts | O(v + e) |
| shortest path using dijkstra with a min-heap | O((v + e) log v) |
What usually goes wrong with Graph
- Adding a node to the visited set when popping from the queue instead of when pushing, which lets neighboring nodes enqueue duplicate entries and wastes memory.
- Failing to check for cycles in directed graphs when finding prerequisite orders, causing topological sort routines to hang or return incomplete lists.
- Assuming an input graph is fully connected and scanning from only a single starting node, missing disconnected islands and isolated components.
Which roles need this problem
Graph is a core topic for these 11 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 6 more roles, including Performance Engineer, Search Engineer, Information Retrieval Engineer.
Track this in your role's order
Pick your target role and all 370 problems — including this one — resequence to what that interview actually asks. Free.
Start freeMore Graph problems
Problem set and role mapping as of .