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

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a pointer to the next node in a linked list node structure.

DSA C

struct Node {
    int data;
    struct Node* [1];
};

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

Anext

Bprev

Clink

Dpointer

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'prev' which is for doubly linked lists.

Using generic names like 'pointer' which are unclear.

The pointer to the next node in a linked list is commonly named next.

2fill in blank

medium

Complete the code to create a new node dynamically in a linked list.

DSA C

struct Node* newNode = (struct Node*) malloc(sizeof([1]));

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

Astruct

BNode

Cnode

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'node' which is undefined.

Using 'int' which is the wrong type.

We allocate memory for a Node structure, so sizeof(Node) is correct.

3fill in blank

hard

Fix the error in the code to properly link a new node to the existing linked list.

DSA C

newNode->[1] = head;

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

Apointer

Bprev

Clink

Dnext

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'prev' which is for doubly linked lists.

Using undefined pointer names like 'link' or 'pointer'.

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

4fill in blank

hard

Fill both blanks to complete the function that inserts a new node at the beginning of the linked list.

DSA C

void insertAtFront(struct Node** head_ref, int new_data) {
    struct Node* newNode = (struct Node*) malloc(sizeof([1]));
    newNode->data = new_data;
    newNode->[2] = *head_ref;
    *head_ref = newNode;
}

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

ANode

Bnode

Cnext

Dprev

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'node' which is undefined.

Using 'prev' which is for doubly linked lists.

Memory is allocated for a Node, and the new node's next pointer is set to the current head.

5fill in blank

hard

Fill all three blanks to complete the function that prints all elements of a linked list.

DSA C

void printList(struct Node* [1]) {
    struct Node* [2] = [3];
    while (temp != NULL) {
        printf("%d -> ", temp->data);
        temp = temp->next;
    }
    printf("NULL\n");
}

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

Ahead

Btemp

Ccurrent

Dnode

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same name for parameter and temp pointer causing confusion.

Using undefined variable names in the loop.

The function takes a pointer named head. A temporary pointer temp is set to head to traverse the list.

Practice

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

easy

A. Because linked lists are faster to access elements by index

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

C. Because linked lists store elements in contiguous memory locations

D. Because linked lists use less memory than arrays always

Solution

1. Step 1: Understand array limitations

   Arrays store elements in continuous memory, so inserting or deleting in the middle requires shifting elements, which is slow.

2. Step 2: Understand linked list advantages

   Linked lists store elements in nodes connected 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 B

4. Quick Check:

   Linked list insertion/deletion is easier than array shifting [OK]

Hint: Linked lists avoid shifting elements on insert/delete [OK]

Common Mistakes:

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

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

easy

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

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

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

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

Solution

1. Step 1: Check pointer usage in struct

   In C, to refer to the same struct type inside itself, we use 'struct Node* next;' as a pointer to next node.

2. Step 2: Identify correct syntax

   struct Node { int data; struct Node* next; }; correctly declares 'struct Node* next;' while others either use wrong types or missing 'struct' keyword.

3. Final Answer:

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

4. Quick Check:

   Use 'struct Node* next;' for linked list node pointer [OK]

Hint: Use 'struct Node* next;' to link nodes in C [OK]

Common Mistakes:

• Omitting 'struct' keyword before Node pointer
• Using 'int' instead of pointer for next
• Declaring next as struct instead of pointer

3. What will be the output of the following C code snippet that creates a linked list with two nodes and prints their data?

struct Node { int data; struct Node* next; };

int main() {
  struct Node node1, node2;
  node1.data = 10;
  node1.next = &node2;
  node2.data = 20;
  node2.next = NULL;

  struct Node* ptr = &node1;
  while (ptr != NULL) {
    printf("%d ", ptr->data);
    ptr = ptr->next;
  }
  return 0;
}

medium

A. Compilation error

B. 20 10

C. 10

D. 10 20

Solution

1. Step 1: Understand linked list creation

   node1 points to node2, node2 points to NULL. So list is 10 -> 20 -> NULL.

2. Step 2: Trace the print loop

   Pointer starts at node1, prints 10, moves to node2, prints 20, then NULL ends loop.

3. Final Answer:

   10 20 -> Option D

4. Quick Check:

   Prints nodes in order: 10 then 20 [OK]

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

Common Mistakes:

• Confusing order of nodes
• Forgetting to set node2.next to NULL
• Assuming compilation error due to struct

4. Identify the error in the following code snippet that tries to insert a new node at the beginning of a linked list:

struct Node {
  int data;
  struct Node* next;
};

void insertAtBeginning(struct Node* head, int value) {
  struct Node* newNode = malloc(sizeof(struct Node));
  newNode->data = value;
  newNode->next = head;
  head = newNode;
}

medium

A. head is passed by value, so the original list head is not updated

B. malloc is not used correctly to allocate memory

C. newNode->next should be NULL instead of head

D. Function should return void* instead of void

Solution

1. Step 1: Check parameter passing

   head is passed by value, so changing head inside function does not affect original head pointer outside.

2. Step 2: Understand pointer update requirement

   To update head, function should take pointer to pointer (struct Node** head) or return new head pointer.

3. Final Answer:

   head is passed by value, so the original list head is not updated -> Option A

4. Quick Check:

   Pointer changes inside function must affect caller [OK]

Hint: Pass pointer to pointer to update head outside function [OK]

Common Mistakes:

• Assuming malloc usage is wrong
• Thinking newNode->next should be NULL
• Confusing function return type

5. You want to store a list of unknown size where frequent insertions and deletions happen anywhere in the list. Which data structure is best and why?

hard

A. Linked list, because it allows efficient insertions and deletions without shifting

B. Array, because it provides fast random access

C. Stack, because it supports last-in-first-out operations

D. Queue, because it supports first-in-first-out operations

Solution

1. Step 1: Analyze requirements

   Unknown size and frequent insertions/deletions anywhere require flexible size and efficient updates.

2. Step 2: Compare data structures

   Arrays have fixed size or costly resizing and require shifting on insert/delete. Stack and queue have restricted access patterns.

3. Step 3: Choose linked list

   Linked list nodes can be inserted or deleted by changing pointers without shifting, and size can grow dynamically.

4. Final Answer:

   Linked list, because it allows efficient insertions and deletions without shifting -> Option A

5. Quick Check:

   Linked list suits dynamic size and frequent insert/delete [OK]

Hint: Use linked list for dynamic size and easy insert/delete [OK]

Common Mistakes:

• Choosing array despite costly shifting
• Confusing stack/queue with general list
• Ignoring dynamic size needs