Why Linked List Exists and What Problem It Solves in DSA Go - Test Your Knowledge

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a linked list node struct in Go.

DSA Go

type Node struct {
	value int
	next [1]
}

Drag options to blanks, or click blank then click option'

ANode

B*Node

Cint

Dstring

Attempts:

3 left

💡 Hint

Common Mistakes

Using Node instead of *Node causes infinite size error.

Using int or string for next is incorrect.

In Go, a linked list node points to the next node using a pointer to Node, written as *Node.

2fill in blank

medium

Complete the code to add a new node at the beginning of a linked list.

DSA Go

func prepend(head *Node, val int) *Node {
	newNode := &Node{value: val, next: [1]
	return newNode
}

Drag options to blanks, or click blank then click option'

Anil

B&head

Chead

D*head

Attempts:

3 left

💡 Hint

Common Mistakes

Setting next to nil loses the existing list.

Using &head or *head is incorrect pointer usage.

The new node's next should point to the current head to insert at the beginning.

3fill in blank

hard

Fix the error in the code to traverse a linked list and print values.

DSA Go

func printList(head *Node) {
	current := head
	for current != [1] {
		fmt.Println(current.value)
		current = current.next
	}
}

Drag options to blanks, or click blank then click option'

Anil

Bhead

Ccurrent

Dnext

Attempts:

3 left

💡 Hint

Common Mistakes

Using head or current as condition causes infinite loop.

Using next is undefined in this scope.

The loop should continue until current is nil, meaning end of list.

4fill in blank

hard

Fill both blanks to create a linked list with three nodes and link them.

DSA Go

node1 := &Node{value: 1, next: [1]
node2 := &Node{value: 2, next: [2]
node3 := &Node{value: 3, next: nil}

Drag options to blanks, or click blank then click option'

Anode2

Bnode3

Cnil

D&node3

Attempts:

3 left

💡 Hint

Common Mistakes

Using &node3 is incorrect because node3 is already a pointer.

Setting node2.next to nil leaves node3 unlinked.

node1.next points to node2, node2.next points to node3 to link all three nodes, with node3.next already nil.

5fill in blank

hard

Fill all three blanks to insert a new node with value 4 after node2.

DSA Go

newNode := &Node{value: 4, next: [1]
node2.next = [2]
head := [3]

Drag options to blanks, or click blank then click option'

Anode2.next

BnewNode

Cnode1

Dnode3

Attempts:

3 left

💡 Hint

Common Mistakes

Setting newNode.next to node3 directly breaks list if node2.next was different.

Assigning head incorrectly changes list start.

newNode.next points to node2.next, node2.next updated to newNode, head remains node1.

Practice

1. Why do we use a linked list instead of an array in some cases?

easy

A. Because linked lists allow easy insertion and deletion without shifting elements

B. Because linked lists use less memory than arrays always

C. Because linked lists provide faster access to elements by index

D. Because linked lists store elements in contiguous memory locations

Solution

1. Step 1: Understand array limitations

   Arrays store elements in contiguous memory, so inserting or deleting elements requires shifting others, which is slow.

2. Step 2: Understand linked list advantages

   Linked lists store elements in nodes linked by pointers, so insertion and deletion can be done by changing pointers without shifting.

3. Final Answer:

   Because linked lists allow easy insertion and deletion without shifting elements -> Option A

4. Quick Check:

   Insertion/deletion ease = C [OK]

Hint: Linked lists excel at insert/delete without shifting [OK]

Common Mistakes:

• Thinking linked lists always use less memory
• Believing linked lists have faster index access
• Assuming linked lists store data contiguously

2. Which of the following is the correct way to declare a node struct for a singly linked list in Go?

easy

A. type Node struct { data int; next **Node }

B. type Node struct { data int; next Node }

C. type Node struct { data *int; next *Node }

D. type Node struct { data int; next *Node }

Solution

1. Step 1: Understand pointer usage in Go structs

   For linked lists, the next field must be a pointer to the next node to avoid copying the whole struct.

2. Step 2: Check each option

   type Node struct { data int; next *Node } uses *Node pointer correctly; B uses Node (value) which causes copying; C uses *int for data which is unnecessary; D uses **Node which is double pointer and unnecessary.

3. Final Answer:

   type Node struct { data int; next *Node } -> Option D

4. Quick Check:

   Next pointer = *Node [OK]

Hint: Next node must be a pointer to avoid copying [OK]

Common Mistakes:

• Using value type instead of pointer for next
• Using pointer for data unnecessarily
• Using double pointer for next

3. What will be the output of the following Go code snippet that creates a linked list and prints its elements?

type Node struct {
    data int
    next *Node
}

func main() {
    head := &Node{data: 1}
    second := &Node{data: 2}
    third := &Node{data: 3}
    head.next = second
    second.next = third

    current := head
    for current != nil {
        fmt.Print(current.data, " -> ")
        current = current.next
    }
    fmt.Print("null")
}

medium

A. 3 -> 2 -> 1 -> null

B. 1 -> 2 -> 3 -> null

C. 1 -> 2 -> null

D. Compilation error

Solution

1. Step 1: Trace linked list creation

   Nodes created with data 1, 2, 3 linked in order: head -> second -> third.

2. Step 2: Trace printing loop

   Loop prints data of current node then moves to next until nil, so prints 1, 2, 3 in order, then prints "null".

3. Final Answer:

   1 -> 2 -> 3 -> null -> Option B

4. Quick Check:

   Print order matches linked list order [OK]

Hint: Follow next pointers to print nodes in order [OK]

Common Mistakes:

• Confusing order of nodes
• Forgetting to print null at end
• Assuming reverse order

4. The following Go code tries to insert a new node with value 4 after the head node in a linked list. What is the bug?

type Node struct {
    data int
    next *Node
}

func main() {
    head := &Node{data: 1}
    second := &Node{data: 2}
    head.next = second

    newNode := &Node{data: 4}
    newNode.next = head.next
    head = newNode
}

medium

A. No bug; code works correctly

B. The newNode.next should be nil

C. The new node is not linked correctly; head pointer is overwritten

D. The second node is lost because head.next is nil

Solution

1. Step 1: Understand intended insertion

   The goal is to insert newNode after head, so newNode.next should point to head.next, then head.next should point to newNode.

2. Step 2: Identify bug in code

   The code sets newNode.next = head.next correctly but then overwrites head pointer itself with newNode, losing original head node and breaking list.

3. Final Answer:

   The new node is not linked correctly; head pointer is overwritten -> Option C

4. Quick Check:

   Head pointer changed incorrectly = D [OK]

Hint: Insert by changing next pointers, not head itself [OK]

Common Mistakes:

• Overwriting head instead of head.next
• Not linking newNode.next properly
• Assuming newNode.next should be nil

5. You want to implement a playlist where songs can be added or removed anywhere efficiently. Why is a linked list a better choice than an array for this use case?

hard

A. Because linked lists allow dynamic memory allocation and efficient insertions/removals anywhere

B. Because linked lists provide faster random access to songs by index

C. Because arrays automatically resize without overhead

D. Because linked lists store all songs contiguously in memory

Solution

1. Step 1: Understand playlist operations

   Adding/removing songs anywhere means frequent insertions and deletions at arbitrary positions.

2. Step 2: Compare array and linked list

   Arrays require shifting elements on insert/delete, which is slow. Linked lists use pointers to insert/delete nodes efficiently without shifting.

3. Final Answer:

   Because linked lists allow dynamic memory allocation and efficient insertions/removals anywhere -> Option A

4. Quick Check:

   Efficient insert/delete = A [OK]

Hint: Linked lists excel at dynamic insertions/removals [OK]

Common Mistakes:

• Thinking linked lists have faster random access
• Assuming arrays resize without cost
• Believing linked lists store data contiguously