PC-CIC-Core
PureConnect: CIC Core Certification
PC-CIC-Core exam guide: verify the target before you study
The supplied official sources do not identify PC-CIC-Core as an exam, certification, or published exam code. They document Genesys Cloud for Azure integration with Microsoft Entra ID, including single sign-on and automatic provisioning, while the testing pages provide general scheduling guidance rather than program-specific PC-CIC-Core rules. This guide therefore helps you make the most important preparation decision first: confirm the exam owner, current blueprint, and booking route before investing in study time. It also provides a practical integration-focused study path if that is the subject your sponsor or training plan associates with PC-CIC-Core.
What does the official evidence confirm about PC-CIC-Core?
The available official material does not confirm the purpose, audience, measured skills, prerequisites, scoring, question format, duration, language, price, delivery method, or current status of PC-CIC-Core. Microsoft’s documentation names Genesys Cloud for Azure and explains its integration with Microsoft Entra ID, but it does not identify an exam or certification named “Genesys PC-CIC-Core.”
Before studying, treat the exam name as an unverified catalogue label rather than as a complete specification. This is not a minor distinction: a technically accurate study plan can still be misdirected if the code belongs to a different provider, a private assessment, an internal course, or an outdated programme.
The two Microsoft pages supplied for research cover different technical jobs. One explains single sign-on between Genesys Cloud for Azure and Microsoft Entra ID. The other explains automatic user provisioning and de-provisioning. Neither page supplies a PC-CIC-Core exam outline.
Use the official programme or sponsoring organisation’s candidate page to verify the exact title and code. Pearson’s test-taker page instructs candidates to find their exam through the relevant programme homepage, where they can see availability, scheduling rules, preparation material, and programme-specific FAQs: https://www.pearsonvue.com/us/en/test-takers.html
Who should consider this preparation path?
This study path suits a candidate who has been directed toward PC-CIC-Core and whose work involves Genesys Cloud for Azure, Microsoft Entra ID, single sign-on, or automated identity lifecycle management. It is a practical orientation, not an officially stated candidate profile, because the supplied sources do not publish the exam’s intended audience.
The Microsoft documentation assumes access to a Microsoft Entra user account with an active subscription, an appropriate application role, a PureCloud organisation, and a user who can create an OAuth client for provisioning work. Those are prerequisites for the documented integration scenario, not confirmed prerequisites for PC-CIC-Core.
A useful candidate fit usually depends on the work you expect to perform after training. If your role includes application integration, identity administration, provisioning scope, attribute mapping, or access troubleshooting, the supplied technical material is relevant study context. If your role is limited to contact-centre operations or end-user activity, do not assume that these administrator-oriented topics represent the exam.
Ask the sponsor or exam owner three questions before committing to a booking: Is PC-CIC-Core the exact current code? Which official blueprint defines its domains? Which account or portal controls registration? Record the answers and keep the links, because the supplied sources do not answer them.
What skills can you study from the available documentation?
The available documentation supports preparation in two technical areas: configuring Microsoft Entra single sign-on for Genesys Cloud for Azure and configuring automatic user provisioning and de-provisioning. It does not provide measured-skill percentages or an exam blueprint, so these topics must not be presented as confirmed PC-CIC-Core domains.
For single sign-on, study the relationship between the Microsoft Entra application, assigned users or groups, and the corresponding user in Genesys Cloud for Azure. The Microsoft procedure describes adding Genesys Cloud for Azure from the application gallery, configuring the Microsoft Entra side, creating a test user, assigning that user, configuring the application side, and testing the result.
For provisioning, study the complete lifecycle rather than only the initial connection. The documentation covers planning, creating an OAuth client in the PureCloud organisation, generating a token, adding the application from the Microsoft Entra gallery, defining scope, configuring automatic provisioning, and monitoring the deployment.
The provisioning page identifies supported capabilities that are useful for a lab checklist: creating users, removing users when access is no longer required, synchronising user attributes, and provisioning groups and group memberships. It also notes that group membership provisioning requires matching group names in PureCloud and Microsoft Entra ID.
These are preparation themes drawn from the supplied technical sources. They are not blueprint claims. Do not assign them percentages, rank them as official domains, or infer that every topic will appear in the assessment until the exam owner publishes that information.
How should you verify the exam before booking?
Verify the code, owner, delivery partner, and current candidate rules on the programme-specific page before choosing a study schedule. The supplied Pearson page provides a general route to search for an exam, locate a test centre or online option where available, review rules, and schedule or change an appointment; it does not confirm those options for PC-CIC-Core.
Start with the exact string PC-CIC-Core and any alternate spelling supplied by your employer or training provider. Check whether the result shows a matching title, objectives, registration instructions, and candidate agreement. A similar-looking Genesys or contact-centre assessment is not sufficient evidence that it is the same exam.
Next, identify the authoritative blueprint. Look for a document that names the exam, lists domains or objectives, and states its revision or effective date. If no blueprint exists, ask the sponsor for written confirmation of what is assessed rather than filling the gap with third-party topic lists.
Finally, check the booking workflow. Pearson’s general page says candidates can use the relevant programme homepage to see available exams, create or access an account, search for a test centre or online option, find programme-specific rules, and schedule, reschedule, or cancel appointments. Those are general portal capabilities, not confirmation that PC-CIC-Core is delivered through Pearson.
If the programme directs you to Certiport, review the current programme instructions rather than relying on the supplied legacy console page. That page discusses iQsystem and Certiport Console administration for authorised testing centres, but it does not identify PC-CIC-Core or establish candidate-facing rules for this exam.
What should your first technical study session produce?
Your first session should produce a one-page integration map showing the systems, identities, trust relationships, and test actions involved. This is more useful than beginning with memorisation because the supplied Microsoft material is procedural: it expects you to understand how configuration decisions connect across Genesys Cloud for Azure and Microsoft Entra ID.
Draw Microsoft Entra ID, the Genesys Cloud for Azure application, the relevant users and groups, and the linked user representation in Genesys Cloud for Azure. For SSO, mark where access is assigned and where the application-side account must correspond to the Microsoft Entra user.
For provisioning, add the OAuth client, token, provisioning scope, attribute mappings, groups, and monitoring path. Mark the direction of each action: Microsoft Entra ID provisions or de-provisions identities and synchronises selected data to Genesys Cloud for Azure.
Then write a short test sequence in your own words. For SSO, it should include assigning a test user, configuring the application side, and verifying sign-in. For provisioning, it should include a small initial scope, a controlled change to a user or group, and review of the resulting logs or status.
Keep a separate column labelled “officially confirmed for PC-CIC-Core.” Leave it blank for topics that are only supported by the adjacent Microsoft documentation. This simple separation prevents recommended lab work from becoming an invented exam outline.
How do you study single sign-on without confusing it with provisioning?
Study single sign-on as an access and trust configuration problem, while studying provisioning as an identity lifecycle problem. The two capabilities can support the same application, but they answer different operational questions: SSO controls how an assigned user signs in, whereas provisioning controls how accounts, attributes, groups, and access changes are represented.
The Microsoft SSO tutorial describes integrating Genesys Cloud for Azure with Microsoft Entra ID so administrators can control access, enable automatic sign-in with Microsoft Entra accounts, and manage accounts centrally. It also states that the scenario requires a Genesys Cloud for Azure SSO-enabled subscription and an appropriate Microsoft Entra role.
Build your notes around dependencies. A successful SSO configuration requires an application entry, an assigned test user, an application-side user counterpart, and matching settings. The tutorial explicitly describes creating and assigning a Microsoft Entra test user, creating the corresponding Genesys Cloud for Azure test user, configuring SSO on both sides, and testing the result.
Do not treat a successful sign-in as proof that provisioning works. Create a separate validation checklist for lifecycle changes. Conversely, do not treat a newly provisioned account as proof that SSO is correctly configured; provisioning and authentication have distinct configuration and testing steps.
The official SSO instructions are available at https://learn.microsoft.com/en-us/entra/identity/saas-apps/purecloud-by-genesys-tutorial. Use the current page for exact portal labels and settings, since interface instructions can change even when the underlying concepts remain familiar.
How do you study automatic provisioning in the right order?
Follow the provisioning workflow in dependency order: plan the deployment, prepare Genesys Cloud for Azure, add the gallery application, define scope, configure provisioning, and monitor the result. This order mirrors the Microsoft documentation and reduces the common mistake of enabling broad synchronisation before the identity and data model are understood.
Begin by deciding which users and groups belong in the initial test. The documentation recommends starting small and testing with a small set before rolling out to everyone. Use that recommendation as a lab control, not as a claim about an exam requirement.
Next, review the OAuth dependency. The Genesys Cloud for Azure side requires an OAuth client configured in the PureCloud organisation and a token generated from that client. Study what the client enables in the provisioning connection and keep credentials out of shared notes or screenshots.
Then examine scope and mapping. Microsoft Entra provisioning can scope users based on assignment to the application or on user and group attributes through a scoping filter. Attribute mapping determines which identity data is transferred, so write down the intended source and target for each field you test.
For group membership, remember the specific condition documented by Microsoft: groups in PureCloud must have an identical name to the corresponding group in Microsoft Entra ID when automatic group membership provisioning is required. Validate this deliberately in a lab rather than assuming similarly named groups will match.
Finish with monitoring. The official page directs administrators to provisioning logs, the progress bar, and the application’s health state. It also notes that an unhealthy configuration can place the application into quarantine. Your notes should explain what evidence each monitoring view provides and what action follows an error.
What lab exercises provide the best preparation value?
Use controlled configuration exercises that force you to explain both the action and the reason for it. A good lab does not attempt to reproduce unknown exam questions; it develops the ability to trace identity, access, scope, mapping, and monitoring decisions through the documented integration.
Exercise one: create a small SSO test environment. Add Genesys Cloud for Azure from the Microsoft Entra application gallery, assign a test user, create the corresponding Genesys Cloud for Azure user, configure the application-side settings, and test sign-in. Record every dependency and the symptom produced when one is missing.
Exercise two: test provisioning scope. Start with a narrowly assigned user or group, configure the connection, and observe the initial provisioning result. Change the assignment or filter deliberately, then determine whether the expected account or group membership is created, updated, or removed.
Exercise three: test attribute mapping. Choose a small set of user attributes, document the source values, and compare them with the values represented in Genesys Cloud for Azure. The goal is to understand data flow and diagnose mismatches, not to memorise field names without context.
Exercise four: test monitoring and recovery. Introduce a safe configuration error in a disposable environment, inspect the provisioning logs and progress information, identify the reported problem, correct the cause, and verify the subsequent state. Do not make disruptive changes in a production tenant merely to create a study example.
After each exercise, write a troubleshooting note with four parts: expected result, observed result, likely cause, and verification step. This turns hands-on work into reusable revision material.
What mistakes can derail preparation?
The biggest mistake is studying an assumed blueprint. Because the supplied sources do not publish PC-CIC-Core objectives, percentages, question counts, duration, or scoring, any third-party list presenting those details as certain should be treated cautiously until the exam owner confirms it.
Another mistake is blending official requirements with personal study preferences. Microsoft’s documented prerequisites and configuration steps apply to the integration scenario described on its pages. They do not establish PC-CIC-Core eligibility rules. Label your notes as “source requirement,” “lab decision,” or “exam-owner confirmation.”
Avoid learning only the happy path. Candidates who can add an application but cannot explain assignment, scope, matching users, OAuth preparation, attribute mapping, or monitoring will have shallow operational understanding. For each configuration step, ask what it controls, what dependency it has, and how its result would be verified.
Do not expand a narrow source into unsupported product claims. The Microsoft pages document Genesys Cloud for Azure integration with Microsoft Entra ID; they do not establish the full feature set of Genesys Cloud, the complete responsibilities of a contact-centre administrator, or the contents of a PC-CIC-Core assessment.
Finally, do not use exam dumps or leaked questions. They are not a substitute for an official blueprint or technical competence, and memorisation cannot guarantee a passing result. Use official documentation, a permitted training environment, and your own configuration records instead.
What is known about delivery and test-centre logistics?
The available delivery evidence is general rather than exam-specific. Pearson’s test-taker portal says candidates can search for a local test centre or see whether online testing is available, review programme-specific rules, and manage appointments through the relevant exam programme page. It does not confirm that PC-CIC-Core uses Pearson or either delivery option.
The supplied Certiport page describes iQsystem and Certiport Console software used by authorised testing centres. It says Certiport Console can operate iQsystem under a limited Windows user account by applying stored administrative credentials when the software is accessed. That is testing-centre infrastructure information, not proof of PC-CIC-Core delivery.
Do not infer a delivery method from the presence of a Pearson or Certiport link in a catalogue record. Confirm the provider on the current official programme page, then read that provider’s candidate instructions for identification, appointment changes, accommodations, equipment, and permitted materials.
If Pearson is the confirmed provider, begin from the programme homepage rather than relying on the general test-taker landing page. Pearson specifically directs candidates to the programme homepage for available exams, programme rules, customer service, FAQs, and preparation resources.
If Certiport is confirmed, use the current candidate-facing programme instructions. The supplied console material includes historical operating-system and administrator-access details for centre administrators, but it does not provide a current PC-CIC-Core appointment procedure. Source: https://www.certiport.com/Portal/desktopdefault.aspx?page=common%2Fpagelibrary%2Fcertiportconsole.html
Which study roadmap should you follow?
Use a verification-first roadmap: establish the exam target, build the identity and integration model, practise SSO, practise provisioning, troubleshoot controlled failures, and then schedule only when the official scope and booking route are clear. This sequence prevents administrative uncertainty from being mistaken for a technical knowledge gap.
Stage one is exam confirmation. Obtain the current exam title, code, blueprint, prerequisites, delivery partner, and candidate rules from the owner or sponsor. If any item is missing, mark it unresolved and avoid making a booking decision based only on the catalogue name.
Stage two is concept mapping. Study the Microsoft SSO and provisioning pages and create a glossary for application assignment, linked user, OAuth client, token, scope, scoping filter, attribute mapping, group membership, provisioning log, and quarantine. Write a one-sentence explanation for each term in your own words.
Stage three is configuration practice. Complete the SSO lab first because it establishes the relationship between Microsoft Entra users and Genesys Cloud for Azure users. Follow with a narrowly scoped provisioning lab, then add attribute and group tests after the basic connection is understood.
Stage four is troubleshooting. Review failed assignments, unmatched users, incorrect group names, incomplete mappings, and unhealthy provisioning states. For every issue, identify the evidence you would inspect before changing configuration. This develops disciplined diagnosis instead of trial-and-error clicking.
Stage five is readiness review. Compare your notes with the verified blueprint once available. Mark each objective as explain, configure, test, or troubleshoot. Schedule only after you know the appointment provider and have checked the current programme rules.
A practical weekly review pattern
At the end of each study cycle, close your documentation and reproduce the workflow from a blank checklist. Explain why each step exists, predict the result, and then verify it in the lab. Reserve the final review for gaps identified against the official blueprint, not for unsupported lists of supposed exam questions.
How should you decide whether to schedule now?
Schedule only when the exam identity and official booking route are confirmed, not simply when the technical reading feels familiar. For PC-CIC-Core, the current supplied evidence leaves those points unresolved, so the immediate next action is verification rather than appointment selection.
You are closer to a sound scheduling decision when you can identify the authoritative exam page, confirm that the code matches, locate the current objectives, understand the provider’s rules, and explain how your preparation maps to those objectives. If the owner cannot provide those details, ask whether the assessment has been renamed, replaced, or restricted to a private programme.
Technical readiness should be demonstrated through explanation and controlled practice. You should be able to distinguish SSO from provisioning, describe how access is assigned, explain how provisioning scope is controlled, identify the OAuth-client dependency, reason about group-name matching, and use logs or status information to investigate a failed deployment.
Before booking, check the official page again for current availability, delivery choices, accommodations, rescheduling conditions, and preparation resources. Pearson’s general portal is a useful starting point for navigation, but its information is not a substitute for programme-specific confirmation.
Keep a final evidence file containing the verified blueprint, official links, configuration notes, and unresolved questions. This gives you a reliable basis for choosing study material and prevents outdated catalogue information from driving the decision.
What should you do next?
Your next action is to validate PC-CIC-Core with the organisation that supplied the code, then use the Microsoft integration documentation as structured technical preparation only if that subject matches the confirmed assessment. This approach is slower than guessing a blueprint but protects your study time and keeps official facts separate from practical recommendations.
Send the sponsor or programme owner a concise request for the current exam page, blueprint, prerequisites, delivery provider, and registration instructions. Ask them to confirm whether the exam is specifically related to Genesys Cloud for Azure and Microsoft Entra ID.
While waiting, build the integration map and complete a small SSO or provisioning lab in a permitted environment. Use the official Microsoft pages as your technical reference: https://learn.microsoft.com/en-us/entra/identity/saas-apps/purecloud-by-genesys-tutorial and https://learn.microsoft.com/en-us/entra/identity/saas-apps/purecloud-by-genesys-provisioning-tutorial.
Once the exam owner confirms the scope, replace this provisional roadmap with an objective-by-objective checklist. Retain only the topics that map to the confirmed blueprint, and return to the official testing provider for current scheduling and candidate rules.
Until that confirmation arrives, the responsible conclusion is not that PC-CIC-Core is easy, difficult, active, or retired. The responsible conclusion is that the available official evidence is insufficient to make those claims, while still providing a useful integration lab path for candidates whose confirmed programme covers this technology.
Conclusion
PC-CIC-Core cannot be described responsibly as a verified public exam from the supplied sources. Those sources do support a focused study path for Genesys Cloud for Azure integration with Microsoft Entra ID: understand SSO, plan provisioning, configure OAuth access, control scope, map identities and groups, and monitor results. Confirm the exam owner and blueprint before treating any of those topics as assessed content or booking an appointment. That verification step is the most practical preparation decision available from the current evidence.