AP Computer Science Principles Unit Tests
Pick a unit to drill it head-on. Each unit has 4 different test variations so you can keep retaking until you master it.
Big Idea 1: Creative Development
Collaboration, program function & purpose, design, and program development.
5 questions · ~8 minsmall bank — variations may overlap
Big Idea 2: Data
Binary, data abstraction, data compression, and information extraction.
10 questions · ~15 minsmall bank — variations may overlap
Big Idea 3: Algorithms & Programming
Variables, data abstraction, algorithms, simulations, and procedures.
12 questions · ~18 minsmall bank — variations may overlap
Big Idea 4: Computing Systems & Networks
Internet, fault tolerance, parallel & distributed computing.
10 questions · ~15 minsmall bank — variations may overlap
Big Idea 5: Impact of Computing
Beneficial and harmful effects, digital divide, computing bias, and security.
10 questions · ~15 minsmall bank — variations may overlap
How unit tests work
- Focused on a single AP unit, between a single-topic quiz and the full diagnostic.
- 4 variations per unit — pick a fresh variation any time you retake.
- Roughly 90 seconds per question — the same pacing as the AP exam.
- You'll get a unit-level score, recommended topics to review, and a question-by-question explanation.
About the AP Computer Science Principles exam
AP Computer Science Principles is a broad, conceptual introduction to computing that emphasizes computational thinking over mastery of a single programming language. Rather than focusing on Java syntax like AP Computer Science A, this course explores the big ideas of computing: creative development, data, algorithms and programming, computer systems and networks, and the impact of computing on society. Students learn how data is represented in binary, how the internet routes information through protocols and fault-tolerant networks, how algorithms can be efficient or undecidable, and how programs use variables, lists, procedures, and conditionals expressed in pseudocode or block-based languages. A defining feature of the course is the through-line on ethics and global impact: students examine privacy, the digital divide, bias in computing innovations, and intellectual property. Assessment is split between a hands-on Create performance task, completed over class time, and an end-of-course exam that now includes written-response questions tied to that project. Students frequently underestimate the exam pseudocode, assuming familiarity with their classroom language transfers directly to the College Board's reference language; careful practice with the provided pseudocode reference is essential. Others lose points on the Create task by submitting programs that lack a genuine student-developed algorithm with selection and iteration, or by writing program code segments in their written responses that do not actually match their submitted code. Strong preparation means practicing binary and data representation, tracing pseudocode, articulating how an algorithm works in plain language, and starting the Create program early so the required list, procedure, and algorithm are well documented before the written responses are drafted.
Exam structure
End-of-course Bluebook exam of 70 multiple-choice questions in 120 minutes plus written-response questions about the student's project; this exam is 70% of the score. The Create performance task (student-developed program, video, and Personalized Project Reference, built in ~9 hours of class time) is 30%.
Scoring
Multiple-choice and written-response points combine with the Create performance task score and convert to the AP 1-5 scale.
Common mistakes
- Assuming the classroom programming language matches the exam's pseudocode reference instead of practicing the College Board notation
- Submitting a Create program that lacks a true student-developed algorithm integrating sequencing, selection, and iteration
- Mismatching written-response code segments with the actual submitted program code, which violates response requirements
- Errors in binary/data representation and converting between number systems
- Treating the impact-of-computing and ethics content as filler rather than a graded, recurring exam topic