More study resources

About this exam

The Certified Web and Internet Data Professional (CWIDP) is an independent credential aimed at practitioners who collect, clean, store, analyse and report on data sourced from the web. It suits data analysts, web analysts, ETL and pipeline developers, marketing and product analysts, and data stewards who regularly work with scraped, API-sourced, or log-derived datasets. The exam is delivered in multiple-choice format and spans eight domains: web acquisition; data quality, cleaning and validation; data modelling and storage; analysis and statistical methods; visualisation and reporting; privacy, ethics and regulatory compliance; security and governance; and infrastructure and automation. Expect questions that test judgement as much as recall - for example, choosing a sampling approach, spotting a validation gap in a pipeline, or recognising when a collection method creates a consent or licensing problem. Because the exam is broad rather than deep in any single tool, preparation should combine hands-on practice with the technologies you already use and deliberate study of the domains you rarely touch. Build a small end-to-end project: acquire data from a public API or permitted scrape, validate and clean it, model it in a relational or columnar store, analyse it, and publish a chart with a written caveat. Then review each domain against that project. The awarding body publishes current details on question count, duration, fees, passing scores and retake rules on its official website; confirm these there before booking, as this page does not restate them.

What you'll study

Common questions

About CWIDP preparation

What format is the CWIDP exam?

It is a multiple-choice examination covering the eight published domains. Questions are scenario-based as well as factual, so you may be asked to pick the best validation step or the most defensible consent practice rather than recall a definition. The awarding body's site confirms current delivery mode, whether that is test centre or remote proctored.

How hard is the exam?

Candidates with a year or two of practical web data work generally find the acquisition, quality and analysis domains comfortable. Difficulty concentrates in the governance, privacy and infrastructure domains, which many analysts meet only indirectly. Breadth is the real challenge: eight domains at 5-20 percent each means you cannot skip weak areas and expect to pass on strength alone.

How long is the exam and how many questions?

The official body publishes the current question count and time limit on its website, and they can change between delivery windows. Check there before you book so you can practise at the right pace. As a planning habit, rehearse answering scenario questions in well under a minute each, leaving time to revisit flagged items.

What score do I need to pass, and what does it cost?

Passing scores and fees are set and published by the awarding body, not by this page. Confirm both on the official site, along with any regional pricing or membership discounts. Do not rely on figures quoted in forums or older study guides, since scoring scales and pricing are revised periodically.

Can I retake it, and how soon?

Retake policy, waiting periods and any additional fees are defined by the awarding body and published officially. Check the current rules before sitting the exam, because some programmes impose a mandatory delay after a failed attempt. If you do fail, request your domain-level score report and target the weakest domains before rebooking.

In what order should I study the domains?

Follow the data lifecycle: acquisition, then quality and validation, then modelling and storage, then analysis, then visualisation. Study privacy and governance alongside acquisition, because consent and licensing decisions happen at collection time. Finish with infrastructure and automation, which ties the pipeline together. Weight your time by domain percentage but never abandon a low-weight domain.

Why do candidates fail?

The most common cause is over-preparing on tool specifics and under-preparing on judgement: candidates can write a scraper but cannot explain when scraping is inappropriate. Others neglect governance and privacy entirely, or misread scenario stems that ask for the best answer rather than a workable one. Weak statistics fundamentals, especially sampling and confounding, also cost marks.

Do I need to know a specific programming language or tool?

The exam tests concepts and judgement rather than syntax, so no single vendor or language is required. That said, fluency in one language for data work and one SQL dialect makes the modelling and analysis questions far easier to reason about. Practise on real data; abstract reading alone rarely prepares you for scenario items.

How should I prepare in the final two weeks?

Take timed practice sets under exam conditions, then review every wrong answer by domain rather than by question. Write short explanations of why each distractor is wrong; this exposes shallow understanding quickly. Re-read your weakest two domains, and confirm logistics such as identification requirements and session rules on the official site.