PEGACPCSD23V1 Certified Pega Customer Service Developer Practice Questions
Prepare for PEGACPCSD23V1 with more than an answer.
- Time limit
- 90 minutes
- Questions on the exam
- 50
- Passing score
- 65%
- Level
- Intermediate
Domains covered on the exam 8
- Case Management10%
- User Experience20%
- Data Integration15%
- Channels15%
- Application Development15%
- Reporting5%
- Interaction Management15%
- Business Outcomes5%
- 1
True or False: In Pega Customer Service '23, organizations migrating from UI-Kit to Constellation must completely rewrite their business logic (such as flows, decision tables, and data pages) because Constellation uses a fundamentally different back-end processing engine.
Show answer details
Correct answer: B
False. Constellation is a presentation layer architecture. The underlying business logic (Center-out architecture, flows, decision tables, data pages) remains the same. Only the UI layer (sections, harnesses) needs to be mapped to Constellation Views.
- 2
During an active customer interaction in the Interaction Portal, a CSR launches an 'Update Address' service case. How does the Pega Interaction Portal manage the presentation of this new service case to ensure the CSR maintains context?
Show answer details
Correct answer: B
The Interaction Portal is designed to maintain context. When a service case is launched, it opens within the context of the current interaction workspace. The CSR can work on the case while still viewing the customer composite, preventing the loss of context.
- 3
A developer is configuring a new 'Vehicle History' composite tab for an auto insurance application. The data is retrieved from a legacy external system via a REST integration. To ensure optimal performance and user experience in the CSR desktop, which TWO design practices should be implemented? (Select TWO)
Show answer details
Correct answer: A, D
Defer loading (asynchronous loading) of external data ensures that the main UI renders quickly for the CSR, while heavy external queries load in the background.
Mapping external data to the Common Data Model ensures consistency, reusability, and easier UI configuration within Constellation Views.
flowchart LR Ext[Legacy System] -->|REST| DP[Data Page] DP -->|Maps to| CDM[Common Data Model Entity] CDM -->|Renders in| View[Vehicle History Tab View] - 4
When applying Constellation UX best practices to a CSR desktop, what is the recommended approach for handling complex data entry forms that contain more than 20 fields?
Show answer details
Correct answer: B
Constellation emphasizes intent-driven, guided UX. Long forms should be broken down into digestible, logical steps (wizards/screen flows) to reduce cognitive load and guide the user through the microjourney efficiently.
- 5
A financial institution is designing a new customer service application. The business requires that when a customer calls to report a lost credit card, the agent's desktop immediately displays the customer's profile, recent transactions, and prompts a specific flow to cancel and reissue the card. According to Pega Customer Service best practices, how should the interaction and the card cancellation process be modeled?
Show answer details
Correct answer: B
In Pega Customer Service, best practices dictate a clear separation between the Interaction case (which manages the communication channel, context, and duration of the customer contact) and Service cases (which represent the specific business intents or transactions, like canceling a card).
- 6
When defining the behavior of a newly created 'Address Change' service request in App Studio, the development team wants to ensure that the request can only be launched if the customer has already passed the identity verification process during the current interaction. Which configuration setting must be applied to enforce this rule?
Show answer details
Correct answer: B
In Pega Customer Service, you can control service request behavior directly via configuration settings in App Studio. Checking the 'Requires Verification' (or similar verification behavioral setting) ensures the CSR cannot execute the service case until the customer identity is successfully authenticated in the interaction.
