A hash table is a data structure that stores key-value pairs. It uses a hash function to convert keys into an index where the value is stored, allowing fast data retrieval.
Click to reveal answer
beginner
What is the role of a hash function in a hash table?
A hash function takes a key and returns an integer index. This index tells where to store or find the value in the hash table.
Click to reveal answer
intermediate
Why do hash tables sometimes have collisions?
Collisions happen when two different keys produce the same index from the hash function. The hash table must handle collisions to store both values correctly.
Click to reveal answer
intermediate
Name one common method to handle collisions in hash tables.
One common method is chaining, where each index holds a list of key-value pairs. If multiple keys hash to the same index, they are stored in the list at that index.
Click to reveal answer
intermediate
What qualities make a good hash function?
A good hash function distributes keys evenly across the table, is fast to compute, and minimizes collisions.
Click to reveal answer
What does a hash function do in a hash table?
ASorts the keys alphabetically
BStores the value directly
CConverts a key into an index
DDeletes duplicate keys
✗ Incorrect
A hash function converts a key into an index where the value is stored or retrieved.
What is a collision in a hash table?
AWhen two keys produce the same index
BWhen a key is missing
CWhen the table is empty
DWhen values are duplicated
✗ Incorrect
A collision occurs when two different keys hash to the same index.
Which method can handle collisions by storing multiple items at one index?
AChaining
BSorting
CBinary search
DHashing again
✗ Incorrect
Chaining stores multiple key-value pairs in a list at the same index to handle collisions.
Why is it important for a hash function to distribute keys evenly?
ATo sort keys alphabetically
BTo make keys look random
CTo use less memory
DTo reduce collisions and improve speed
✗ Incorrect
Even distribution reduces collisions and makes data retrieval faster.
What is stored in a hash table?
ASorted lists
BKey-value pairs
COnly values
DOnly keys
✗ Incorrect
Hash tables store key-value pairs for quick lookup.
Explain how a hash table uses a hash function to store and retrieve data.
Think about how keys become positions in the table.
You got /4 concepts.
Describe what a collision is in a hash table and one way to handle it.
Imagine two friends trying to sit in the same chair.
You got /4 concepts.
Practice
(1/5)
1. What is the main purpose of a hash function in a hash table?
easy
A. To sort the keys in ascending order
B. To convert a key into an index for storing values
C. To encrypt the data stored in the table
D. To count the number of elements in the table
Solution
Step 1: Understand the role of a hash function
A hash function takes a key and converts it into a number that can be used as an index in the hash table.
Step 2: Identify the correct purpose
This index helps to quickly find where the value related to the key is stored.
Final Answer:
To convert a key into an index for storing values -> Option B
Quick Check:
Hash function = key to index [OK]
Hint: Hash function maps keys to indexes fast [OK]
Common Mistakes:
Thinking hash functions sort keys
Confusing hashing with encryption
Believing hash functions count elements
2. Which of the following is the correct way to declare a hash map in Rust?
easy
A. let mut map = HashMap::new();
B. let map = new HashMap();
C. HashMap map = new HashMap();
D. var map = HashMap();
Solution
Step 1: Recall Rust syntax for hash maps
In Rust, hash maps are created using HashMap::new() and usually declared mutable with let mut.
Step 2: Check each option
let mut map = HashMap::new(); uses correct Rust syntax. Options A, B, and C use syntax from other languages or incorrect Rust syntax.
Using syntax from other languages like Java or JavaScript
Forgetting to make the map mutable
Missing the HashMap:: prefix
3. What will be the output of the following Rust code?
use std::collections::HashMap;
fn main() {
let mut map = HashMap::new();
map.insert("apple", 3);
map.insert("banana", 2);
map.insert("apple", 5);
println!("{:?}", map.get("apple"));
}
medium
A. Error: duplicate key
B. Some(3)
C. None
D. Some(5)
Solution
Step 1: Understand insert behavior in HashMap
In Rust's HashMap, inserting a value with an existing key replaces the old value.
Step 2: Trace the inserts and get
First insert: "apple" -> 3, second insert: "banana" -> 2, third insert: "apple" -> 5 replaces 3. So map.get("apple") returns Some(5).
Final Answer:
Some(5) -> Option D
Quick Check:
Last insert replaces value = Some(5) [OK]
Hint: Last insert with same key overwrites value [OK]
Common Mistakes:
Assuming duplicate keys cause error
Thinking old value remains after insert
Expecting None for existing key
4. Identify the error in this Rust code snippet using a hash map:
use std::collections::HashMap;
fn main() {
let map = HashMap::new();
map.insert("key", 10);
println!("{:?}", map.get("key"));
}
medium
A. HashMap is not imported
B. get method does not exist
C. map is immutable but insert is called
D. Missing semicolon after insert
Solution
Step 1: Check mutability of map
The map is declared with let (immutable) but insert tries to modify it.
Step 2: Identify the error cause
In Rust, to modify a HashMap, it must be declared mutable with let mut.
Final Answer:
map is immutable but insert is called -> Option C
Quick Check:
Insert needs mutable map [OK]
Hint: Use let mut for hash maps you modify [OK]
Common Mistakes:
Forgetting to import HashMap
Assuming get method is missing
Thinking semicolon is missing
5. You want to create a hash function for strings that sums the ASCII values of characters and then takes modulo with table size. Which of these Rust functions correctly implements this?
hard
A. fn hash(key: &str, size: usize) -> usize { key.bytes().map(|b| b as usize).sum::<usize>() % size }
The function must sum ASCII values of all characters and then take modulo with size.
Step 2: Analyze each option
fn hash(key: &str, size: usize) -> usize { key.bytes().map(|b| b as usize).sum::<usize>() % size } sums bytes (ASCII values) and mods by size correctly. Options A, B, and D only use length or count, not sum of ASCII values.
Final Answer:
fn hash(key: &str, size: usize) -> usize { key.bytes().map(|b| b as usize).sum::<usize>() % size } -> Option A
Quick Check:
Sum ASCII bytes then mod size = fn hash(key: &str, size: usize) -> usize { key.bytes().map(|b| b as usize).sum::<usize>() % size } [OK]
Hint: Sum bytes, then modulo table size for hash [OK]
Common Mistakes:
Using length instead of sum of ASCII values
Using chars count instead of bytes
Forgetting to modulo by table size
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.