Adobe CJA Business Practitioner Pro

Items are multiple choice and multiple response (select all that apply), plus scenario-based item sets in which a business situation is described and several questions follow. Scenario sets reward people who read the whole situation before answering. Adobe's certification site publishes the current structure and any delivery details.

Practitioners generally find it conceptually harder despite narrower scope. CJA assumes you understand Experience Platform foundations - datasets, schemas, identities - and forces you to reason about stitching and data view curation rather than panel configuration. If you only know the Analytics UI, budget extra time for the platform layer.

Most comfortable candidates have roughly a year of hands-on CJA or adjacent Experience Platform work, including at least one full connection-to-workspace build. You should be able to explain identity stitching choices, why a component was renamed or hidden, and how a calculated metric differs from a segment without looking it up.

Adobe publishes the current fee, appointment length, passing score, and retake policy on its official certification website, and those figures change periodically. Check that page before you schedule or budget. No third-party source, including this one, should be treated as authoritative for those numbers.

Start with architecture: schemas, datasets, connections, and identity. Then data views and component curation, because everything downstream depends on them. Move to Workspace visualization, then segments and calculated metrics, and finish with attribution, cross-channel identity, and governance. Building one end-to-end project cements the sequence better than reading notes.

Candidates lose points by confusing connection-level and data-view-level settings, forgetting that component naming and hiding affect every downstream report, and misjudging which identity namespace a stitched report actually uses. Another frequent trap is choosing a segment when a calculated metric, or vice versa, was the correct instrument.

No. Items test decisions, not clicks. You will do better understanding why you would create a derived field, hide a component, or change the default attribution model than memorizing where a button sits. Navigation recall rarely decides an outcome on scenario items.

Retake windows and credential validity periods are set by Adobe and are subject to change, so confirm them on the official certification page before you rely on them. Plan your first attempt as if a retake were unavailable - it keeps preparation honest and avoids scheduling pressure.

CJA is built on Experience Platform datasets rather than report suites, so you gain cross-dataset stitching and person-level identity but take on schema and governance responsibility. Fields are curated in data views instead of being largely inherited, which means design decisions early have long-lasting reporting consequences.