Binary Tree Cameras
A hard Binary Trees problem included in Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Binary Trees
- Sheets
- 1
- Core for
- 4 roles
- Platform
- LeetCode
The problem
Given a binary tree, install the minimum number of cameras on nodes so that every node is monitored. A camera at a node monitors itself, its parent, and its immediate children. Return the minimum number of cameras needed.
Example 1
- Input
- [0,0,null,0,0]
- Output
- 1
- Why
- One camera at the left child node monitors all nodes: the root, itself, and its two children.
Example 2
- Input
- [0,0,null,0,null,0,null,null,0]
- Output
- 2
- Why
- Two cameras are needed to monitor all nodes in this elongated tree.
Example 3
- Input
- [0]
- Output
- 1
- Why
- A single node requires one camera to monitor itself.
Constraints
- The number of nodes is in the range [1, 1000].
- Node.val is 0.
How to think about it
Updated 2026-09-09Placing a camera on a leaf is the worst possible choice because its coverage can only reach its parent. Cameras should be placed on parents of uncovered nodes. Work bottom-up from the leaves using three states: needs camera (0), has camera (1), and covered (2).
Approaches, worst first
Tree dynamic programming
time O(n) · space O(h)
Define states for each node: `(dp0, dp1, dp2)` where dp0 is min cameras with node unmonitored, dp1 is monitored with camera at node, dp2 is monitored without camera. Compute transition equations combining child states.
Greedy bottom-up tri-state DFSWrite this one
time O(n) · space O(h)
Return 2 for null. For any node, recurse into children. If either child returns 0 (needs coverage), place a camera here (increment count, return 1). If either child returns 1 (has camera), this node is covered (return 2). Otherwise return 0. If the root evaluates to 0 at the end, add one last camera.
Where people lose marks · 3
- Forgetting to check the root after the postorder traversal finishes: if the root returns state 0 (uncovered), an additional camera must be placed at the root.
- Treating null nodes as uncovered (state 0) forces unnecessary cameras onto leaf nodes; null nodes must be treated as already covered (state 2).
- Top-down greedy choices fail because placing cameras at the root cannot anticipate leaf parity deep in subtrees.
The theory behind it
Binary Trees — the ground this problem stands on. All Binary Trees problems
What Binary Trees is
A binary tree is a branching data structure that starts at a single top node called the root, like an upside-down family tree. Every node holds a piece of data and can branch out to at most two children below it, known as the left child and the right child. Because there is no ordering rule about which values go left or right, finding a specific item can require checking every single node in the entire tree.
When to reach for it
Reach for binary trees when problems present hierarchical data with left and right child pointers. Questions asking for tree height, maximum depth, path sums from root to leaf, diameter, lowest common ancestor, or checking whether two trees are mirror reflections of each other all signal binary tree traversals. Any problem asking to inspect or reconstruct a tree layer by layer or path by path belongs here.
How the pattern works
Think recursively by focusing on what a single node must do. If the current node is null, return the base answer immediately. Otherwise, ask the left child for its result, ask the right child for its result, and combine both answers with the current node value before returning up to the parent. For horizontal scans, use a queue to read nodes layer by layer, measuring the queue length at the start of each layer to group nodes by depth.
What each operation costs
| Operation | Time |
|---|---|
| traverse all nodes using recursion or queue | O(n) |
| search for an arbitrary value in an unordered tree | O(n) |
| call stack memory on balanced tree | O(log n) |
| call stack memory on skewed tree | O(n) |
What usually goes wrong with Binary Trees
- Dereferencing left or right child pointers without checking if the current node is null, throwing null pointer errors on empty trees or leaf nodes.
- Defining a leaf node incorrectly by stopping when either child is null instead of checking that both left and right children are simultaneously null.
- Computing tree diameter by taking left height plus right height inside a recursive helper without updating a global maximum across every visited node.
Which roles need this problem
Binary Trees is a core topic for these 4 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 5 more roles, including Full-Stack Developer, Android Developer, iOS Developer.
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 Binary Trees problems
Problem set and role mapping as of .