SAP · Practice Exam · Associate Architect · Updated for 2026

SAP CX Solution Architect (C_C4HCX) Practice Exam

Prepare for the SAP Certified Associate – Solution Architect – Customer Experience exam across its real scope — the features and architecture of SAP CX solutions and SAP BTP, the Intelligent Enterprise and its end-to-end processes, integration and side-by-side extensibility, and clean core — with objective-mapped questions, Learn-mode feedback, and a full timed Exam mode.

Start 24-hour free trial →

This is a CX and BTP exam — and clean core is required reading

SAP’s scope statement names two things: the features and architecture of SAP Customer Experience solutions and SAP BTP. The platform is co-equal, not a footnote. Expect the Intelligent Enterprise and its end-to-end processes, BTP and Extension Suite pillars and commercial models, side-by-side extensibility, Integration Suite capabilities such as Integration Advisor, and Kyma runtime components.

Required preparation: SAP states that you must also take the Managing Clean Core learning journey in addition to the CX journey — and note SAP has renamed it from “for SAP S/4HANA Cloud” to “for SAP Cloud ERP.” Confirm the current outline on the official certification page before scheduling.

500+
Practice questions
80
Questions on exam
2
Study modes
24h
Free trial

SAP CX Solution Architect exam at a glance

Vendor
SAP
Exam code
C_C4HCX_2405
Certification
SAP Certified Associate – Solution Architect – Customer Experience
Level
Associate architect
Scope
The features and architecture of SAP Customer Experience solutions and SAP BTP
Format
80 questions, multiple-choice with single and multiple answer items
Duration
180 minutes (3 hours)
Cut score
63%
Language
English
Experience expected
Two or more years working with SAP Customer Experience solutions; the associate architect performs and guides project tasks within a team
Required preparation
The Managing Clean Core learning journey, in addition to the CX learning journey SAP lists under How to Prepare
Attempts
Up to three attempts per exam version; after that, wait for the next version

Sources: SAP Learning — official certification page · SAP Learning — Managing Clean Core. SAP reserves the right to update exam content, items, and weighting at any time; verify current details before scheduling.

About the SAP CX Solution Architect (C_C4HCX) certification

The SAP Certified Associate – Solution Architect – Customer Experience credential verifies that you understand the features and architecture of SAP Customer Experience solutions and SAP BTP. SAP frames the role precisely: an associate architect with two or more years of CX experience who can perform and provide guidance on project tasks within a team — a working architect, not a chief architect.

Read the scope statement again, because the second half is where preparation usually falls short. SAP BTP is named alongside the CX portfolio, not beneath it. Candidates who prepare by learning which CX solution does what — commerce here, service there — meet an exam that asks about Extension Suite commercial models, side-by-side extensibility patterns, Integration Advisor, Kyma runtime components, and where the Intelligent Enterprise’s end-to-end processes cross system boundaries. SAP also requires the Managing Clean Core journey as preparation, which tells you how it expects extensions to be designed. For where this sits among architect tracks, see the IT certifications guide in our Learning Hub.

SAP CX Solution Architect exam topic areas

SAP publishes the topic list as a guide rather than a guaranteed split, and reserves the right to change content and weighting at any time. The areas below reflect SAP’s scope statement and the subjects consistently reported across the exam — note how much of it lives on the platform side.

SAP CX portfolio architecture

The features and architecture of the CX solutions: commerce, sales, service, marketing and engagement, and customer data — how each is built, what it is for, and how an architect selects among them for a customer scenario.

Core area
SAP BTP and Extension Suite

Named in SAP’s scope statement alongside CX itself: the main pillars of BTP and the Extension Suite, the different commercial models, Kyma runtime components, and when each capability applies to a CX landscape.

Core areaOften underestimated
Integration and extensibility

SAP Integration Suite and its capabilities including Integration Advisor, integration patterns between CX and back-office systems, event-driven versus synchronous design, and side-by-side extensibility as the sanctioned way to extend.

Core area
The Intelligent Enterprise and end-to-end processes

The Intelligent Enterprise framework and its components, and the end-to-end business processes — lead-to-cash chief among them — that cross CX and ERP boundaries and give the architecture its shape.

Tested area
Clean core and architecture principles

Required preparation in its own right: keeping the core clean while extending beside it, upgrade-stable extensions, and the architectural discipline SAP expects across process, integration, extensibility, data, and operations.

Required prep
Customer data and identity architecture

Where identity, consent, and unified profiles live across the landscape, and how customer data flows between CX solutions so personalization has something trustworthy to work from.

Tested area

Areas reflect SAP’s published scope for this certification. SAP notes its topic list is a guide, not a guarantee, and reserves the right to update content, items, and weighting at any time. Source: SAP Learning — official certification page. Confirm the current outline before scheduling.

Who this exam is for

SAP aims this credential at practitioners moving from implementing CX to designing it. It is an experience-gated exam:

  • CX consultants with two or more years of experience stepping up from configuring one solution to designing across several.
  • Solution architects joining a CX programme who need the portfolio and the platform in one credential.
  • Project leads and senior developers moving into architecture, who already know a CX solution deeply and need the integration and extensibility picture.
  • Integration and BTP practitioners whose work lands in CX landscapes and who want the front-office architecture formalized.

Professionals holding this certification commonly work as SAP CX solution architects, CX integration architects, and technical leads on customer experience programmes. Adjacent credentials go deeper on each part: SAP Commerce Cloud, Sales Cloud v2, and Service Cloud v2 for implementation depth; SAP BTP architect for the platform half of this exam’s scope; and CX positioning if you advise rather than design. For the roles this certification supports, see the solution architect career path.

What this CX architect practice exam delivers

Learn mode

Get the correct answer, the explanation, and why each other choice is weaker — immediately after each question. Best for BTP and extensibility scenarios, where several designs work but only one is upgrade-safe.

Exam mode

80 questions, 180-minute timer — the real C_C4HCX format at a 63% cut score, including the multi-select items where SAP states how many answers are correct.

CX and BTP, as SAP scopes it

Practice across Extension Suite, Integration Suite, Kyma, and the Intelligent Enterprise — not just which CX solution covers which channel.

Score by topic area

Results break down across portfolio architecture, platform, integration, and data — so practice tells you exactly which to revisit.

Sample CX Solution Architect practice questions

Ten free questions across the exam’s real scope, with full explanations and source links to SAP resources. The complete bank is available with the 24-hour trial.

Question 1 · CX portfolio architecture

A retailer wants end-to-end customer experience coverage across marketing, e-commerce, sales, service, and customer data. Which portfolio should the architect design with?

  1. SAP S/4HANA Finance, SAP BW/4HANA, and SAP Analytics Cloud
  2. SAP Ariba, SAP Fieldglass, and SAP Concur
  3. SAP Engagement Cloud (the Emarsys lineage), Commerce Cloud, Sales Cloud, Service Cloud, and SAP customer data solutions
  4. SAP SuccessFactors and Qualtrics
Show answer & explanation

Correct: C — Engagement Cloud, Commerce Cloud, Sales Cloud, Service Cloud, and customer data. Those cover marketing and engagement, e-commerce, selling, service, and the profile layer underneath — note SAP now presents the Emarsys lineage as Engagement Cloud, so recognise both names.

Why not the others: finance and analytics (A) are back-office; Ariba, Fieldglass and Concur (B) are spend management; and SuccessFactors with Qualtrics (D) is HCM and experience management — none is the CX portfolio.

Source: SAP — Customer Experience and CRM → Further reading: PowerKram — CX positioning →
Question 2 · SAP BTP and Extension Suite

How does SAP BTP support extending CX solutions in an architecture?

  1. Through side-by-side extensions, custom services, and integration flows that extend CX capabilities without modifying the standard solutions
  2. By requiring extensions to be built directly in each CX solution’s codebase
  3. By providing database hosting for CX solutions and nothing more
  4. BTP cannot be used with CX solutions
Show answer & explanation

Correct: A — Side-by-side extensions, custom services, and integration flows. Building beside the standard solution rather than inside it is what keeps the extension upgrade-stable — the clean core principle SAP requires you to study for this exam.

Why not the others: extending inside the codebase (B) is the modification anti-pattern clean core exists to prevent; database hosting only (C) understates the platform enormously; and claiming BTP is unusable with CX (D) contradicts SAP’s own scope statement for this credential.

Source: SAP — App development and automation on BTP → Further reading: PowerKram — SAP BTP architect →
Question 3 · Integration and extensibility

How does the Integration Advisor capability accelerate integration development? (SAP states two answers are correct; pick the pairing that is genuinely supported.)

  1. By offering SAP methodology templates for integration strategy, and by assigning advisory consultants
  2. By providing SAP advisory consultants to support go-lives, and by generating flow artifacts
  3. By replacing the need for any integration flow, and by auto-deploying to production
  4. By generating artifacts for creating an integration flow in SAP Cloud Integration, and by using a machine-learning proposal service based on crowd sourcing
Show answer & explanation

Correct: D — Generating integration flow artifacts, plus an ML-based proposal service using crowd sourcing. Integration Advisor speeds up mapping work by proposing mappings learned across many implementations and then generating the artifacts you drop into Cloud Integration.

Why not the others: advisory consultants (A, B) are a service offering, not a product capability; and replacing integration flows or auto-deploying to production (C) invents behaviour Integration Advisor does not have.

Source: SAP — Integration Suite →
Question 4 · The Intelligent Enterprise and end-to-end processes

An architect must integrate CX front-office solutions with SAP S/4HANA for lead-to-cash. What approach should they recommend?

  1. Manual data re-entry between front-office and back-office systems
  2. API-based integration using SAP Integration Suite with pre-built content for CX-to-S/4HANA scenarios
  3. Replacing S/4HANA with CX solutions entirely
  4. No integration — the front and back office should stay independent
Show answer & explanation

Correct: B — API-based integration via Integration Suite with pre-built content. Lead-to-cash is an end-to-end process that crosses the CX and ERP boundary, and SAP ships packaged integration content for exactly these scenarios rather than expecting a bespoke build.

Why not the others: manual re-entry (A) breaks the process it is meant to serve; replacing the ERP (C) misreads complementary systems as competing ones; and independence (D) is what makes a customer promise the business cannot fulfil.

Source: SAP — Integration Suite → Further reading: PowerKram — SAP Commerce Cloud →
Question 5 · Customer data and identity architecture

How should customer data be architected across the CX landscape so every touchpoint recognises the same person?

  1. Each CX solution maintains its own isolated customer database
  2. All customer data lives only in the S/4HANA business partner master
  3. Identity and consent handled by SAP’s customer data solutions, with unified profiles available for activation across the CX solutions
  4. Customer data does not need to flow between CX solutions
Show answer & explanation

Correct: C — Identity and consent in the customer data layer, with unified profiles activated across CX. Separating identity and consent from the applications that use them is what lets commerce, marketing, sales, and service act on one coherent view of the customer.

Why not the others: isolated databases per solution (A) guarantee contradictory experiences; the ERP business partner master (B) is not built for anonymous-to-known CX profiling; and no data flow at all (D) removes the basis for personalization entirely.

Source: SAP — Customer Experience and CRM → Further reading: PowerKram — SAP Customer Data Cloud →
Question 6 · SAP BTP and Extension Suite (Kyma)

A solution must assess fraud risk at order placement, with rules that change as business needs change. Which BTP Kyma runtime approach fits?

  1. A serverless function triggered by the order event, so the rule logic can be changed and redeployed independently of the storefront
  2. Hard-coding the fraud rules into the Commerce Cloud storefront
  3. A nightly batch job that reviews orders after they have been placed
  4. Manual review of every order by the fraud team
Show answer & explanation

Correct: A — A serverless function triggered by the order event. Kyma’s functions give you an event-driven, independently deployable place for volatile logic — which is exactly what “rules may change from time to time” is asking for, and it keeps the storefront clean.

Why not the others: hard-coding into the storefront (B) means a release cycle for every rule change and breaks clean core; a nightly batch (C) checks after the order is already placed; and manual review (D) does not scale to order volume.

Source: SAP — App development and automation on BTP →
Question 7 · Integration and extensibility

When should an event-driven pattern be preferred over synchronous integration between CX solutions?

  1. For every interaction, regardless of requirements
  2. Never — synchronous integration is always correct in CX
  3. For real-time notifications, asynchronous updates, and decoupled processing where an immediate response is not required
  4. Only when the systems are in the same data centre
Show answer & explanation

Correct: C — Notifications, asynchronous updates, and decoupled processing. Events suit work that can complete independently of the caller; synchronous calls remain right when the caller genuinely needs the answer before proceeding, such as a payment authorization.

Why not the others: events for everything (A) forces asynchrony onto transactions that need an answer now; never using events (B) discards decoupling entirely; and a data-centre condition (D) is not what drives the choice.

Source: SAP — Integration Suite →
Question 8 · Clean core and architecture principles

SAP requires the Managing Clean Core journey as preparation for this certification. What does clean core mean for a CX architecture?

  1. Extensions are built inside the standard solutions so they stay close to the code they modify
  2. Custom code is avoided entirely, so no extensions are ever built
  3. The core is kept clean by deleting unused data at year end
  4. Extensions are upgrade-stable and follow SAP’s extensibility model, with standard integration and good data quality, so the core stays current
Show answer & explanation

Correct: D — Upgrade-stable extensions following SAP’s extensibility model, with standard integration and sound data. Clean core spans several dimensions — process, integration, extensibility, data, operations — and the point is a core that can take the next release without a rescue project.

Why not the others: extending inside the standard solution (A) is the practice clean core replaces; never extending (B) confuses discipline with paralysis; and deleting data at year end (C) mistakes housekeeping for architecture.

Source: SAP Learning — Managing Clean Core →
Question 9 · CX portfolio architecture (marketing)

A customer asks which SAP solution runs personalized omnichannel campaigns, and under what name it is presented today.

  1. SAP Commerce Cloud, which owns all customer-facing communication
  2. SAP Engagement Cloud — the omnichannel marketing and engagement solution, previously presented as Emarsys
  3. SAP Analytics Cloud, which delivers campaign dashboards
  4. SAP Service Cloud, since campaigns follow support cases
Show answer & explanation

Correct: B — SAP Engagement Cloud, the Emarsys lineage. SAP’s own Emarsys product page now redirects to Engagement Cloud, so an architect should recognise both names and lead with the capability — omnichannel marketing and engagement.

Why not the others: Commerce Cloud (A) runs the storefront; Analytics Cloud (C) reports on outcomes rather than executing campaigns; and Service Cloud (D) handles support, which follows the campaign rather than driving it.

Source: SAP — Engagement Cloud →
Question 10 · CX portfolio architecture (scalability)

The architecture must absorb a large traffic spike during a seasonal sale without degrading. What should the architect plan?

  1. Deployment on a single fixed-capacity server sized for the peak
  2. Cloud-native auto-scaling, a CDN for content delivery, and load testing against peak-traffic simulations
  3. Limiting customer access during peak periods
  4. Accepting that scalability cannot be planned for in a CX architecture
Show answer & explanation

Correct: B — Auto-scaling, CDN, and load testing. Elastic capacity handles the surge, the CDN takes static delivery off the origin, and load testing is what turns the plan from a hope into a measurement before the sale starts.

Why not the others: fixed capacity (A) means paying for the peak year-round and still guessing wrong; limiting access (C) discards revenue at the moment it is available; and treating scalability as unplannable (D) abandons a core architect responsibility.

Source: SAP — Commerce Cloud → Further reading: PowerKram — Sales Cloud v2 →

Keep going: Learning & Career resources

CX architecture spans the front office and the platform beneath it — and it opens onto senior architect roles. Two PowerKram hubs back this exam.

Deep dive: the BTP half, clean core, exam mechanics, and study path

Half this exam lives on the platform

SAP’s scope statement is one sentence and worth memorizing: this certification verifies understanding of the features and architecture of SAP Customer Experience solutions and SAP BTP. Candidates read the exam title, see “Customer Experience,” and prepare a portfolio tour. Then the paper asks about Extension Suite pillars and commercial models, Kyma runtime components, Integration Advisor, and side-by-side extensibility. If you cannot currently explain what BTP’s commercial models are or when you would reach for a Kyma function, that is where your study time should go first. SAP’s official certification page →

Clean core is required, not suggested

SAP states plainly that to prepare for this certification it is necessary to take the Managing Clean Core learning journey in addition to the CX journey. That is unusual phrasing and it tells you something: SAP expects a CX architect to design extensions that survive upgrades. Clean core spans process, integration, extensibility, data, and operations — so when a question offers a technically workable design that modifies a standard solution and a slightly more indirect one that extends beside it, the second is the answer. Note the journey has been renamed from “for SAP S/4HANA Cloud” to “for SAP Cloud ERP.” SAP Learning — Managing Clean Core →

The Intelligent Enterprise is the frame

Reported questions consistently reach into the Intelligent Enterprise framework and its end-to-end business processes — lead-to-cash above all. That is the frame the architecture hangs on: a customer promise made in the storefront or by a sales rep has to survive the handover into fulfilment and billing. Know which processes cross the CX and ERP boundary, where the packaged integration content sits, and what breaks when the handover is missing. SAP — Integration Suite →

Names move; capabilities do not

The CX portfolio has been renamed repeatedly, and an architect who memorized a product list gets stranded. The clearest current example: SAP’s Emarsys product page now redirects to SAP Engagement Cloud. Lead with the capability — omnichannel marketing and engagement, storefront and catalog, selling, service, identity and profiles — and treat the label as a detail you refresh before the exam rather than the thing you learned. SAP — Engagement Cloud →

Exam mechanics and study path

80 questions in 180 minutes at a 63% cut score — a more forgiving bar than most SAP associate exams, with over two minutes per question. SAP expects two or more years of hands-on CX experience, and you get three attempts per exam version before waiting for the next release. Work the CX learning journey and the Managing Clean Core journey, then use objective-mapped practice to find whether your gap is the portfolio or the platform — for most candidates coming from implementation, it is the platform. SAP BTP architect on PowerKram →

Frequently asked questions

How many questions is the exam, and what is the cut score?

80 questions in 180 minutes with a 63% cut score, in English. The exam uses multiple-choice items with single and multiple correct answers — SAP states how many to select on multi-answer questions. You get up to three attempts per exam version.

Is this exam only about the SAP CX solutions?

No. SAP’s scope statement names the features and architecture of SAP Customer Experience solutions and SAP BTP. Expect questions on the Extension Suite pillars and commercial models, Kyma runtime components, Integration Suite capabilities such as Integration Advisor, and side-by-side extensibility alongside the CX portfolio itself.

Is there a required learning journey beyond the CX one?

Yes. SAP states that to prepare for this certification it is necessary to take the Managing Clean Core learning journey in addition to the journey listed under How to Prepare. SAP has renamed that journey from “Managing Clean Core for SAP S/4HANA Cloud” to “Managing Clean Core for SAP Cloud ERP,” so search the current name.

How much experience does SAP expect?

Two or more years working with SAP Customer Experience solutions. SAP describes the associate architect as someone who can perform and provide guidance on various project tasks within a project team — a working architect contributing to a team rather than owning the enterprise architecture.

Is SAP Emarsys still called Emarsys?

SAP now presents that lineage as SAP Engagement Cloud — its own Emarsys product page redirects there. Older material and some certification titles still use the Emarsys name, so recognise both and lead with the capability (omnichannel marketing and engagement) rather than the label.

Start your free 24-hour CX Solution Architect practice trial

Full access to the question bank, both study modes, and score-by-topic feedback. No credit card required.

Start free trial →