CDGT

Questions are multiple choice, covering the nine published domains. Each domain carries a stated weight, with fundamentals, test design and functional gameplay testing the largest at 15 percent each. The official body publishes the current question count, time limit and delivery method on its site, so check there rather than relying on second-hand figures.

People with hands-on QA experience usually find the vocabulary domains straightforward and the judgement domains harder. The tricky part is choosing between two plausible answers when both sound reasonable. Candidates who have only read about testing tend to underestimate how much the exam rewards concrete reasoning about risk, reproducibility and player impact.

Retake rules, waiting periods and any fees are set by the certifying body and can change. Check the official site for the current policy before you book your first attempt, and plan your preparation as though you only get one shot, because that produces better study habits than budgeting for a retake.

Most candidates need several weeks of steady work rather than a weekend of cramming. A useful pattern is one domain per study session, followed by writing your own practice scenarios. Spend extra time on the domains you have never touched professionally, usually certification compliance, localisation and accessibility, and metrics.

Start with fundamentals and test design, because later domains assume that vocabulary. Then work through functional gameplay, defect reporting and triage, and platform certification. Finish with multiplayer, performance, localisation and accessibility, and tools and metrics, which are easier to absorb once you can already reason about test coverage.

Three patterns recur: treating a bug report as a place to assign blame rather than describe reproduction steps; confusing severity with priority; and proposing exhaustive manual coverage where a risk-based sample is the better answer. Another common miss is ignoring platform certification requirements until late, when they constrain design decisions.

No, but the tools and automation domain expects you to know what automation is good for and where it fails, such as scripted smoke tests versus exploratory play. Being able to read a log file, capture a reliable reproduction, and interpret basic performance data matters more than writing code.

Recognition varies by employer. The credential signals structured knowledge, but studios still weigh portfolios, bug-writing samples and platform-specific experience heavily. Treat it as a complement to practical evidence, such as a well-documented test plan or a set of clear, reproducible defect reports you can show.

Scoring method and the passing threshold are set by the certifying body and are not fixed for all time. The official site publishes the current passing score and any domain-level requirements. Do not rely on numbers quoted in forums, since they are frequently outdated or simply guessed.