Tree Traversal Postorder Left Right Root in DSA Go - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the order of visiting nodes in Postorder Tree Traversal?

In Postorder traversal, nodes are visited in the order: Left subtree, Right subtree, then Root node.

intermediate

Why is Postorder traversal useful in deleting a tree?

Postorder traversal visits children before the parent, so it safely deletes all child nodes before deleting the parent node.

beginner

Given a binary tree, what will be the Postorder traversal output for this tree?
Root: 1
Left child: 2
Right child: 3

The Postorder traversal visits Left (2), Right (3), then Root (1). So output is: 2 -> 3 -> 1

beginner

Show the Go function signature for a recursive Postorder traversal of a binary tree node.

func postorderTraversal(root *TreeNode) { // implementation }

beginner

What is the main difference between Inorder and Postorder traversal?

Inorder visits nodes in Left, Root, Right order, while Postorder visits nodes in Left, Right, Root order.

In Postorder traversal, which node is visited last?

A Right child

B Left child

C Root node

D None of the above

Postorder visits Left subtree, then Right subtree, and finally the Root node.

What is the Postorder traversal of a tree with root 5, left child 3, and right child 7?

A 3 -> 7 -> 5

B 3 -> 5 -> 7

C 7 -> 3 -> 5

D 5 -> 3 -> 7

Postorder visits Left (3), Right (7), then Root (5).

Which traversal is best suited for deleting all nodes in a tree safely?

A Preorder

B Postorder

C Inorder

D Level order

Postorder visits children before the parent, so it deletes safely.

In Postorder traversal, what is the first subtree visited?

A Left subtree

B Root node

C Right subtree

D None

Postorder starts with the Left subtree.

Which of these is the correct Postorder traversal output for this tree?
Root: 10
Left child: 5
Right child: 15

A 5 -> 10 -> 15

B 10 -> 5 -> 15

C 15 -> 10 -> 5

D 5 -> 15 -> 10

Postorder visits Left (5), Right (15), then Root (10).

Explain the steps of Postorder traversal on a binary tree.

Think about visiting children before the parent.

Describe a real-life scenario where Postorder traversal is useful.

Consider tasks that require finishing all parts before the whole.

Practice

1. What is the order of nodes visited in a postorder tree traversal?

easy

A. Root node, Right subtree, Left subtree

B. Root node, Left subtree, Right subtree

C. Left subtree, Right subtree, Root node

D. Right subtree, Left subtree, Root node

Solution

1. Step 1: Understand postorder traversal definition

   Postorder traversal visits the left subtree first, then the right subtree, and finally the root node.

2. Step 2: Match the order with options

   Left subtree, Right subtree, Root node matches the order Left, Right, Root exactly.

3. Final Answer:

   Left subtree, Right subtree, Root node -> Option C

4. Quick Check:

   Postorder = Left, Right, Root [OK]

Hint: Remember postorder ends with root after children [OK]

Common Mistakes:

• Confusing postorder with preorder or inorder
• Visiting root before children
• Swapping left and right subtree order

2. Which of the following Go function signatures correctly represents a recursive postorder traversal of a binary tree node root?

easy

A. func postorder(root *Node) { postorder(root.Left); postorder(root.Right); fmt.Println(root.Value) }

B. func postorder(root *Node) { fmt.Println(root.Value); postorder(root.Left); postorder(root.Right) }

C. func postorder(root *Node) { postorder(root.Right); postorder(root.Left); fmt.Println(root.Value) }

D. func postorder(root *Node) { fmt.Println(root.Value); postorder(root.Right); postorder(root.Left) }

Solution

1. Step 1: Recall postorder traversal steps

   Postorder visits left subtree, then right subtree, then root node.

2. Step 2: Check function calls and print order

   func postorder(root *Node) { postorder(root.Left); postorder(root.Right); fmt.Println(root.Value) } calls postorder on left, then right, then prints root value, matching postorder.

3. Final Answer:

   func postorder(root *Node) { postorder(root.Left); postorder(root.Right); fmt.Println(root.Value) } -> Option A

4. Quick Check:

   Calls: Left, Right, Print root [OK]

Hint: Print root after recursive calls to left and right [OK]

Common Mistakes:

• Printing root before recursive calls
• Swapping left and right recursive calls
• Missing recursive calls for subtrees

3. Given the binary tree below, what is the output of the postorder traversal?

      1
     / \
    2   3
   / \
  4   5

func postorder(root *Node) { if root == nil { return } postorder(root.Left) postorder(root.Right) fmt.Print(root.Value, " ") }

medium

A. 4 2 5 3 1

B. 1 2 4 5 3

C. 2 4 5 3 1

D. 4 5 2 3 1

Solution

1. Step 1: Traverse left subtree of root (1)

   Left subtree is rooted at 2. Postorder of subtree 2 is: left(4), right(5), root(2) -> 4 5 2.

2. Step 2: Traverse right subtree and root

   Right subtree is 3 (leaf), so output 3. Then print root 1 last.

3. Final Answer:

   4 5 2 3 1 -> Option D

4. Quick Check:

   Postorder = Left, Right, Root = 4 5 2 3 1 [OK]

Hint: Visit left subtree fully, then right, then root [OK]

Common Mistakes:

• Printing root before children
• Mixing left and right subtree order
• Skipping leaf nodes

4. The following Go code attempts a postorder traversal but produces incorrect output. What is the error?

func postorder(root *Node) {
  if root == nil {
    return
  }
  postorder(root.Right)
  postorder(root.Left)
  fmt.Print(root.Value, " ")
}

medium

A. The order of recursive calls is swapped; left should be before right

B. The base case is missing for nil nodes

C. The root value should be printed before recursive calls

D. The function should return a slice instead of printing

Solution

1. Step 1: Analyze recursive call order

   The code calls postorder on right subtree first, then left subtree, which reverses the expected order.

2. Step 2: Recall correct postorder sequence

   Postorder requires left subtree first, then right subtree, then root. Swapping left and right causes wrong output.

3. Final Answer:

   The order of recursive calls is swapped; left should be before right -> Option A

4. Quick Check:

   Left before Right in postorder [OK]

Hint: Left subtree call must come before right subtree call [OK]

Common Mistakes:

• Swapping left and right subtree calls
• Printing root before children
• Ignoring base case for nil

5. You want to collect the values of a binary tree in postorder traversal into a slice instead of printing. Which Go function correctly implements this?

hard

A. func postorder(root *Node, res *[]int) {
if root == nil {
return
}
postorder(root.Right, res)
postorder(root.Left, res)
*res = append(*res, root.Value)
}

B. func postorder(root *Node) []int {
if root == nil {
return []int{}
}
left := postorder(root.Left)
right := postorder(root.Right)
return append(left, append(right, root.Value)...)
}

C. func postorder(root *Node, res *[]int) {
if root == nil {
return
}
*res = append(*res, root.Value)
postorder(root.Left, res)
postorder(root.Right, res)
}

D. func postorder(root *Node) []int {
if root == nil {
return nil
}
return []int{root.Value}
}

Solution

1. Step 1: Understand collecting values in slice recursively

   We want a function returning a slice with postorder values: left subtree slice + right subtree slice + root value.

2. Step 2: Check each option for correct order and slice handling

   func postorder(root *Node) []int { if root == nil { return []int{} } left := postorder(root.Left) right := postorder(root.Right) return append(left, append(right, root.Value)...) } correctly returns left slice, then appends right slice, then root value, matching postorder traversal.

3. Final Answer:

   func postorder(root *Node) []int { if root == nil { return []int{} } left := postorder(root.Left) right := postorder(root.Right) return append(left, append(right, root.Value)...) } -> Option B

4. Quick Check:

   Return slices: left + right + root [OK]

Hint: Return left + right + root slices combined [OK]

Common Mistakes:

• Appending root before children slices
• Not combining slices correctly
• Returning nil instead of empty slice for nil node