CDDP

It is a multiple-choice exam delivered in English, covering the eight published domains in fixed proportions. The official body publishes the current question count, time limit, and delivery method on its site. Expect scenario-based items, not just recall, so practise applying concepts to short business situations rather than memorising glossaries.

Difficulty is moderate: the breadth across eight domains is the main challenge, not any single topic. Most candidates need a few weeks of structured study. Spend time proportional to the weights, starting with Governance and Architecture (15% each), and do not neglect the smaller domains, which still carry 10–12% each.

Retake rules, waiting periods, and any fees are set by the certifying body and can change. Check the official website for the current retake policy before scheduling. In practice, candidates who fail usually do so on two or three weak domains, so request or reconstruct your domain-level results and target those areas before rebooking.

The official body publishes the current question count and time limit; confirm them on its website when you register. As a planning heuristic, aim for roughly one minute per multiple-choice question and leave time to flag and revisit uncertain items. Practise with a timer so pacing is automatic on exam day.

Start with Data Governance and Ethics and Data Architecture and Modeling, because governance vocabulary and modelling concepts recur in later questions. Then move to Storage and Integration, Quality and MDM, and Security and Privacy, which build on architecture. Finish with Analysis and Statistics, Visualization, and Platforms, and do mixed-topic practice in the final week.

Candidates typically lose marks by confusing similar concepts (for example, data lake versus data warehouse, or encryption versus tokenisation), ignoring governance and ethics in technical scenarios, misreading statistics questions about sampling and significance, and choosing the most technically advanced answer when the question asks for the most appropriate business solution. Read the stem carefully.

The exam is vendor-neutral, so tool-specific syntax is unlikely to be tested, but you should be comfortable reading SQL, interpreting joins and aggregations, and explaining basic statistics such as mean versus median, sampling error, correlation versus causation, and confidence intervals. Hands-on practice makes these concepts stick better than reading alone.

The certifying body sets the scoring method and passing standard and publishes the current figure on its official site; this page does not state a number because it changes. Your score report may show performance by domain, which is the most useful feedback for planning a retake or filling knowledge gaps.

It signals breadth across the data lifecycle, which suits analysts, engineers, stewards, and consultants who need to talk credibly to both technical and business stakeholders. Its value depends on your role and region. Check whether employers in your market list it, and pair it with a portfolio or hands-on project to demonstrate practical skill.