PCEP-30-02 — Python Institute PCEP - Certified Entry-Level Python Programmer Study Plan

How to use this Study Plan

This independent Study Plan is for candidates preparing for the Python Institute PCEP - Certified Entry-Level Python Programmer (PCEP-30-02) exam from the Python Institute.

Use it to turn your available time into a structured review schedule. The plan is built around entry-level Python skills: reading code, predicting output, using core syntax correctly, handling simple logic, working with built-in data types, and recognizing common errors.

The most important rule: do not only read Python explanations. Write, run, and trace code every study day.

Which plan should you use?

Use the shorter plan only if you already know basic Python syntax. If you are new to programming, choose the 60/90-day path.

Core PCEP-30-02 skill areas to organize your study

Do not study topic names in isolation. For this exam, you need to be able to read short Python programs and determine what happens.

Daily practice rhythm

Use the same rhythm regardless of plan length.

A good daily session should produce something visible: a small script, a corrected error log, a list of missed patterns, or a timed score.

Diagnostic-first setup

Before starting any plan longer than 7 days, take a short diagnostic set.

Do not be discouraged by a low first diagnostic score. Its purpose is to tell you where your time should go.

7-day final review sprint

Use this plan if your exam is in one week and you have already studied Python basics.

7-day rules

• Do not start a full Python course from scratch.
• Do not add large new resources after Day 4.
• Prioritize repeated missed patterns over broad reading.
• Take one serious timed mock no later than Day 6.
• The final day should be lighter and focused on confidence, accuracy, and sleep.

14-day focused plan

Use this plan if you know some Python but need a complete exam-focused pass.

14-day emphasis

For each topic day, complete three layers:

1. Explain the rule in your own words.
2. Run 5-10 short code examples that test the rule.
3. Answer exam-style questions and log every miss.

30-day balanced plan

Use this plan if you want enough time to learn, practice, and stabilize performance.

Weeks 1-4 overview

30-day schedule

60/90-day full preparation path

Use this path if you are new to programming or want a lower-stress schedule.

60-day version

90-day version

Weekly routine for 60/90 days

Hands-on Python drill patterns

For PCEP-30-02, small examples are better than large projects. Your goal is to recognize behavior quickly.

Drill 1: Predict output before running

x = 3
y = 2
x = x + y
y = x - y
print(x, y)

Before running it, write:

• final value of x
• final value of y
• exact printed output

Then change the starting values and repeat.

Drill 2: Trace loops carefully

total = 0

for i in range(1, 5):
    if i % 2 == 0:
        total += i

print(total)

For loop questions, make a small table:

Drill 3: Test collection behavior

items = [10, 20, 30, 40]
items[1] = items[0] + items[2]
print(items)
print(items[1:3])

Ask:

• Which operation changes the list?
• Which operation creates a sliced result?
• What is printed first?
• What is printed second?

Drill 4: Separate return values from printed output

def add_one(n):
    return n + 1

x = add_one(4)
print(x)

For function questions, identify:

1. what arguments are passed,
2. what local variables exist,
3. what value is returned,
4. what output is printed, if any.

Missed-question review method

A missed question is useful only if you classify why you missed it.

Missed-question log template

Review this log every 3-4 study days and daily during the final week.

When to use timed mock exams

Timed mocks are most valuable after you have covered the core topics at least once.

Mock review rules

After each mock:

1. Review every incorrect answer.
2. Review every lucky guess.
3. Review every question that took too long.
4. Recreate short code snippets for missed programming behavior.
5. Turn the top 3 weak areas into the next study session.

Do not take mock after mock without review. For this exam, the review is where most improvement happens.

Focused review checklists

Syntax and basics checklist

You should be able to answer yes to each item.

• I can recognize valid indentation and block structure.
• I know how assignment changes variable values.
• I can distinguish strings, integers, floats, and booleans.
• I can predict the result of simple arithmetic expressions.
• I can identify when type conversion is needed.
• I can use print() and understand what it outputs.
• I can explain what input() returns.

Control flow checklist

• I can trace if, elif, and else branches.
• I can evaluate compound conditions with and, or, and not.
• I can trace while loops and identify when they stop.
• I can trace for loops using range().
• I understand break and continue.
• I can follow nested conditions and nested loops.

Collections checklist

• I can index strings, lists, and tuples.
• I can use slicing and remember that the stop position is not included.
• I understand which common operations mutate a list.
• I can iterate through a collection.
• I can read and update simple dictionaries.
• I can distinguish list, tuple, string, and dictionary behavior.

Functions and exceptions checklist

• I can identify function definitions and function calls.
• I understand parameters and arguments.
• I can determine what a function returns.
• I can distinguish returned values from printed output.
• I understand basic local variable behavior.
• I can recognize common errors and basic exception-handling flow.

Final-week rules

During the final week, your goal is stability.

Exam-readiness checks

You are likely ready to schedule or sit for PCEP-30-02 when most of the following are true:

If you are still missing the same topic repeatedly, do not just reread notes. Write 5-10 small examples that isolate that exact issue.

Practical next step

Start with a timed diagnostic practice set for the Python Institute PCEP - Certified Entry-Level Python Programmer (PCEP-30-02). Tag every missed question, choose the 7-day, 14-day, 30-day, or 60/90-day path, and make your next session a targeted drill on your weakest topic.