Why Arrays Exist and What Problem They Solve in DSA Go - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do arrays provide faster access to elements compared to linked lists?

Choose the best explanation for why arrays allow faster access to elements than linked lists.

A Arrays store elements in continuous memory locations, so accessing any element by index is direct and fast.

B Arrays use pointers to link elements, so you must follow links to find an element, making access slower.

C Arrays store elements randomly in memory, so searching for an element takes longer time.

D Arrays compress elements to save space, which slows down access to individual items.

💡 Hint

Think about how memory is arranged for arrays versus linked lists.

Arrays keep elements next to each other in memory. This means the computer can calculate where any element is quickly using its index. Linked lists store elements scattered in memory and use pointers to connect them, so you must follow links to reach an element, which takes more time.

❓ Predict Output

intermediate

What is the output after inserting elements in an array?

Given the Go code below, what is the printed output?

DSA Go

package main
import "fmt"
func main() {
  arr := [5]int{0, 0, 0, 0, 0}
  arr[0] = 10
  arr[3] = 20
  fmt.Println(arr)
}

A [0 10 0 20 0]

B [0 0 0 0 0]

C [10 0 0 20 0]

D [10 0 20 0 0]

💡 Hint

Remember array indexes start at 0.

The array starts with all zeros. Setting arr[0] = 10 changes the first element. Setting arr[3] = 20 changes the fourth element. The rest remain zero.

🔧 Debug

advanced

Why does this Go code cause an error when accessing array elements?

What error will this Go code produce and why?

DSA Go

package main
import "fmt"
func main() {
  arr := [3]int{1, 2, 3}
  fmt.Println(arr[3])
}

A compilation error: missing semicolon after arr declaration

B runtime error: index out of range because arr has only 3 elements indexed 0 to 2

C prints 0 because arr[3] is default zero value

D compilation error: cannot assign to arr[3]

💡 Hint

Check the valid index range for the array.

Arrays in Go have fixed size. Indexes go from 0 to length-1. Accessing arr[3] when length is 3 is out of range and causes a runtime error.

🚀 Application

advanced

Which problem do arrays solve best compared to other data structures?

Select the problem that arrays are best suited to solve.

A Storing elements with complex relationships like trees or graphs

B Efficient insertion and deletion of elements anywhere in the collection

C Dynamic resizing without copying elements

D Fast access to elements by position when size is fixed or known in advance

💡 Hint

Think about what arrays do well and what they do poorly.

Arrays provide fast access by index but are not good for frequent insertions or deletions because elements must be shifted. They also have fixed size, so dynamic resizing is costly. Complex relationships are better handled by other structures.

❓ Predict Output

expert

What is the output of this Go code showing array memory layout?

Analyze the code and select the correct output printed.

DSA Go

package main
import "fmt"
func main() {
  arr := [3]int{5, 10, 15}
  ptr := &arr[0]
  fmt.Println(*ptr)
  ptr = &arr[2]
  fmt.Println(*ptr)
}

A

5
15

B

0
15

C

5
0

D

15
5

💡 Hint

Remember pointers hold addresses of elements, and *ptr dereferences to value.

The pointer ptr first points to arr[0], which is 5, then to arr[2], which is 15. Printing *ptr shows these values.

Practice

1. Why do arrays exist in programming languages like Go?

easy

A. To perform mathematical calculations faster

B. To store values of different types in a single variable

C. To store multiple values of the same type in a fixed-size sequence

D. To replace all other data structures

Solution

1. Step 1: Understand the purpose of arrays

   Arrays are designed to hold multiple values of the same type together in a fixed-size sequence.

2. Step 2: Compare with other options

   The other options describe features not specific to arrays or are incorrect.

3. Final Answer:

   To store multiple values of the same type in a fixed-size sequence -> Option C

4. Quick Check:

   Arrays = fixed-size same-type storage [OK]

Hint: Arrays hold same-type items in order with fixed size [OK]

Common Mistakes:

• Thinking arrays can store different types together
• Confusing arrays with lists or slices
• Believing arrays perform calculations themselves

2. Which of the following is the correct way to declare an array of 5 integers in Go?

easy

A. var arr [5]int

B. int arr[5]

C. var arr []int = make(5)

D. arr := []int{5}

Solution

1. Step 1: Recall Go array declaration syntax

   In Go, arrays are declared with fixed size: var arr [5]int declares an array of 5 integers.

2. Step 2: Analyze other options

   int arr[5] is invalid C-style syntax in Go. var arr []int = make(5) uses make incorrectly (make is for slices, not arrays). arr := []int{5} declares a slice, not an array.

3. Final Answer:

   var arr [5]int -> Option A

4. Quick Check:

   Array declaration = var arr [size]type [OK]

Hint: Use var name [size]type for arrays in Go [OK]

Common Mistakes:

• Using make() for arrays instead of slices
• Confusing slices with arrays
• Initializing arrays with fewer elements than size without explicit zeros

3. What will be the output of the following Go code?

package main
import "fmt"
func main() {
  var arr [3]int
  arr[0] = 10
  arr[1] = 20
  arr[2] = 30
  fmt.Println(arr)
}

medium

A. [10 20]

B. [10 20 30]

C. [0 0 0]

D. Compilation error

Solution

1. Step 1: Understand array initialization and assignment

   The array of size 3 is declared with default zeros. Then each index is assigned 10, 20, and 30 respectively.

2. Step 2: Print the array

   Printing the array shows all elements in order: [10 20 30].

3. Final Answer:

   [10 20 30] -> Option B

4. Quick Check:

   Array after assignments = [10 20 30] [OK]

Hint: Arrays print all elements in order inside brackets [OK]

Common Mistakes:

• Expecting commas between elements in output
• Thinking unassigned elements remain uninitialized
• Confusing slices and arrays output format

4. Identify the error in this Go code snippet that tries to assign a value to an array element:

package main
func main() {
  var arr [3]int
  arr[3] = 100
}

medium

A. Index out of range error at runtime

B. Compilation error: index 3 out of bounds

C. No error, code runs fine

D. Array size is not declared

Solution

1. Step 1: Check array size and index used

   The array has size 3, so valid indices are 0, 1, and 2. Index 3 is out of bounds.

2. Step 2: Understand Go's bounds checking

   Go performs bounds checking at runtime and panics with an index out of range error on out-of-bounds access.

3. Final Answer:

   Index out of range error at runtime -> Option A

4. Quick Check:

   Array index must be less than size [OK]

Hint: Array indices go from 0 to size-1 only [OK]

Common Mistakes:

• Using index equal to array size
• Expecting runtime error instead of compile error
• Confusing slices with arrays for index bounds

5. You want to store the daily temperatures for a week using an array in Go. Which of the following is the best approach and why?

medium

A. Use a single float64 variable and update it daily

B. Use a slice without fixed size to store temperatures

C. Use a map with string keys for days and float64 values

D. Use an array of size 7 with type float64 to store temperatures

Solution

1. Step 1: Analyze the problem requirements

   We need to store exactly 7 temperature values, one for each day of the week.

2. Step 2: Choose the best data structure

   An array of size 7 with float64 type fits perfectly because the size is fixed and known. Slices or maps add unnecessary overhead here. A single variable cannot hold multiple values.

3. Final Answer:

   Use an array of size 7 with type float64 to store temperatures -> Option D

4. Quick Check:

   Fixed-size data = array best choice [OK]

Hint: Fixed known size? Use array for efficient storage [OK]

Common Mistakes:

• Choosing slices when size is fixed and known
• Using maps when order matters and keys are unnecessary
• Trying to store multiple values in one variable