AP CSP exam - how do I actually do well on the Create performance task?
I'm a junior and this is my first AP exam ever. My teacher has been good at preparing us for the multiple choice section but the Create performance task feels like a different animal. I understand that I need to submit code and written responses, but the rubric language is really confusing to me. Terms like program purpose vs. program function seem like the same thing but apparently they're scored differently and people lose points for mixing them up.
My program is a simple recommendation quiz that takes user input and outputs a suggested activity based on their answers. I wrote it in Python and it works fine, but I'm worried it's not complex enough to demonstrate the algorithmic concepts the rubric wants. I used a list and a loop which I think covers the data and algorithm requirements, but I'm not 100% sure.
The written responses are where I'm most nervous. I tend to write too much and then cut it down, which wastes time. My teacher said to be precise but I'm not naturally a concise writer. The 3a through 3d response format is also confusing about what exactly each part wants versus the others.
I have about 5 weeks until submission. Currently scoring around 72% on practice multiple choice. The exam is May 15th and I want to walk in feeling prepared rather than just hoping for the best.
A recommendation quiz with a list, loop, and conditional logic is more than sufficient for the algorithm requirements as long as you explain it clearly. The rubric doesn't reward complexity for its own sake. I saw people with fancy programs lose points because their written explanation was vague, and simple programs get full credit because the student was precise about what the code does.
72% on multiple choice 5 weeks out is solid. The MC section has a lot of questions about internet infrastructure and data encoding that feel random but they test the same concepts repeatedly. Know binary, data compression trade-offs, and how packets and protocols work and you'll pick up a lot of easy points there.
The purpose vs. function distinction trips everyone up. Purpose is the broader goal - why someone would use the program. Function is what it specifically does. Something like "to help users discover new hobbies" is purpose. "Takes 5 user inputs and returns a matching activity from a list of 20 options" is function. Write those two things and don't mix them up in your responses.
For the written responses, write your answer then cut it by 30%. Seriously. The rubric wants specific and concise, and most students over-explain. Practice reading the response out loud - if it sounds like you're circling around the point, it probably is. The graders read hundreds of these.
I was in the same boat a few weeks ago honestly. The rubric felt like it was written in another language. What helped me was just picking one row at a time and asking myself "can I literally point to a line in my code that proves this?" For the algorithm row especially, make sure your code has sequencing, selection, AND iteration all visible, not just one. I've been doing practice MC on the side too, just hit a 68 on a practice set which I'm actually happy with considering where I started. Sitting the real exam in May so still got some runway. Also if you're shaky on the logic stuff that shows up in written responses, drilling through apcsp/questions/boolean logic questions helped me understand how to explain my code decisions in plain English, which is basically what the written responses want.
Don't overthink the program purpose vs function thing either. Purpose is why it exists, function is what it does. Once that clicked for me the written responses got way less scary.
Just wanted to share a quick update since I'm in a similar boat. I took a practice version of the Create task last week and honestly it went better than I expected -- I got a 4 out of 6 which isn't amazing but it's way better than the 1 I thought I'd get going in. The biggest thing that helped me was just picking a program I actually cared about instead of trying to make something that "looked impressive."
I'm planning to submit my final version in late April before the deadline, so I've got a few more weeks to polish the written responses. The rubric language is weird but once you realize they're basically asking "show me a loop, show me a function, show me a list, and explain why it matters" it clicks a little more. Good luck to you too, we've got this.
I was in the same boat a few months ago and honestly the rubric clicked for me once I stopped trying to memorize it and just focused on making sure my written responses directly referenced specific lines of my code. Like, don't just say "my program uses a list" -- say "on line 14, I iterate through the list using a for loop to process each input." The graders aren't reading your mind. Also studying the underlying concepts helped way more than I expected -- I actually went through apcsp/questions/boolean logic practice questions because boolean conditions kept showing up in my algorithms section and I wasn't confident explaining them in writing.
Quick update on my end: just got a 74% on a full practice run last week which felt way better than my first attempt at 58%. I'm planning to sit the real exam in May so I've got a few months to keep refining my task. Honestly just keep iterating on your code and written responses together -- don't treat them as separate things.