PCPP2

The Institute lists the cost as "from $295". Delivery is through Pearson VUE, either at an authorised Pearson VUE Testing Center or online via OnVUE proctoring. Book through Pearson VUE once the exam version you want is available; the Institute's page currently shows PCPP-32-201 as in development.

45 questions in 65 minutes, plus 10 minutes for the NDA and tutorial. That is roughly 87 seconds per question. Scenario-based and interactive items take longer than single-select ones, so bank time on quick recall questions and do not let one long item consume your budget.

The published passing score is 70%. Because the syllabus is still listed as in development, no official domain weights are published, so you cannot safely skip a topic area. Assume all five published areas can appear and prepare each to a working level rather than optimising for a weighting.

The Institute's exam information table lists PCPP-32-201 with the status "In development", and the certification roadmap marks PCPP-32-20x as "Work in progress". Check the official PCPP2 page for the current status before paying for a voucher or scheduling a seat.

No formal prerequisites apply. The Institute recommends prior PCAP™ and PCPP1™ certification. That recommendation is practical: PCPP1-level familiarity with advanced OOP, file processing and standard library modules underpins the design patterns and testing content here, so candidates without it usually need extra groundwork.

The public PCPP2 page does not state a retake policy. It links to PCPP-32-10x testing policies rather than a PCPP2-specific document, so the terms that will govern PCPP2 attempts are not confirmed in the published material. Confirm the policy with the Institute or Pearson VUE before relying on a retake plan.

Five years from the date you earn it. Plan recertification or renewal before expiry if the credential matters for your role. The Institute publishes credential verification and digital badging services, which employers may use to check that your certification is current.

Start with testing (unittest, then pytest), because writing tests reinforces everything else. Move to design patterns, then threading and multiprocessing, then sockets, then databases. Write runnable code for each area: a small socket server, a process pool with a lock, and a CRUD layer over both a relational and a document database.

Reading without coding. Typical weak spots are telling threading from multiprocessing correctly, mixing up pattern intents (Facade versus Proxy, Strategy versus State), and shallow socket knowledge such as blocking behaviour and byte framing. Also practise reading multi-select wording carefully, since partially correct selections usually earn nothing.

No. This is independent study material written for candidates preparing for the exam. It is not affiliated with, endorsed by, or produced by the OpenEDG Python Institute or Pearson VUE. Always treat the official PCPP2 page as the authority on exam status, pricing, format and policies.