Dequeue Using Linked List in DSA Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Dequeue (Double Ended Queue)?

A Dequeue is a data structure where elements can be added or removed from both the front and the rear ends.

beginner

Why use a linked list to implement a Dequeue?

A linked list allows efficient insertion and deletion at both ends without shifting elements, unlike arrays.

beginner

What are the main operations of a Dequeue using a linked list?

InsertFront, InsertRear, DeleteFront, DeleteRear, and Display.

intermediate

How does DeleteRear work in a singly linked list based Dequeue?

You traverse to the second last node, remove the last node, and update the second last node's next pointer to null.

intermediate

What is the time complexity of InsertFront and InsertRear in a linked list based Dequeue?

Both InsertFront and InsertRear operations take O(1) time if you maintain pointers to both ends.

Which operation is NOT supported by a Dequeue?

A Delete from front

B Delete from rear

C Insert at front

D Insert at middle

Dequeue supports insertion and deletion only at the front and rear ends, not in the middle.

What is the advantage of using a linked list for Dequeue over an array?

A Fixed size

B Dynamic size and no shifting needed

C Faster random access

D Uses less memory always

Linked lists allow dynamic size and efficient insertions/deletions at both ends without shifting elements.

In a singly linked list Dequeue, what is needed to efficiently delete from the rear?

A Pointer to the second last node

B Pointer to the front node

C Pointer to the last node only

D No pointers needed

To delete the rear node, you need to update the second last node's next pointer to null.

What is the time complexity of deleting from the front in a linked list Dequeue?

A O(log n)

B O(n)

C O(1)

D O(n^2)

Deleting from the front is O(1) because you just move the front pointer to the next node.

Which pointer(s) should be maintained for efficient Dequeue operations?

A Both front and rear pointers

B Only rear pointer

C No pointers needed

D Only front pointer

Maintaining both front and rear pointers allows O(1) insertion and deletion at both ends.

Explain how insertion at the front and deletion at the rear work in a Dequeue implemented using a linked list.

Think about how nodes connect and how pointers move.

Describe the advantages of using a linked list for implementing a Dequeue compared to an array.

Consider flexibility and operation costs.

Practice

1. What is the main advantage of using a linked list to implement a Dequeue compared to using an array?

easy

A. It uses less memory than arrays in all cases.

B. It allows dynamic memory allocation and easy insertion/deletion at both ends.

C. It provides faster access to elements by index.

D. It automatically sorts elements when inserted.

Solution

1. Step 1: Understand linked list properties

   A linked list can grow or shrink dynamically without fixed size limits.

2. Step 2: Compare with array limitations

   Arrays have fixed size and inserting/deleting at ends may require shifting elements, which is costly.

3. Final Answer:

   It allows dynamic memory allocation and easy insertion/deletion at both ends. -> Option B

4. Quick Check:

   Linked list dynamic size = Advantage [OK]

Hint: Linked list grows dynamically, arrays have fixed size [OK]

Common Mistakes:

• Thinking arrays always use less memory
• Confusing access speed with insertion speed
• Assuming linked list sorts elements automatically

2. Which of the following is the correct way to declare a node class for a doubly linked list used in a dequeue in Java?

easy

A. class Node { int data; Node next; }

B. class Node { int data; Node prev; }

C. class Node { int data; Node left; Node right; }

D. class Node { int data; Node next; Node prev; }

Solution

1. Step 1: Identify node requirements for dequeue

   A dequeue needs to insert/delete at both ends, so nodes must link forward and backward.

2. Step 2: Check node class fields

   Only class Node { int data; Node next; Node prev; } has both next and prev pointers for doubly linked list.

3. Final Answer:

   class Node { int data; Node next; Node prev; } -> Option D

4. Quick Check:

   Doubly linked list node = next + prev [OK]

Hint: Doubly linked list nodes have next and prev pointers [OK]

Common Mistakes:

• Using single pointer nodes for dequeue
• Confusing binary tree node pointers with linked list
• Omitting prev pointer needed for backward traversal

3. What will be the output after performing these operations on an empty dequeue implemented using a linked list?

dequeue.insertFront(10);
dequeue.insertRear(20);
dequeue.insertFront(5);
dequeue.deleteRear();
dequeue.display();

medium

A. 5 -> 10 -> null

B. 10 -> 5 -> null

C. 5 -> 20 -> null

D. 10 -> null

Solution

1. Step 1: Perform insertFront(10) and insertRear(20)

   List becomes: 10 -> 20 -> null

2. Step 2: Perform insertFront(5)

   List becomes: 5 -> 10 -> 20 -> null

3. Step 3: Perform deleteRear()

   Removes 20, list becomes: 5 -> 10 -> null

4. Step 4: Display list

   Output is 5 -> 10 -> null

5. Final Answer:

   5 -> 10 -> null -> Option A

6. Quick Check:

   Front insertions add left, rear deletion removes right [OK]

Hint: Track insertFront and insertRear positions carefully [OK]

Common Mistakes:

• Deleting front instead of rear
• Mixing order of insertions
• Forgetting to update pointers after deletion

4. Consider this buggy method to delete from the front of a dequeue implemented using a linked list:

public void deleteFront() {
  if (front == null) {
    System.out.println("Dequeue is empty");
    return;
  }
  front = front.next;
  front.prev = null;
}

What error can occur when this method is called on a dequeue with only one element?

medium

A. NullPointerException when setting front.prev = null

B. ArrayIndexOutOfBoundsException

C. No error, method works fine

D. Infinite loop in linked list

Solution

1. Step 1: Analyze deleteFront on single element list

   If only one node, after front = front.next, front becomes null.

2. Step 2: Check next line front.prev = null

   Since front is null, accessing front.prev causes NullPointerException.

3. Final Answer:

   NullPointerException when setting front.prev = null -> Option A

4. Quick Check:

   Accessing null pointer causes NullPointerException [OK]

Hint: Check for null before accessing front.prev [OK]

Common Mistakes:

• Assuming front is never null after deletion
• Ignoring edge case of single element
• Confusing exception types

5. You want to implement a dequeue using a linked list that supports these operations efficiently:
1. Insert at front
2. Insert at rear
3. Delete from front
4. Delete from rear
5. Get size of dequeue

Which data members should your dequeue class maintain to achieve all operations in O(1) time?

hard

A. Pointer to rear node only, no size counter

B. Pointer to front node only, and an integer size counter

C. Pointers to front and rear nodes, and an integer size counter

D. Array to store elements and a size counter

Solution

1. Step 1: Identify pointers needed for O(1) insert/delete at both ends

   We need both front and rear pointers to access both ends directly.

2. Step 2: Identify how to get size in O(1)

   Maintain an integer size counter updated on each insert/delete.

3. Final Answer:

   Pointers to front and rear nodes, and an integer size counter -> Option C

4. Quick Check:

   Front + rear pointers + size counter = O(1) ops [OK]

Hint: Keep front, rear pointers and size counter for O(1) operations [OK]

Common Mistakes:

• Using only one pointer for both ends
• Not maintaining size counter for quick size retrieval
• Using array instead of linked list for dequeue