Why Searching in BST in Data Structures Theory? - Purpose & Use Cases

The Big Idea

What if you could find any name in a giant list almost instantly without flipping every page?

The Scenario

Imagine you have a huge phone book with thousands of names sorted alphabetically. You want to find one person's phone number, but you start flipping pages from the beginning one by one.

The Problem

This manual way is very slow and tiring. You waste a lot of time checking every name, and it's easy to lose your place or make mistakes.

The Solution

Searching in a Binary Search Tree (BST) is like using a smart method to find names quickly. Because the tree keeps data sorted, you can skip large parts and jump closer to the answer fast.

Before vs After

✗ Before

for name, number in phone_book:
    if name == target:
        return number
return not_found

✓ After

node = root
while node:
    if target == node.value:
        return node.data
    elif target < node.value:
        node = node.left
    else:
        node = node.right
return not_found

What It Enables

It enables lightning-fast searches even in huge collections by cutting down the work step-by-step.

Real Life Example

When you search for a contact on your phone, the system uses a method like BST search to find the number instantly instead of checking every contact one by one.

Key Takeaways

Manual searching is slow and error-prone for large sorted data.

BST searching uses order to jump directly to the target area.

This method saves time and effort, making searches efficient.

Practice

1. What is the main advantage of searching in a Binary Search Tree (BST)?

easy

A. It allows faster search by using the order of elements

B. It stores elements in random order for quick access

C. It uses hashing to find elements instantly

D. It searches all nodes one by one sequentially

Solution

1. Step 1: Understand BST property

   A BST keeps elements ordered so smaller values are on the left and larger on the right.

2. Step 2: Use order for searching

   This order lets us decide to go left or right, skipping half the tree each step, making search faster.

3. Final Answer:

   It allows faster search by using the order of elements -> Option A

4. Quick Check:

   BST order speeds search = It allows faster search by using the order of elements [OK]

Hint: BST order guides search direction quickly [OK]

Common Mistakes:

• Thinking BST stores elements randomly
• Confusing BST with hashing
• Assuming linear search in BST

2. Which of the following is the correct way to decide the next node to visit when searching for a value in a BST?

easy

A. Go left if target is greater than current node

B. Go left if target is smaller than current node

C. Go right if target is smaller than current node

D. Always go to the root node

Solution

1. Step 1: Recall BST search rule

   If the target is smaller than the current node's value, we move to the left child.

2. Step 2: Apply rule to options

   Go left if target is smaller than current node correctly states to go left if target is smaller, which matches BST property.

3. Final Answer:

   Go left if target is smaller than current node -> Option B

4. Quick Check:

   Smaller target -> left child = Go left if target is smaller than current node [OK]

Hint: Smaller target means go left in BST [OK]

Common Mistakes:

• Reversing left and right directions
• Ignoring BST ordering rules
• Always going to root node

3. Consider the BST below:

      15
     /  \
    10  20
   /    / \
  8    17 25

Which nodes will be visited when searching for the value 17?

medium

A. [10, 8, 17]

B. [15, 10, 8]

C. [15, 20, 25]

D. [15, 20, 17]

Solution

1. Step 1: Start at root and compare with 17

   Root is 15. Since 17 > 15, move right to 20.

2. Step 2: Compare 20 with 17

   17 < 20, so move left to 17, which matches the target.

3. Final Answer:

   [15, 20, 17] -> Option D

4. Quick Check:

   Path to 17 = 15 -> 20 -> 17 [OK]

Hint: Follow BST rules: left if smaller, right if larger [OK]

Common Mistakes:

• Going left from 15 when target is larger
• Skipping nodes in path
• Confusing node values

4. You wrote code to search a BST but it always returns None even when the value exists. What is the most likely mistake?

medium

A. Not moving to left child when target is smaller

B. Using a queue instead of recursion

C. Always moving to left child regardless of target

D. Checking only the root node

Solution

1. Step 1: Understand BST search logic

   Search must move left if target is smaller, right if larger.

2. Step 2: Identify error in always moving left

   If code always moves left, it misses nodes on the right side where target might be.

3. Final Answer:

   Always moving to left child regardless of target -> Option C

4. Quick Check:

   Wrong direction causes search failure = Always moving to left child regardless of target [OK]

Hint: Move left or right based on comparison, not always left [OK]

Common Mistakes:

• Ignoring right subtree
• Checking only root node
• Using wrong data structure for traversal

5. Given a BST where some nodes have duplicate values on the right subtree, how should the search algorithm be adapted to find all occurrences of a target value?

hard

A. Traverse both left and right subtrees when node equals target

B. Search left subtree only once target is found

C. Stop search immediately after first match

D. Ignore duplicates and return first found

Solution

1. Step 1: Understand duplicates in BST

   Duplicates are stored in right subtree, so multiple matches can exist there.

2. Step 2: Adapt search to find all matches

   When a node equals target, search both left (for smaller) and right (for duplicates) subtrees to find all occurrences.

3. Final Answer:

   Traverse both left and right subtrees when node equals target -> Option A

4. Quick Check:

   Check both sides for duplicates = Traverse both left and right subtrees when node equals target [OK]

Hint: Check both subtrees when value matches to find duplicates [OK]

Common Mistakes:

• Stopping after first match
• Ignoring right subtree duplicates
• Searching only one subtree