Checkmarx CxCE
Checkmarx Certified Engineer (CxCE)
More study resources
Cheat sheet
Keep the key ideas within reach.
ExploreKey terms
Get comfortable with the vocabulary.
ExploreStudy plan
Give each week a clear focus.
ExploreCommon mistakes
Understand the traps and how to avoid them.
ExploreCase studies
Put your knowledge to work in context.
ExploreExam-day guide
Prepare for the day ahead.
ExploreAbout this exam
The Checkmarx Certified Engineer (CxCE) credential is aimed at security engineers, DevSecOps practitioners, and application security leads who administer and operate Checkmarx in real delivery pipelines rather than merely reading scan reports. It tests the working knowledge that separates someone who can install the platform from someone who can keep it producing trustworthy, actionable results across many projects and teams. Coverage spans static analysis fundamentals and secure coding concepts, platform architecture and administration, scan configuration through projects, presets, queries, and scheduling, results triage and false positive management, CxQL custom query development, IDE and CI/CD integration via plugins, CLI, and automation, remediation guidance and reporting, and open-source risk through software composition analysis. Expect scenario-based multiple choice: a noisy project, a broken pipeline gate, a query that returns too much, a deployment that will not scale. Preparation should be hands-on. Build a lab instance, scan deliberately vulnerable applications in more than one language, write and tune your own CxQL queries, wire a scan into a CI job, and practice triaging findings with written justification. Supplement lab work with vendor documentation and secure coding references. The certification body publishes current details on format, duration, pricing, and scoring on its official site; confirm those figures there before booking.
What you'll study
About Checkmarx CxCE preparation
What is the exam format?
It is delivered as multiple choice with scenario-based items, so many questions describe a concrete situation and ask for the best next action rather than a definition. Confirm the current delivery method, item count, and timing with the certification body, which publishes those details on its official site.
How difficult is the CxCE?
Candidates with regular hands-on platform administration and pipeline work generally find it manageable; those who have only consumed scan reports find the configuration and CxQL sections hardest. Difficulty is less about trivia and more about judgment under realistic constraints, so lab time matters more than memorization.
What happens if I fail, and can I retake it?
Retake eligibility, waiting periods, and any associated costs are set by the certification body and can change. Check the official site for the current retake policy before scheduling, and plan your first attempt as if it were the only one so you prepare to the full scope.
How long is the certification valid?
Validity periods and recertification requirements are published by the certification body and are not fixed across programs. Consult the official site for the current validity term and the process for renewal, including whether continuing education or a repeat exam is required.
In what order should I study the domains?
Start with SAST fundamentals and secure coding so findings make sense, then platform architecture and administration, then scan configuration. Move to triage and CxQL together, since query tuning depends on understanding false positives. Finish with CI/CD integration, remediation reporting, and SCA, which build on everything prior.
What are the most common failure modes?
Weak CxQL fluency is the big one: candidates can read queries but cannot write or narrow one. Others include confusing preset selection with query editing, treating false positive marking as a substitute for root-cause analysis, and misunderstanding how incremental versus full scans affect results and pipeline gates.
Do I need programming experience?
Yes, practically speaking. Custom query development and remediation guidance both assume you can read source code in at least one language and understand data flow from user input to a sink. Experience with more than one language helps, because scan behavior and query coverage differ across them.
How much hands-on lab work should I do?
Enough that configuration choices become reflexes. Scan a deliberately vulnerable application, tune a preset, write a custom query, integrate a scan into a CI job, and triage a batch of findings with written justifications. A few focused weeks of this beats months of reading documentation alone.
Where do I confirm fees, dates, and scoring?
Only from the certification body's official site. Pricing, scheduling windows, passing standards, and any published pass rates are set there and change over time, so verify before you book rather than relying on forum posts or training material of unknown age.