1. What should you do when the problem isn’t obvious?

✔️ Ask questions.
❌ Move the conversation along
❌ Ask interviewer for solution

---

2. Should you rely on others’ code in an interview?

✔️ Use the data structures, but don’t use any other external implementation.
❌ Use other people’s code
❌ Write everything yourself

---

3. Number of sock pairs

Sock_colors = [3,3,2,1,1,3,5,1,4,2]
Pairs =

• 3 → 3 times → 1 pair

• 2 → 2 times → 1 pair

• 1 → 3 times → 1 pair

• 5 → 1 → 0

• 4 → 1 → 0

Total = 3 pairs

✔️ 3
❌ 4
❌ 2

---

4. Stay silent while coding?

✔️ False
❌ True
(You should explain your thought process.)

---

5. Should you ask questions?

✔️ Yes. Ask questions for clarity or during an appropriate time.
❌ Ask to waste time
❌ Only when interviewer needs help

---

6. What is the STAR method?

✔️ A structured approach to answering questions.
❌ Stellar answer
❌ Coding practice

---

7. CPU transfer rate means?

✔️ The rate at which memory is transferred into cache.
❌ Instruction processing rate
❌ Terminal input processing

---

8. Tests to include in a coding interview

✔️ Unit tests
❌ Integration tests
❌ Functional tests

---

9. Memory closest to CPU

✔️ Cache
❌ Main memory
❌ Secondary memory

---

10. Best approach when designing a solution

✔️ Planning outline → identify obstacles → explore solutions → review constantly
❌ Tackle every problem immediately
❌ Sketch quickly and implement everything

---

📘 Summary Table

---