SAP Customer Data Cloud (C_C4H62) Practice Exam
Prepare for the SAP Certified Associate – Implementation Consultant – SAP Customer Data Cloud exam across all four published topic areas — managing clean core, Console administration and configuration, the data schema, and customer identity and Site Groups — with objective-mapped questions, Learn-mode feedback, and a full timed Exam mode.
Start 24-hour free trial →SAP calls this the development consultant profile
This is not a features-and-benefits exam. SAP states the credential verifies the core skills required for the development consultant profile and in-depth technical skills, and its published objectives name the Web SDK and REST API, the schema editor and accounts.setSchema calls, the Identity and Data Store, Site Groups, lite versus full screen-sets, account linking, workflows, and Risk-Based Authentication.
SAP publishes four topic areas: Managing Clean Core, Console – Administration and Configuration, Data Schema, and Customer Identity and Site Groups. Material that stops at “CDC does CIAM and consent” covers about a quarter of it. Confirm the current outline on SAP Learning before scheduling.
SAP Customer Data Cloud exam at a glance
- Vendor
- SAP
- Exam code
- C_C4H62_2408
- Certification
- SAP Certified Associate – Implementation Consultant – SAP Customer Data Cloud
- Level
- Associate — SAP recommends it as an entry-level qualification
- Profile
- Development consultant; SAP expects in-depth technical skills and positions the outcome as contributing to a CDC project team in a mentored role
- Blueprint
- Four topic areas: Managing Clean Core; Console – Administration and Configuration; Data Schema; Customer Identity and Site Groups
- Format
- 80 questions, multiple-choice with single and multiple answer items
- Duration
- 180 minutes (3 hours)
- Cut score
- 66%
- Language
- English
- Product heritage
- SAP Customer Data Cloud was formerly Gigya; the Gigya name still appears in SDK and API artefacts
Sources: SAP Learning — Implementing SAP Customer Data Cloud · SAP Learning — Managing Clean Core. SAP notes its topic list is a guide, not a guarantee, and reserves the right to update content, items, and weighting at any time.
About the SAP Customer Data Cloud (C_C4H62) certification
The SAP Certified Associate – Implementation Consultant – SAP Customer Data Cloud credential verifies that you can implement SAP Customer Data Cloud — formerly Gigya — as a member of a project team in a mentored role. It covers customer identity and access management, the data schema behind it, consent and preferences, and the Console where all of it is configured. SAP recommends it as an entry-level qualification for the CDC track.
The word that reframes your preparation is in SAP’s own description: development consultant profile. SAP expects in-depth technical skills, and the published objectives back that up — developing your site with the Web SDK and REST API, creating and updating schema fields with the schema editor and accounts.setSchema, working with the Identity and Data Store, and configuring Site Groups, single sign-on, and Risk-Based Authentication. If your mental model is “CDC handles logins and consent,” that is the marketing summary, not the exam. For the identity and privacy vocabulary underneath, the enterprise security practices guide in our Learning Hub is a useful companion.
SAP Customer Data Cloud exam topic areas
SAP publishes four topic areas for this exam. SAP notes the list is a guide rather than a guaranteed split and reserves the right to change content and weighting — but the four areas tell you plainly where the exam lives, and three of them are technical.
Customer Identity policies and their options; lite versus full screen-sets, social login, account linking, workflows, and progressive profiling; Site Groups with their parent and child structure and shared database; single sign-on; and Risk-Based Authentication.
The Identity and Data Store; creating and updating schema fields with the schema editor and REST API calls; the profile, data, subscriptions, and preferences objects; field types, encryption, required fields, and client-side write access.
Working in the CDC Console: adding a site and generating its API key, site settings and trusted site URLs, data centre selection and residency, permissions and policies, and the administration tasks an implementation consultant owns.
The clean core discipline SAP now attaches to its implementation credentials: extend beside the standard rather than modifying it, use released integration, and keep the implementation upgrade-stable across process, integration, extensibility, data, and operations.
Topic areas reflect SAP’s published outline for this exam version. 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 — Implementing SAP Customer Data Cloud. Confirm the current outline before scheduling.
Who this exam is for
SAP aims this credential at people implementing CDC on real projects. It is entry-level in seniority but technical in content:
- Implementation consultants on CDC and Gigya deployments who configure identity, schema, and consent for customer-facing sites.
- Digital and CX engineers integrating customer identity data across web, mobile, and APIs.
- Developers joining a CDC project who will work with the Web SDK, REST API, and screen-sets and want the platform model formalized.
- Project members responsible for privacy, consent, and data governance who need to understand the schema and policies the compliance story rests on.
Professionals holding this certification commonly work as SAP Customer Data Cloud consultants, CIAM consultants, and customer identity engineers. Adjacent credentials cover the neighbouring ground: SAP Customer Data Platform for the profile-unification and activation layer, CX Solution Architect for designing across the portfolio, and SAP Commerce Cloud for the storefront CDC most often fronts. For the roles this certification supports, see the cybersecurity specialist career path.
What this Customer Data Cloud practice exam delivers
Learn mode
Get the correct answer, the explanation, and why each other choice is wrong — immediately after each question. Best for schema and Site Group questions, where the platform model is unintuitive until it clicks.
Exam mode
80 questions, 180-minute timer — the real C_C4H62 format at a 66% cut score, including the multi-select items where SAP states how many answers are correct.
Technical, as SAP scopes it
Practice across the Web SDK and REST API, schema objects, the Console, and Site Groups — not just the CIAM and consent talking points.
Score by topic area
Results break down across all four published areas, so practice tells you exactly which to revisit before you book.
Sample Customer Data Cloud practice questions
Ten free questions across the four published topic areas, with full explanations and source links to SAP resources. The complete bank is available with the 24-hour trial.
What is the primary function of SAP Customer Data Cloud?
- Employee identity management for internal systems
- Customer identity and access management — registration, login, and profile management for customer-facing sites
- SAP system user provisioning
- Server infrastructure access control
Show answer & explanation
Correct: B — Customer identity and access management. CDC is CIAM: it handles registration, login, and profiles for a company’s customers, which is a different discipline from managing employees or system users.
Why not the others: employee identity (A) and SAP user provisioning (C) are workforce identity domains handled by different tools entirely; and server access control (D) is infrastructure security, several layers below a customer registration flow.
Source: SAP — Customer Experience and CRM → Further reading: PowerKram — SAP Customer Data Platform →A company owns several sites and wants a different experience on each, but one unified user database and a central place for configuration. What should the consultant configure?
- A separate CDC tenant per site, synchronized nightly
- One site with a single screen-set reused across every domain
- A Site Group, where a parent API key holds the shared database and global settings and child sites inherit most settings
- Independent sites, with users asked to register again on each
Show answer & explanation
Correct: C — A Site Group with a parent and child sites. The parent is not a live site: it is an API key holding the group’s database and global settings, and child sites inherit permissions and policies from it while overriding what they need to.
Why not the others: separate tenants with nightly sync (A) defeats the unified database; one site with one screen-set (B) gives up the per-site experience; and independent sites (D) force re-registration, which is the problem being solved.
Source: SAP Learning — Implementing SAP Customer Data Cloud →A consultant needs to add custom fields to store loyalty data on customer accounts. Which schema object should they extend, and how?
- The profile object, by adding new fields to it through the schema editor
- The data object, using the schema editor or an
accounts.setSchemaREST call - The preferences object, since it holds all custom values
- No custom fields are possible; only out-of-the-box profile fields exist
Show answer & explanation
Correct: B — The data object, via the schema editor or accounts.setSchema. The data object is where custom fields live, and you can set field names, types, formatting, encryption, and client-side access restrictions there.
Why not the others: the profile object (A) is SAP’s out-of-the-box set, and you may not add or remove its fields — only restrict or encrypt them; the preferences object (C) belongs to consent management; and claiming no custom fields exist (D) contradicts the platform’s dynamic schema.
Source: SAP Learning — Implementing SAP Customer Data Cloud → Further reading: PowerKram — Enterprise security practices →Which statement about the SAP Customer Data Cloud Accounts Storage is accurate?
- It requires a fixed schema defined before any data is written
- It is a relational database requiring joins across normalized tables
- It stores data without indexing, so searches require an external engine
- It is a fully indexed, dynamic-schema store that supports SQL-like search across the user base
Show answer & explanation
Correct: D — Fully indexed with a dynamic schema and SQL-like search. The storage indexes data as it arrives and accepts custom structures without prior schema creation, which is why accounts.search can query the whole user base with a SQL-like interface.
Why not the others: a fixed up-front schema (A) is exactly what a dynamic schema avoids; a normalized relational model (B) misdescribes the store; and no indexing (C) contradicts the fully-indexed design that makes search work.
Source: SAP Learning — Implementing SAP Customer Data Cloud →A developer wants branded registration screens on their own web pages rather than pages hosted by SAP. What approach fits?
- Build the screen-sets with the UI Builder and render them on your own pages via the Web SDK, tweaking the generated markup as needed
- Modify the SAP-hosted login page’s source code directly
- Accept the standard screens, which cannot be branded
- Rebuild registration from scratch with no CDC involvement
Show answer & explanation
Correct: A — UI Builder screen-sets rendered through the Web SDK on your own pages. The UI Builder is effectively a markup generator: export the markup, paste it into your page, and extend it while CDC powers the flow behind it.
Why not the others: modifying SAP-hosted page source (B) is not available and would not survive updates; unbrandable standard screens (C) is false; and rebuilding without CDC (D) throws away the identity platform you are implementing.
Source: SAP Learning — Implementing SAP Customer Data Cloud →A customer must comply with data residency rules for European users. What does the consultant need to know about site creation in the Console?
- Data residency cannot be controlled in a cloud platform
- All sites store data in a single global data centre regardless of configuration
- Residency is handled after go-live by exporting and re-importing user data
- A site is created in a specific data centre and user data is physically stored there; a global site can also route storage by the user’s residency
Show answer & explanation
Correct: D — The site’s data centre determines where user data physically lives, and a global site can store by residency. That choice is made when the site is created in the Console, which makes it an early decision with compliance consequences.
Why not the others: claiming residency is uncontrollable (A) or that everything sits in one global centre (B) misstates the platform; and fixing residency post-go-live by export and re-import (C) is precisely the expensive mistake this configuration prevents.
Source: SAP Learning — Implementing SAP Customer Data Cloud → Further reading: PowerKram — Cybersecurity specialist path →A retailer is worried about account takeover on customer logins. Which CDC capabilities address this?
- Only basic username and password authentication is available
- Risk-Based Authentication, multi-factor authentication, and bot detection
- Account security is entirely the end customer’s responsibility
- Security features are not part of Customer Data Cloud
Show answer & explanation
Correct: B — Risk-Based Authentication, MFA, and bot detection. Risk-Based Authentication is named directly in SAP’s objectives for this exam, and the point is to raise friction only when the risk signal justifies it rather than for every login.
Why not the others: password-only (A) and no security features (D) are plainly false for a CIAM platform; and pushing responsibility to the customer (C) abandons the protections the platform exists to provide.
Source: SAP — Cloud identity and access management →A team wants CDC identity, consent, and profile data to drive personalized campaigns in SAP’s marketing solution. What should the consultant know about that integration?
- Only email addresses can be shared between the two
- The integration requires a third-party middleware platform
- CDC shares identity, consent, and profile data with SAP Engagement Cloud — the omnichannel marketing solution previously presented as Emarsys
- No integration between identity and marketing is available
Show answer & explanation
Correct: C — CDC feeds identity, consent, and profile data to SAP Engagement Cloud. Consent travelling with the profile is the important part: marketing can only act on what the customer actually agreed to. Note SAP’s Emarsys product page now redirects to Engagement Cloud, so recognise both names.
Why not the others: email-only sharing (A) would strip the consent and profile context that makes personalization lawful and useful; middleware (B) is unnecessary within SAP’s own portfolio; and no integration at all (D) is false.
Source: SAP — Engagement Cloud → Further reading: PowerKram — CX positioning →Clean core is a published topic area for this exam. What does it mean for a CDC implementation?
- Deleting inactive customer accounts at the end of each year
- Avoiding custom fields entirely so the schema stays standard
- Modifying the platform’s standard behaviour so it fits the customer exactly
- Extending through released, upgrade-stable mechanisms and standard integration, so the implementation survives platform updates
Show answer & explanation
Correct: D — Extend through released, upgrade-stable mechanisms with standard integration. Clean core spans process, integration, extensibility, data, and operations, and the goal is an implementation that takes the next platform update without a rescue project.
Why not the others: deleting inactive accounts (A) is data housekeeping; avoiding custom fields (B) confuses discipline with paralysis, since the data object exists to be used; and modifying standard behaviour (C) is the anti-pattern clean core exists to prevent.
Source: SAP Learning — Managing Clean Core →The privacy team needs GDPR-compliant consent with granular opt-in and opt-out plus an audit trail, and the company also operates under CCPA and LGPD. What does CDC provide?
- Configurable consent statements with granular controls and audit trails, adaptable across GDPR, CCPA, LGPD, and other regimes
- A single consent checkbox covering all data usage
- GDPR support only, with other regimes requiring separate instances
- Consent captured through email responses and reconciled manually
Show answer & explanation
Correct: A — Configurable consent with granular controls, audit trails, and multi-regime adaptability. Consent statements live in the preferences object and are configured per regime, so one implementation serves several jurisdictions rather than one per country.
Why not the others: a single blanket checkbox (B) fails the granularity regulators expect; GDPR-only with an instance per regime (C) multiplies cost for no reason; and email-based manual consent (D) has no audit trail worth the name.
Source: SAP Learning — Implementing SAP Customer Data Cloud → Further reading: PowerKram — CX Solution Architect →Keep going: Learning & Career resources
Customer identity sits between the CX portfolio and the privacy discipline underneath it — and it opens onto identity and CX consulting roles. Two PowerKram hubs back this exam.
Deep dive: the technical scope, schema objects, Site Groups, and study path
Read the profile SAP assigned this exam
SAP describes this certification as verifying the core skills required for the development consultant profile, with in-depth technical skills, and recommends it as an entry-level qualification. Those two statements together are the whole story: entry-level in seniority, technical in content. The published objectives name the Web SDK and REST API, the schema editor and accounts.setSchema, the Identity and Data Store, Site Groups, screen-sets, account linking, workflows, and Risk-Based Authentication. Preparation built on capability summaries will not survive contact with that. SAP Learning — Implementing SAP Customer Data Cloud →
Learn the four schema objects cold
The data schema is a full topic area and the questions turn on knowing which object does what. profile holds SAP’s out-of-the-box fields — you can restrict, encrypt, or require them, but you cannot add to or remove from them. data is where your custom fields go, with your choice of names, types, formatting, and encryption. subscriptions holds communication-preference opt-ins. preferences holds consent statements. Fields are created through the schema editor, accounts.setSchema, or the UI Builder. Confusing profile with data is the classic error, and it is the difference between a design that works and one that cannot be built. SAP Learning — Implementing SAP Customer Data Cloud →
Site Groups are stranger than they look
The counterintuitive part: the parent site in a Site Group is not a live site at all. It is an API key that holds the group’s global settings and the shared database, and child sites inherit permissions and policies from it while overriding selected settings. All sites in a group share one data centre and one database, and any API key belongs to only one group. Get that model straight and single sign-on across your sites follows naturally; miss it and the SSO questions look arbitrary. SAP — Cloud identity and access management →
Clean core reached the implementation exams
Managing Clean Core is a published topic area here, which is worth noticing: SAP is attaching the same extend-beside-rather-than-modify discipline to implementation credentials that it applies to development ones. For a CDC consultant that means using released mechanisms and standard integration, keeping the data model sound, and not solving today’s requirement in a way that breaks at the next platform update. When a question offers a workable customization and a released alternative, the released one is the answer. SAP Learning — Managing Clean Core →
Realistic study path and the Gigya heritage
80 questions in 180 minutes at a 66% cut score gives you over two minutes per question — comfortable if you have configured a tenant, tight if you have only read about one. Work SAP’s Implementing SAP Customer Data Cloud journey, then get hands on: create a site in the Console, choose its data centre, extend the data object with a custom field, build a screen-set, and call an Accounts API. One practical note — CDC was formerly Gigya, and the name persists in artefacts like gigya.js and the SDK namespaces, so do not be thrown when it appears in a question or in code. SAP Customer Data Platform on PowerKram →
Frequently asked questions
What are the exam topic areas?
SAP publishes four: Managing Clean Core; Console – Administration and Configuration; Data Schema; and Customer Identity and Site Groups. SAP notes the list is a guide rather than a guarantee and reserves the right to change content and weighting at any time.
How many questions is the exam, and what is the cut score?
80 questions in 180 minutes with a 66% cut score, in English. The exam uses multiple-choice items with single and multiple correct answers. SAP versions this exam by release — C_C4H62_2408 — so confirm the current code before booking.
Is this a configuration exam or a technical one?
Technical. SAP states the certification verifies the core skills required for the development consultant profile and in-depth technical skills. Its objectives name the Web SDK and REST API, the schema editor and accounts.setSchema calls, the Identity and Data Store, and Site Groups — alongside the identity and consent features.
What is the difference between the profile and data objects in the schema?
The profile object holds SAP’s out-of-the-box fields: you can apply access restrictions, mark fields required, and encrypt them, but you cannot add or remove fields. The data object is for your custom fields, where you set names, types, formatting, encryption, and client-side access. Custom loyalty or preference data belongs in data, not profile.
Is SAP Customer Data Cloud the same as Gigya?
Yes — CDC is the former Gigya platform, and the Gigya name still surfaces in technical artefacts such as the gigya.js Web SDK file and API namespaces. Expect to see it in documentation and code, and do not treat it as a different product.
Start your free 24-hour Customer Data Cloud practice trial
Full access to the question bank, both study modes, and score-by-topic feedback. No credit card required.
Start free trial →