---
title: "AP CSP Practice 1: Computational Solution Design Study Guide"
description: "Learn AP Computer Science Principles Practice 1: Computational Solution Design. Investigate tasks, design methods, evaluate options, and use collaboration well."
canonical: "https://fiveable.me/ap-comp-sci-p/computational-thinking-practices/practice-1-computational-solution-design/study-guide/TkG1YlTvDFs731OB4aZ3"
type: "study-guide"
subject: "AP Computer Science Principles"
unit: "Computational Thinking Practices"
lastUpdated: "2026-06-17"
---

# AP CSP Practice 1: Computational Solution Design Study Guide

## Summary

Learn AP Computer Science Principles Practice 1: Computational Solution Design. Investigate tasks, design methods, evaluate options, and use collaboration well.

## Guide

## Overview

[AP Computer Science Principles](/ap-comp-sci-p "fv-autolink") Practice 1: Computational Solution Design is the skill set for planning and judging computing solutions before and while you build them. With this practice you investigate a [problem](/ap-comp-sci-p/unit-3/algorithmic-efficiency/study-guide/jGSWIqW49BtrQ8dqCWFd "fv-autolink"), design an approach that fits the purpose, use collaboration to strengthen the work, and compare options to pick the best one.

This practice shows up on both the multiple-choice section and the Create written responses. It is less about writing code line by line and more about making smart choices: what is the goal, what [method](/ap-comp-sci-p/key-terms/procedure "fv-autolink") fits, who should be involved, and which option works best.

The four subskills are:

- **1.A** Investigate the situation, context, or task.
- **1.B** Determine and design an appropriate method or approach to achieve the purpose.
- **1.C** Explain how collaboration affects the development of a solution.
- **1.D** Evaluate solution options.

## What Practice 1: Computational Solution Design Means

Think of this practice as the design-thinking layer of the course. Before a program exists, someone has to understand the problem and plan a route to a solution. Practice 1 covers that planning, plus the ongoing judgment calls about whether a solution actually meets its purpose.

It connects directly to the iterative design process in Big Idea 1: investigate the problem, design a solution, develop it, then test and refine. Practice 1 lives mostly in the investigate and design stages, but you reuse it whenever you compare two ways to do the same task.

## What This Practice Requires

Each subskill asks for something specific.

- **1.A Investigate the situation, context, or task.** Figure out what the problem actually is, who the users are, and what constraints apply. You identify needs before jumping to a solution.
- **1.B Determine and design an appropriate method or approach.** Choose a fitting plan or structure for the purpose. This could mean picking a [data](/ap-comp-sci-p/unit-2/extracting-information-data/study-guide/EFuLgc6tL71cegDFjXRl "fv-autolink") structure, deciding on inputs and outputs, or outlining steps a program should take.
- **1.C Explain how collaboration affects development.** Describe how working with people from different backgrounds and perspectives changes or improves a solution. Effective collaboration means equal voice and shared contribution, not just splitting up tasks.
- **1.D Evaluate solution options.** Compare choices and judge which is better based on goals like speed, accuracy, fairness, or fit. This includes comparing [algorithm](/ap-comp-sci-p/key-terms/algorithm "fv-autolink") efficiency, runtime, or whether an approach even meets user needs.

## Skills You Need for This Practice

You will lean on these abilities:

- Reading a scenario and naming the real goal, not a surface detail.
- Identifying users and what they need from a solution.
- Choosing a method that matches the purpose and constraints.
- Comparing two or more approaches on clear criteria.
- Reasoning about tradeoffs like parallel versus [sequential execution](/ap-comp-sci-p/unit-3/calling-procedures/study-guide/lwdr3yhVOtUJZhAmJ5cu "fv-autolink") or linear versus [binary search](/ap-comp-sci-p/unit-3/binary-search/study-guide/YADShVFQZbqwGicqH3ub "fv-autolink").
- Explaining why diverse collaboration produces solutions that serve more users.

## How It Shows Up on the AP Exam

Practice 1 appears in two places.

**Multiple-choice questions.** Expect items that give you a scenario and ask you to evaluate options or pick an approach. For example:

- A question about two processors running three processes in parallel asks for the minimum total time. With processes of 60, 30, and 50 seconds split across two processors, the best split puts 60 alone on one and 30 plus 50 on the other, so the minimum is about 80 seconds.
- A question about a sorted [list](/ap-comp-sci-p/unit-3/data-abstraction/study-guide/kMMTClSiHohfiaHMGFFE "fv-autolink") of 500 [elements](/ap-comp-sci-p/key-terms/elements "fv-autolink") asks for the maximum elements examined in a binary search. Because binary search halves the list each step, the answer is closest to 10.

Both questions are tagged to skill 1.D because they ask you to evaluate which outcome or method is best.

**Create written responses.** You answer prompts based on your own submitted program. Here you describe the purpose of your program, the approach you chose, and the design decisions you made. That work draws on 1.A, 1.B, and 1.C.

Note on strategy: when a question says "best approximates" or "most likely," it usually wants you to compare options and judge tradeoffs. That is a 1.D signal. This is practical advice, not an official scoring rule.

## Examples Across the Course

Practice 1 reaches into many units. Here are varied examples.

- **[Unit 4](/ap-comp-sci-p/unit-4 "fv-autolink"), [parallel computing](/ap-comp-sci-p/unit-4/parallel-distributed-computing/study-guide/wkNxn30shWZFeNUlcild "fv-autolink").** Deciding whether to run processes sequentially or across multiple processors is an evaluation of options (1.D). You weigh runtime against the limits of how tasks can be split.
- **[Unit 3](/ap-comp-sci-p/unit-3 "fv-autolink"), binary search and efficiency.** Choosing binary search over a linear scan for a sorted list is both a method choice (1.B) and an evaluation (1.D), since binary search examines far fewer elements.
- **[Unit 2](/ap-comp-sci-p/unit-2 "fv-autolink"), data and [metadata](/ap-comp-sci-p/key-terms/metadata "fv-autolink").** Deciding to analyze photo metadata like date and location to determine whether a photo was taken at an event, instead of analyzing pixel data, is investigating the task and choosing the right approach (1.A and 1.B).
- **[Unit 1](/ap-comp-sci-p/unit-1 "fv-autolink") and [Unit 5](/ap-comp-sci-p/unit-5 "fv-autolink"), collaboration.** Building a diverse team so a solution reflects users of different backgrounds, ages, and demographics is the core of 1.C. The course pairs this with the idea that more perspectives surface more user needs.
- **Unit 4, a customer call system upgrade.** Investigating what a directory should hold so calls route effectively, and judging which benefits a voice system can realistically deliver, mixes 1.A [investigation](/ap-comp-sci-p/unit-1/program-design-development/study-guide/SsouN8LrhRWiQ5hevIV6 "fv-autolink") with 1.D evaluation.

## How to Practice Practice 1: Computational Solution Design

Try these habits:

- For each scenario, write the goal in one sentence before looking at answer choices. This sharpens 1.A.
- Name the users and one constraint they face. Ask whether the proposed method actually serves them.
- When two methods could work, list a criterion for each (speed, accuracy, fairness) and compare them. That builds 1.D reasoning.
- On efficiency questions, practice halving for binary search and splitting work across processors for parallel timing.
- For your Create task, write a clear statement of purpose and explain one design decision and why you made it.
- Practice describing a collaboration moment: what a teammate added, and how it changed the solution.

## Common Mistakes

- **Jumping to a solution before understanding the task.** If you skip 1.A, your method may not fit the real goal.
- **Confusing collaboration with [division](/ap-comp-sci-p/unit-3/mathematical-expressions/study-guide/00lGBdF7QyY5hmd1rubD "fv-autolink") of labor.** 1.C is about how shared, diverse input improves the design, not just splitting up the work.
- **Picking the first workable option.** 1.D wants the best option by a stated criterion, so compare before you commit.
- **Ignoring constraints.** A solution that works in theory but ignores user needs or runtime limits will lose points.
- **Vague design explanations.** On the Create responses, "I made it work" is weaker than naming the purpose and the specific choice you made.

## Quick Review

- **1.A** is about investigating the task, users, and constraints before designing.
- **1.B** is choosing a method or approach that fits the purpose.
- **1.C** is explaining how diverse, shared collaboration improves a solution.
- **1.D** is evaluating and comparing options to pick the best one.
- This practice appears in multiple-choice scenario questions and in the Create written responses.
- Watch for words like "best," "minimum," and "most likely," which usually signal an evaluation of options.
- Examples span data analysis, binary search, parallel computing, and team-based design, so this practice is not tied to a single unit.
