CDEF

The profile lists multiple-choice questions across nine weighted domains. The official certification body publishes the current question count, delivery method, and any item types beyond standard multiple choice on its website; confirm there before booking, since formats are revised periodically.

Most candidates find the conceptual material accessible but the scenario items demanding. Questions often describe a realistic conflict, such as a model that improves accuracy at the cost of disparate impact, and ask for the most defensible next step. Distractors are usually plausible but incomplete answers, so shallow familiarity is not enough.

A reasonable plan is four to eight weeks of part-time study. Start with the foundations and regulatory domains to build vocabulary, then fairness and transparency, then governance and decision frameworks. Finish with emerging technology and organisational culture, which are lighter in weight but easier to revise once the core concepts are solid.

Candidates lose marks by treating compliance with law as the whole of ethics, by ignoring affected stakeholders in scenario answers, and by choosing the most technical option when a governance or process answer is better. Another frequent error is memorising framework names without being able to apply their steps to a described situation.

Retake rules, waiting periods, and any fees are set by the certifying body and change over time. The official website publishes the current retake policy; check it before scheduling so you understand the cost and timing implications of a second attempt.

Scoring methodology and the passing threshold are determined by the certification body and are not fixed in this profile. The official site publishes the current passing score and any domain-level reporting. Do not rely on figures quoted in forums, which are often outdated.

Fees vary by region, membership status, and whether training is bundled. The certification body publishes the current fee schedule on its website. Check there for the authoritative price rather than relying on secondhand summaries.

Read the final question stem first, then scan the scenario for stakeholders, the stated harm, and any legal constraint. Eliminate options that ignore an affected group or leap straight to a technical fix. If two answers seem defensible, prefer the one that includes documentation, review, or escalation.

No single background is required, but the exam assumes comfort with basic data concepts and awareness of privacy regulation. Lawyers may need to work harder on model and data-pipeline questions; engineers may need to work harder on rights, stakeholders, and governance. Fill whichever gap applies to you early.