CPA-Test
Certified Public Accountant Test: Auditing and Attestation, Business Environment and Concepts, Financial Accounting and Reporting, Regulation
CPA-Test Exam Guide: C++ Skills, Study Plan, and Scheduling Decisions
The CPA – C++ Certified Associate Programmer certification validates that you can solve common programming problems with C++, write correct and efficient code, and apply core object-oriented principles such as classes, inheritance, and polymorphism. It serves learners moving beyond entry-level C++ as well as aspiring software developers who want a structured skills benchmark. This guide helps you decide whether your current foundation is sufficient, what to study first, and whether a Pearson VUE test center or OnVUE appointment suits your circumstances.
What does the CPA exam validate?
CPA measures applied knowledge rather than familiarity with isolated C++ terminology. The official objective is to show that you can use C++ syntax and semantics, program logic, pointers, memory management, exceptions, preprocessor directives, classes, inheritance, and polymorphism to solve typical programming tasks. A sensible preparation target is therefore working understanding: you should be able to predict behavior, identify defects, and select an appropriate implementation technique.
The certification belongs to the C++ Institute’s associate level. The institute describes that level as recognizing essential programming techniques, core language features, coding practices, and use of standard libraries. CPA is positioned above the C++ Certified Entry-Level Programmer certification and below the C++ Certified Professional Programmer certification. The exam has no formal prerequisites, but the absence of a prerequisite does not mean that a first-time programmer should skip foundational practice.
The active exam version identified by the official CPA page is CPA-21-02, while CPA-21-01 is retired. Confirm the version shown in the registration flow before buying or applying a voucher, particularly if you are using older course material or a third-party study plan.
Who is a realistic candidate?
CPA is a reasonable target for a learner who can already write small C++ programs and is ready to connect procedural programming with object-oriented design. It can also suit a programmer with intermediate C++ proficiency who wants a formal checkpoint before pursuing the professional-level CPP certification. Beginners may start with the official C++ Essentials sequence, but should assess their ability to write and debug code rather than relying only on course completion.
What the credential does not prove
Passing CPA does not by itself establish expertise in every modern C++ library, a particular framework, production software engineering, or advanced algorithm design. The measured objectives are specific. Treat the certificate as evidence of the tested C++ and OOP foundation, not as a substitute for projects, code review, debugging practice, or knowledge of a workplace toolchain.
How is the exam structured and scored?
The CPA exam contains 40 questions in single-choice and multiple-choice formats. The exam duration is 65 minutes plus approximately 10 minutes for the nondisclosure agreement and tutorial. Questions can carry different point values, with candidates able to earn up to a maximum of 200 points; the total is normalized into a percentage. Passing requires a cumulative score of 70% or higher across all questions, not a simple average by exam block.
This scoring model changes how you should review. A weak area matters, but the official result is not calculated as a separate pass-or-fail result for each domain. Use the blueprint to allocate study time, then use mixed practice to test whether you can move between topics without confusing similar rules. Do not interpret a high result on one small topic as proof that the full exam is ready.
The official page presents the active CPA-21-02 blueprint with five blocks. Block 1 – Types & Operators has 9 exam items and a weight of 24.5%; Block 2 – Control & Exceptions has 8 exam items and a weight of 18%; Block 3 – Functions & Preprocessor Directives has 9 exam items and a weight of 17.5%; Block 4 – Pointers has 4 exam items and a weight of 11%; and Block 5 – Classes & Namespaces has 10 exam items and a weight of 29%. Each percentage is tied to its named domain because the values are not useful as unlabeled comparisons.
How should you use the blueprint?
Use domain weight as a planning signal, not as a prediction of the exact questions you will see. Begin with Block 1 and Block 5 because they represent substantial portions of the blueprint, then give deliberate attention to pointers and functions even though those blocks contain fewer or differently weighted items. Finally, combine domains in code-tracing sessions so that an operator, pointer, class, or exception is considered in context.
What does a 70% target mean for practice?
A practice score at the pass threshold leaves little room for unfamiliar wording, careless tracing, or a technical problem. Set a personal readiness margin above the official 70% requirement, but do not present that margin as an official passing rule. More important than one score is a repeatable pattern: explain why an answer is correct, locate the rule involved, and correct the code when your answer is wrong.
Which C++ topics deserve the most attention?
The syllabus is broad but coherent: start with types and expressions, move through control flow and functions, then study pointers and memory, and finish by integrating classes, inheritance, polymorphism, exceptions, and namespaces. This sequence follows dependencies in the language. For example, class behavior is harder to reason about if references, object lifetime, type conversion, and function calls are still uncertain.
Block 1 includes literals, standard types, ranges and representations, strings, aggregates, declaration modifiers, conversions, casts, sizeof, and unary, binary, ternary, arithmetic, relational, logical, bitwise, assignment, increment/decrement, and short-circuit operators. Practice should focus on expression evaluation and type behavior. Write short snippets that force you to identify precedence, promotion, conversion, and the final value rather than merely naming operators.
Block 2 covers if and else, while, do, and for loops, switch, case, default, break, continue, goto, and exception handling. Trace the exact path through a program and mark where control leaves a loop or function. For exceptions, distinguish try, catch, throw, catch-all handling, exception categories, hierarchies, and the throw() specifier listed in the objectives.
Block 3 covers function definition, declaration, invocation, typed and void functions, return statements, overloading, default parameters, recursion, conventions for main(), preprocessor conditional compilation, and parameterized or non-parameterized macros. Alternate code writing with code reading. A candidate who can write a function but cannot predict overload selection or recursive termination has an avoidable gap.
Block 4 covers pointer declarations and initialization for variables, objects, functions, and aggregates; dereferencing; the address-of operator; pointer arithmetic and comparisons; and dynamic memory with new, delete, and delete[]. Include memory-leak prevention in every exercise. Ask who owns an allocated object, when it is released, and whether the matching deletion form is used.
Block 5 covers OOP principles, class definitions, access specifiers, the scope resolution operator, this, constructors and destructors, member and operator overloading, single and multiple inheritance, visibility, type compatibility, static_cast, dynamic_cast, virtual and polymorphic functions, const on objects and members, friend classes and functions, and named, anonymous, and aliased namespaces. This is not one topic: divide it into object construction, class interfaces, inheritance behavior, and name/type resolution.
Where do the official courses fit?
C++ Essentials 1 is designed for beginners and covers the programming environment, basic syntax, semantics, data types, control structures, vectors, arrays, structures, strings, namespaces, and exception handling. C++ Essentials 2 continues from that foundation and focuses on OOP, inheritance, exceptions, operator overloading, and enumerated types. The official C++ Essentials 2 course is free, online, self-study, in English, and lists a suggested study time of 42 hours; that study-time figure is a course recommendation, not a guaranteed CPA preparation duration.
If you are starting from zero, use C++ Essentials 1 before C++ Essentials 2, even though the second course has no formal prerequisites. If you already write C++ comfortably, use the CPA objectives as a diagnostic and select modules based on demonstrated gaps. Do not spend equal time on material you can already explain and material that still produces incorrect predictions.
How should you build a preparation strategy?
Use a diagnose, learn, implement, and review cycle. First test each blueprint block with short code-tracing and implementation tasks. Next study the rule behind each error. Then write or modify a small program that applies the rule. Finally, record the mistake in your own words and revisit it later. This method is more reliable than reading every chapter repeatedly because CPA requires transfer between concepts.
Create an error log with four fields: the code or question pattern, your selected answer, the governing C++ rule, and the corrected reasoning. Add tags such as conversion, lifetime, overload, inheritance, or exception flow. When a tag appears repeatedly, return to the smallest prerequisite that explains it. For example, an apparent class problem may actually be a misunderstanding of reference parameters or static versus dynamic type.
Use an editor and compiler while learning, but do not let successful compilation replace reasoning. Compile a minimal example, change one feature, predict the output or error, and then test the prediction. For pointer and object-lifetime work, draw addresses or ownership relationships on paper or a whiteboard before running the program. For operators and control flow, trace values line by line.
Reserve some sessions for closed-book recall. Write the declaration of a function, explain the difference between value, reference, and pointer parameters, describe constructor and destructor roles, and trace a virtual call without consulting notes. Then verify against authoritative material. This exposes gaps that passive highlighting conceals.
A practical study sequence
Start with environment setup and basic syntax so that every later topic can be compiled. Continue with types, literals, strings, aggregates, and operators. Add control structures and exceptions, then functions and parameter passing. Study pointers and dynamic memory after references and function calls are stable. Finish with classes, constructors, inheritance, casts, virtual functions, namespaces, and integrated exercises.
At the end of each stage, produce something small: a value-conversion test, a loop-driven text utility, a function library, a pointer-based data exercise, and a class hierarchy. The purpose is not portfolio quality. It is to force the language rules to interact in code that you can inspect and revise.
A decision rule for changing your plan
If you miss questions because you cannot recall a rule, schedule targeted reading and flashcard-style recall. If you know the rule but misread code, schedule slower tracing and annotate each state change. If you can solve isolated items but fail mixed sets, increase interleaving. If errors come from rushing, practise a deliberate review routine rather than simply adding more content.
What roadmap can take you from foundation to readiness?
A flexible roadmap should move from language mechanics to integration, with a readiness check before scheduling. The official course materials can provide structure, but the calendar is your decision: compress or extend each phase according to prior experience and the error log. A useful sequence is five phases, each ending with evidence that you can perform the skill without copying a worked example.
Phase 1: establish the toolchain and fundamentals. Set up the compiler or IDE, build a minimal program, and practise variables, literals, standard types, strings, arrays, vectors, structures, and basic input/output. Verify that you can explain declarations, conversions, modifiers, and the result of common expressions. If these are unstable, do not rush into inheritance.
Phase 2: control flow and functions. Write programs using conditionals, switch, loops, break, continue, and return. Add typed and void functions, overloads, default arguments, recursion, and all three parameter-passing styles. Include a small main() program that calls several functions and handles invalid input or an exception. Review both syntax and behavior.
Phase 3: pointers, memory, and exceptions. Declare and initialize pointers, use dereferencing and address-of operations, trace pointer arithmetic, and compare pointers only in contexts you can justify. Implement dynamic allocation with matching deletion and deliberately inspect paths that could leak memory. Add try, catch, and throw examples, including more than one handler, then explain which handler receives a thrown value.
Phase 4: object-oriented C++. Define classes with appropriate access control, constructors, destructors, this, const members, and overloaded functions or operators. Add inheritance and visibility, then compare static and dynamic type. Build a small hierarchy in which a virtual function demonstrates polymorphism. Test copies, object lifetime, casts, and namespace qualification rather than treating a class as only a collection of fields.
Phase 5: exam integration. Work through mixed, original practice tasks that reflect the published objectives without relying on recalled or leaked exam content. Keep a strict review process: identify the objective, trace the code, eliminate incompatible options, and flag any item whose answer depends on a rule you cannot explain. Revisit the error log, then take a final readiness check under conditions that resemble your selected delivery method.
How do you know when to schedule?
Schedule when you can work across all five blueprint blocks, not merely when you finish a course. You should be able to explain recurring errors, trace short programs without guessing, and complete mixed practice with a stable margin above the official passing requirement. Also confirm the active exam version, acceptable identification, delivery choice, equipment or travel arrangements, and the cancellation window before committing to an appointment.
What should the final review contain?
The final review should be compact and active: operator precedence and conversions, control-flow exits, function overload and parameter rules, recursion, pointer lifetime, new/delete matching, exception selection, constructor and destructor behavior, inheritance visibility, virtual dispatch, casts, const, and namespaces. Avoid starting an unfamiliar textbook immediately before the appointment. Use your error log and write a few small programs from memory instead.
Where can you take CPA?
The C++ Institute lists Pearson VUE authorized testing centers and OnVUE online proctoring as CPA delivery options. A test center provides a secure physical location; OnVUE allows remote testing from a quiet, private space that meets technical and room requirements. Choose based on reliability, not convenience alone: a stable test-center appointment may be preferable if your home network, room, or computer is uncertain.
Candidates can schedule CPA-21-02 through the C++ Institute registration portal at Pearson VUE, by contacting a Pearson VUE test center, or through the Pearson VUE contact center. The official scheduling page says OnVUE is available 24/7 year-round, subject to brief maintenance windows, while test-center availability varies by location. Use the Test Center Locator to check local hours and seat availability.
The CPA page lists the price starting at USD 325 for the exam and USD 375 for an exam plus retake, while the scheduling information warns that prices and availability may vary by region. Treat those figures as the published starting listings, not a universal amount. Confirm the amount displayed for your location before payment or voucher purchase.
What does a test-center appointment require?
Arrive at least 15 minutes before the scheduled appointment so that sign-in can be completed. Bring two forms of original, valid, unexpired identification: a primary government-issued ID with your name, recent recognizable photo, and signature, plus a secondary ID with at least a name and signature or a name and recent recognizable photo. Your booking name must match the identification requirements.
What does OnVUE require?
For OnVUE, run the system test on the same device and network you plan to use. Pearson VUE’s listed requirements include a supported Windows or macOS computer, working webcam, microphone, and speaker, one display, a stable internet connection, and the ability to close other applications. VPNs, corporate or public/shared networks, virtual machines, and multiple displays are listed among prohibited or unsuitable arrangements; check the current program policy before booking.
How does online check-in work?
OnVUE check-in includes technology checks, identity verification, photographs, and a 360-degree room scan before a proctor launches the session. Be ready at least 15 minutes before the start, keep the desk and room clear, and have your phone available for check-in only while following the on-screen instructions. Pearson VUE says the process typically takes about 15 minutes but may take longer.
Which scheduling and identification rules can affect your fee?
Treat administrative preparation as part of exam preparation. The C++ Institute says appointments should be scheduled at least one full business day, or 24 hours, in advance, and changes must be made within the authorized window. Its policy states that cancellation less than 24 hours before the appointment forfeits the entire exam fee. A no-show also incurs the exam fee, and arriving more than 15 minutes late can result in refusal of admission without a refund.
Before confirming, check the voucher code, exam version, spelling of your name, time zone, delivery method, and appointment date. The official scheduling page says a confirmation email is sent after scheduling, rescheduling, or canceling. Save that confirmation and use the same account details when communicating with Pearson VUE.
The policies also state that a candidate who fails an exam must wait 15 days before being allowed to re-sit that exam, and a new voucher may be required to launch a retake session. Because policies can be updated and the published material includes different waiting language for some entry-level contexts, verify the current rule for CPA-21-02 directly in the official policy and registration flow before planning a retake.
How should you handle identification?
Check the original-ID requirement well before the appointment. Digital IDs, photocopies, expired IDs, and damaged documents are not acceptable under the cited policies. If your name differs between your Pearson VUE account and your documents, resolve it before scheduling rather than hoping the proctor can correct it at check-in. Candidates requiring accommodations should arrange them through the stated process before booking; registrations with accommodations must be rescheduled or canceled through the Call Center.
What if something goes wrong online?
Use the in-exam chat to contact the proctor, but do not expect the proctor to pause or extend the exam or troubleshoot your device or network. If the computer freezes or disconnects, close and relaunch OnVUE from the downloads folder; if the problem continues, use the customer-service route for the exam program. Keep the workspace compliant while resolving the issue and never access your phone unless the proctor explicitly permits it.
What conduct is prohibited during the appointment?
Online testing requires a private, controlled environment. Pearson VUE states that you must remain alone, keep the desk clear except for approved items, stay within webcam view unless an approved break is confirmed, and avoid speaking or reading aloud unless instructed. You must not record, share, or let another person view the screen, and you must not use a phone, notes, paper, books, headphones, or other prohibited items.
These rules are operational rather than study advice, but a breach can revoke the exam and forfeit the fee. Complete the room scan honestly, remove extra displays and connected devices, clear whiteboards, and tell household members not to enter. For a test center, follow staff instructions about personal-item storage and secure check-in.
The CPA session also requires acceptance of the nondisclosure agreement and testing policies. The policy states that refusing the NDA terminates the session, changes the voucher status to used, and forfeits the exam fee. Read the agreement before the appointment so that the administrative step does not become an avoidable surprise.
What should you do on exam day?
Use a short checklist: verify the appointment and time zone, prepare valid IDs, complete the system test if testing online, close prohibited applications, arrive or begin check-in early, and keep the confirmation details accessible. Once the exam starts, read the full question, identify the tested rule, eliminate options that contradict the language, and mark uncertain items for review if the interface permits.
What should you avoid in preparation materials?
Avoid exam dumps, leaked questions, and memorization claims. They do not establish the ability to write or analyze C++ and may conflict with nondisclosure obligations. Use the published objectives, official learning resources, compiler-based exercises, and original practice questions. The most useful question is not only whether an option is correct, but which language rule makes the alternatives incorrect.
What should you do after the exam or after a setback?
After the exam, the official policy says a score report showing pass or fail and a breakdown becomes available in the User Account under Exam History; successful candidates receive online credentials by email, also available in the account. If you fail, use the breakdown as a diagnostic, respect the applicable retake waiting period, and rebuild the weak skills before purchasing another attempt.
A pass is a point to consolidate, not a reason to stop programming. Review the areas that required the most effort, retain your code exercises, and decide whether the next objective is a project, the professional-level CPP path, or broader C++ library knowledge. The C++ Institute states that certificates are currently issued for a lifetime with no recertification required, but verify future policy changes through the official certification pages.
If scheduling or technical problems caused the result, document the appointment, messages, and error details promptly and contact the relevant Pearson VUE or program support channel. Do not assume that a technical incident automatically pauses the exam, restores a voucher, or creates a free retake; those outcomes depend on the applicable policy and review.
A useful post-result review
For a pass, write down the topics that were least automatic and practise them in real programs. For a fail, classify each weak area as knowledge, tracing, implementation, pacing, or administration. Then choose one corrective action per category: reread the objective, compile a minimal example, trace by hand, complete mixed timed practice, or correct the scheduling setup. This produces a plan rather than a vague instruction to study harder.
What is the best next action?
Start by downloading or reviewing the current CPA-21-02 objectives and marking each item as explain, implement, trace, or unknown. If several fundamentals are unknown, begin with C++ Essentials 1 and continue to C++ Essentials 2. If the foundation is sound, build a block-by-block error log and practise the highest-risk topics first, especially expression behavior, function calls, memory lifetime, and object-oriented dispatch.
Then decide the delivery method before setting a date. Check test-center availability or verify OnVUE technology and room requirements on the same equipment you will use. Confirm identification, name matching, voucher validity, regional price, and the 24-hour change and cancellation rule. Schedule only after your practice evidence and logistics support the same decision.
The official exam and policy pages should remain the authority for the active version, current procedures, accommodations, and appointment terms. This guide supplies a study sequence and decision framework; it does not replace those rules. Your immediate task is simple: map the objectives, close the largest skill gap with code, and schedule when both technical readiness and administrative readiness are credible.
Conclusion
CPA preparation is strongest when it combines language reasoning with deliberate scheduling. Learn the published domains in dependency order, compile and trace your own examples, maintain an error log, and use mixed practice to confirm that knowledge transfers across topics. Before booking, verify CPA-21-02, identification, delivery requirements, regional availability, and the applicable change policy. A candidate who treats memory management, object behavior, and exam administration as practical tasks—not last-minute details—can make a better-informed decision about when and how to test.
Related exams
- AACD exam — American Academy of Cosmetic Dentistry
- ACLS exam — Advanced Cardiac Life Support
- ACT-Test exam — American College Testing: English, Math, Reading, Science, Writing
- ASSET exam — Short Placement Tests Developed by ACT
- ASVAB-Test exam — Armed Services Vocational Aptitude Battery Test: General Science, Arithmetic Reasoning, Word Knowledge, Paragraph Comprehension, Mathematics Knowledge, Electronics Information, Automotive & Shop Information, Mechanical Comprehension, Assembling Objects
- CBEST-Section-1-Math exam — California Basic Educational Skills Test - Math