Question

A developer at a financial firm replaced a Binary Search Tree (BS

  • D became significantly faster, but range-based queries (e.g., fetch all transactions between ₹10,000 and ₹50,000) became drastically slower. What is the most likely reason for this degradation?
  • T based search index with a Hash Table based index to improve lookup performance. After deployment, point lookups (e.g., fetch record by I
A Hash Tables have higher memory usage than BSTs, causing RAM overflow and slowing range queries
B BSTs use recursion internally which is faster than the iterative approach of Hash Tables for range queries
C Hash functions destroy the natural ordering of keys, making it impossible to efficiently locate all keys within a range without scanning the entire table
D Hash Tables do not support duplicate keys, and the range query contained duplicate transaction amounts causing collisions
E Hash Tables cannot be used as a search index
Practice Next

Hey! Ask a query

🎓
Think You're Ready for RBI Grade B?
RBI Grade B 2026 Phase 1 Memory Based Paper
  • 200 Questions with Detailed Solutions
  • Section-wise Coverage (GA, English, Quant & Reasoning)