DEA Level 3

It is a multiple-choice exam delivered in a single sitting, covering all six domains. Expect scenario-based stems rather than pure recall, with four options and one best answer. Confirm the current delivery method (test centre or remote proctored) and any scheduling rules on the certifying body's official site before booking.

Question count and time limit are set by the certifying organisation and can change between exam versions. Rather than rely on second-hand figures, check the official programme page for the current blueprint, duration and number of items, then practise pacing yourself at roughly one minute per question as a starting benchmark.

It is pitched at experienced practitioners, so the difficulty comes from breadth and from questions that cross domains rather than from obscure trivia. Candidates with several years of hands-on data work usually find the technical domains manageable; the common struggle is governance, compliance and strategy vocabulary, which rewards deliberate study.

Retake rules, waiting periods and any associated costs are set by the certifying body and are not fixed across programmes. Look up the current retake policy on the official site before you sit the exam, and factor a possible second attempt into your schedule and budget so a single bad day does not derail your plans.

Start with the two heaviest domains, data management and governance, and data architecture and modeling, because they underpin the rest. Then work through integration and analytics, which reward hands-on practice. Finish with security, privacy and compliance, then strategy and delivery, which are lighter in weight and mostly conceptual.

Three recur: neglecting the lower-weighted domains entirely and losing easy marks; memorising definitions without being able to apply them to a scenario; and misreading stems that ask for the best or first action rather than a correct statement. Practise eliminating options and justifying your choice before checking the answer.

Self-study can cover the terminology, but the scenario questions assume you have seen real trade-offs: schema choices, pipeline failures, access-control decisions, stakeholder pushback. If your experience is narrow, build small projects or walkthroughs in the domains you have not touched, and read case studies for the rest.

Use them diagnostically, not as a memory drill. Take a mixed set, log every miss by domain and by reason (unknown fact, misread stem, wrong reasoning), then revisit the underlying topic. Retake only after studying, and track whether your weak domains improve rather than your overall score alone.

The passing standard is set and periodically revised by the certifying organisation, and it is not published in a single fixed place for all candidates. Check the official programme documentation for the current scoring scale and passing threshold rather than relying on figures quoted in forums or study guides.