Answers to common CFE Day 2 study questions about declared roles, long-case navigation, role depth, common issues, recommendations, and practice timing.
This FAQ covers CFE Day 2 study strategy for the exam-mapped guide pages. Confirm official module rules, dates, registration, accommodations, and candidate administration with CPA Canada or your provincial or regional CPA body.
Use this guide as a structured reading path. Each topic is a chapter, and each terminal lesson explains one exam topic:
Start with declared role and case navigation. Day 2 performance depends on knowing what your role owns, which exhibits matter, and how much depth each issue deserves.
Use the CFE Day 2 study plan to sequence the 32 section lessons. Use the CFE Day 2 cheat sheet before long-case attempts when you need quick checks for declared role, exhibit use, depth allocation, common issues, and supported recommendations.
Begin each major issue with role responsibility and case evidence. Then write the analysis that the role requires: procedure and evidence for Assurance, tax consequence for Taxation, decision support for Finance, or management recommendation for Performance Management.
| Role lens | Strong response habit |
|---|---|
| Assurance | State the risk, evidence need, procedure, documentation, reporting effect, and ethics constraint. |
| Taxation | Classify the taxpayer and transaction, then explain tax consequence, compliance, planning, CRA response, or appeal path. |
| Finance | Use cash, capital, valuation, risk, stakeholder, and implementation evidence to support a decision. |
| Performance Management | Connect strategy, measures, behaviour, controls, systems, and implementation to management advice. |
Do not ignore them, but do not let them consume all role-depth time. Map financial reporting and management accounting issues early, then allocate time based on significance and evidence.
Enough to support the recommendation. A calculation should show the setup, key assumptions, result, and implication. Overbuilding calculations can reduce answer completeness.
Unsupported conclusions. A strong answer ties every recommendation to facts, exhibits, procedures, calculations, documents, controls, deadlines, or stakeholder constraints.
Debrief both coverage and depth. A response can feel technically strong and still be weak if it misses role responsibility, common issues, or sufficiency.
| Debrief question | What to fix |
|---|---|
| Did I state the declared role before analyzing? | Add the role boundary and decision maker before technical detail. |
| Did I map exhibits efficiently? | Link each exhibit to one issue, calculation, procedure, or constraint. |
| Did I cover common competencies? | Add enough financial reporting or management accounting analysis where the case requires it. |
| Did I overwrite one issue? | Reallocate time toward missing assessment opportunities. |
| Did my recommendation have support? | Tie the conclusion to facts, calculations, evidence, documents, controls, or risk. |
Start practice after the role-framing pages. Day 2 skill develops when you repeatedly map exhibits, rank issues, write role-depth analysis, and communicate recommendations under time pressure.