Skip to content

CSP mock exam review #7

Description

@Shayanb1
Image Image Image Image Image Image Image Image Image Image Image

Question 6
Mistake: I chose B because I thought only Program I worked and didn’t fully trace Program II.
Correction: The correct answer is C because both Program I and Program II successfully move the robot to the gray square.
Lesson Learned: Trace every step of each program carefully before deciding which answers work.

Question 11
Mistake: I chose B and thought the triplet represented light yellow instead of ivory.
Correction: The correct answer is A because (11111111, 11111111, 11110000) converts to (255, 255, 240), which matches ivory.
Lesson Learned: Convert binary RGB values to decimal before comparing to the color table.

Question 17
Mistake: I chose C and did not realize that all digital data, including integers and characters, are represented by bits.
Correction: The correct answer is D because sequences of bits represent all digital data at the lowest level.
Lesson Learned: Remember that bits are the fundamental representation of all digital information.

Question 23
Mistake: I chose C because I misread the conditions and thought the algorithm used OR instead of AND.
Correction: The correct answer is D because the flowchart sets available to true only when weekday is true and miles are less than 20.
Lesson Learned: Carefully trace all conditions in a flowchart to understand the logic before matching to code.

Question 29
Mistake: I chose D and thought no compression was needed.
Correction: The correct answer is A because lossless compression allows the original file to be fully reconstructed after transmission.
Lesson Learned: Lossless compression preserves all data so the exact original can be restored.

Question 35
Mistake: I chose C because I thought MaxFour generalized MaxTwo and MaxThree.
Correction: The correct answer is B because Max(numList) works for any number of inputs, fully generalizing MaxTwo and MaxThree.
Lesson Learned: Generalization means handling any number of inputs, not just a fixed number.

Question 38
Mistake: I chose C, incorrectly thinking IPv6 removed hierarchy in addresses.
Correction: The correct answer is B because IPv6 provides a larger address space than IPv4, supporting more devices.
Lesson Learned: Focus on the actual improvements of new technologies over old versions.

Question 52
Mistake: I chose C and assumed the simulation displayed total population at the end.
Correction: The correct answer is A because the simulation displays the change in population and stops after 24 hours or when population reaches 0.
Lesson Learned: Carefully read what the simulation outputs versus what it tracks internally.

Question 58
Mistake: I chose D and thought the procedure worked for all inputs.
Correction: The correct answer is C because the procedure returns false when x = z and y is different, which does not match the intended behavior.
Lesson Learned: Make sure all possible input combinations are tested to verify a procedure works as intended.

Question 61
Mistake: I chose A and C, incorrectly thinking restricting access could help reduce the digital divide.
Correction: The correct answers are B and D because accessibility features and improved network infrastructure help more people access technology.
Lesson Learned: Reducing the digital divide requires making technology accessible and available, not limiting it.

Question 67
Mistake: I chose B and D, incorrectly assuming the procedure would count occurrences correctly.
Correction: The correct answers are A and B because the count variable is reset inside the loop, causing incorrect results for multiple occurrences.
Lesson Learned: Be careful with variable placement inside loops; resetting counters inside the loop can break the intended logic.

Analysis of Strengths and Weaknesses

  • Strengths: Networking concepts (IPv6), basic algorithms.
  • Weaknesses: Loop logic, conditional statements, procedure generalization, tracing code execution.
  • Common mistakes: Misreading flowcharts, misplacing counters in loops, confusing OR/AND conditions.

Future Steps to Review

  • Practice tracing loops and nested conditionals step by step.
  • Review generalization of functions and procedures for any number of inputs.
  • Drill digital literacy topics, like compression and accessibility concepts.
  • Work on reading and interpreting flowcharts and pseudocode carefully.

What I Can Do to Master These Topics

  • I will do daily loop tracing exercises with varying inputs, including nested loops and edge cases.
  • I will practice writing and debugging procedures with multiple input combinations to verify correctness.
  • I will use flashcards to memorize key differences between IPv4 vs IPv6, lossless vs lossy compression, and AND vs OR logic.
  • I will draw out flowcharts by hand and trace every branch before matching to pseudocode.
  • I will create a dedicated RGB conversion cheat sheet and practice binary-to-decimal conversions regularly.
  • I will explain each problem out loud or to a study partner to confirm true understanding.
  • I will review generalization concepts by practicing rewriting fixed-input functions to handle any number of inputs.
  • I will study digital divide topics including accessibility features, infrastructure, and equity in technology access.
  • I will time myself on practice tests to build speed and accuracy under exam conditions.
  • I will keep a running error log of repeated mistakes to identify and address persistent weak spots.
  • I will watch video walkthroughs of tricky algorithm and flowchart problems to see step-by-step reasoning.

Summary of mastery for each topic:

Image Image

Skills I should work on the most:

  • 2.1 - 3/5
  • 2.2 - 0/1
  • 3.13 - 0/1
  • 5.2 - 0/1

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions