First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Customer Service Implementation
In Pega Customer Service, which rule type is the primary mechanism used to route an incoming interaction to the right work queue or operator based on business conditions?
- Data transform
- Service level agreement
- Assignment shape with a routing activity Correct answer.
- Section rule
Explanation
Routing in a Pega Customer Service case type is normally driven from the assignment shape, where a routing activity or router evaluates conditions and places the assignment on a work queue or with a specific operator. The routing decision belongs to the assignment lifecycle, not to presentation or data mapping rules.
Question 2Customer Service Implementation
A customer service application must show agents a consolidated view of a customer's open cases, recent interactions, and account details on a single screen. Which Pega Customer Service construct is designed for this purpose?
- A decision table in the data layer
- A flow action with a single text property
- A background processing queue processor
- A composite portal with a configured 360 view Correct answer.
Explanation
The interaction portal in Pega Customer Service is built as a composite portal, and the customer 360 view surfaces related cases, interactions, and account context side by side for the agent. This lets an agent handle the customer without navigating away from the interaction.
Question 3Customer Service Implementation
Which Pega Customer Service feature lets you define the categories, issues, and sub-issues an agent selects when logging a new customer problem?
- The taxonomy configured for the interaction Correct answer.
- The access group's role configuration
- The data page source definition
- The case type hierarchy in App Studio
Explanation
The interaction taxonomy organizes the categories, issues, and sub-issues that classify why a customer is contacting the service center. Selecting a taxonomy path typically determines which case type or process is launched for the interaction.
Question 4Customer Service Implementation
An agent must be prevented from closing a complaint case until a supervisor has approved the resolution. Which Pega construct enforces this dependency?
- A dependent stage or an approval step in the case lifecycle Correct answer.
- A declarative expression on the work queue
- A validation rule on the resolution property
- A portal skin rule
Explanation
Enforcing that one piece of work must complete before another is modeled in the case lifecycle, typically as a dependent stage or an explicit approval step that gates progression. Validations check data on a form but do not enforce process sequencing across stages.
Question 5Customer Service Implementation
What is the purpose of a service-level agreement (SLA) on an assignment in a customer service case?
- To store the customer's contact preferences for the interaction
- To encrypt sensitive data shown on the assignment form
- To determine which operator has the skill to handle the work
- To define the goal, deadline, and escalation actions for completing the assignment Correct answer.
Explanation
An SLA attaches timing intervals to an assignment: a goal interval, a deadline interval, and the actions to run when each passes, such as escalation or reassignment. It is about timeliness of the work, not about data storage, skills, or security.
Question 6Customer Service Implementation
In a Pega Customer Service implementation, which artifact typically holds reusable customer data such as name, contact details, and account identifiers so that multiple case types can reference it?
- A separate access group per case type
- A data class for the customer entity referenced by case types Correct answer.
- A report definition per case type
- A section rule embedded in each flow action
Explanation
Customer information is modeled as a data class so that case types can reference the same customer entity through data pages rather than duplicating properties. This keeps customer context consistent across interactions and cases.
Question 7Customer Service Implementation
Which Pega Customer Service capability allows a business user to change a decision such as which retention offer applies to a customer, without deploying new application code?
- A hard-coded value in a section rule
- A decision table maintained through the business change process Correct answer.
- A schema change in the external database
- A Java step in an activity
Explanation
Decision rules such as decision tables and when rules are designed to be owned and updated by business users through the change management process. This separates policy from code so offers and eligibility can change without a full application release.
Question 8Customer Service Implementation
What does the phrase 'Next-Best-Action' mean in the context of a Pega Customer Service interaction?
- The default value populated in the first field of an intake form
- The escalation path defined in an SLA deadline interval
- The next case in the work queue ordered by creation date
- The single action the system recommends to the agent based on the customer's context and business rules Correct answer.
Explanation
Next-Best-Action evaluates customer context, eligibility, and business rules to recommend the most appropriate action, such as an offer or a retention step, during an interaction. It is a recommendation driven by decision logic rather than a queue ordering or a form default.
Question 9Customer Service Implementation
A developer wants an agent to see a warning when a customer's outstanding balance exceeds a threshold, before the agent submits the resolution form. Which mechanism is appropriate?
- A validate rule on the flow action that checks the balance property Correct answer.
- An SLA goal interval on the assignment
- A report definition filtered by balance
- A queue processor that runs after case resolution
Explanation
A validate rule attached to the flow action evaluates property values when the agent submits the form and blocks or warns on invalid data. Because it runs at submission, it can enforce the balance threshold before the resolution is recorded.
Question 10Customer Service Implementation
During an interaction, an agent needs to transfer the case to a specialized department queue. Which configuration most directly accomplishes this in Pega Customer Service?
- Change the case type's starting process to a new stage
- Create a data page that loads department names
- Add a new section to the case's review screen
- Configure the assignment routing to send the assignment to the target work queue Correct answer.
Explanation
Transferring work to a department is a routing concern, so the assignment's routing configuration should direct the assignment to the target work queue. The department's operators, who are members of that queue, then pick up the work.
Question 11Customer Service Implementation
A service manager wants agents to be able to view a customer's previous interactions and their outcomes while handling a new phone call. Which design choice best supports this requirement?
- Add a free-text notes field to the current case
- Disable the customer 360 view to reduce screen load
- Create a new case type for each previous interaction
- Configure the interaction portal to display related interaction history for the customer context Correct answer.
Explanation
The interaction portal can surface related interactions for the identified customer so the agent sees prior contact history and outcomes in context. This uses the existing customer relationship rather than duplicating data into notes.
Question 12Customer Service Implementation
A company wants different agent groups to see different sets of fields on the same case review screen. Which Pega mechanism supports this without duplicating the entire section?
- Separate database tables per agent group
- A distinct case type for each agent group
- A separate report definition per agent group
- Field-level access controlled by privileges in access roles Correct answer.
Explanation
Privileges assigned through access roles control whether a field is visible or editable for a given operator, allowing one section to present different fields to different groups. This is the standard way to tailor the same UI by role.
Question 13Customer Service Implementation
An implementation requires that a case automatically move from the 'Resolve' stage to the 'Closed' stage only after a customer satisfaction survey response is received. Which approach fits Pega case lifecycle design?
- Configure the SLA deadline to close the case automatically
- Model a wait step or dependent stage that listens for the survey response before advancing Correct answer.
- Create a report definition that counts survey responses
- Add a validation rule that requires a survey property to be non-empty
Explanation
Waiting for an external event such as a survey response is modeled in the case lifecycle with a wait step or a dependent stage that holds progression until the event arrives. Validations and reports cannot hold a case in a stage until an external signal occurs.
Question 14Customer Service Implementation
Which statement best describes how a data page configured with a read-only scope supports customer service performance?
- It bypasses security checks for faster access to customer records
- It writes each agent's changes directly to the external system on every keystroke
- It replaces the need for a case type hierarchy
- It caches reference data so repeated lookups by many interactions avoid repeated source calls Correct answer.
Explanation
A read-only data page caches its results for the configured scope, so repeated requests for the same reference data are served from memory rather than re-querying the source. This reduces latency during high-volume interactions without changing write behavior or security.
Question 15Customer Service Implementation
A developer needs a case to record which agent handled each interaction and when, for audit purposes. Which design is most appropriate?
- Capture the operator and timestamp in history or audit properties as the case progresses Correct answer.
- Store the values only in the agent's browser session
- Rely on the external database's default values
- Overwrite the case creation date with the latest handling time
Explanation
Audit information should be captured in case history or dedicated audit properties so each handling event is recorded with its operator and time. This preserves a durable trail that survives the session and supports later reporting.
Question 16Customer Service Implementation
An agent handling a billing dispute needs to see the customer's last three invoices pulled from an external billing system. Which Pega construct is best suited to retrieve this data on demand?
- A section rule containing static invoice text
- A queue processor scheduled nightly
- A data page backed by a connector to the billing system Correct answer.
- A decision table keyed on invoice number
Explanation
A data page with a connector source retrieves external records on demand and makes them available to the UI and case processing. This is the standard integration pattern for pulling live data from a system of record.
Question 17Customer Service Implementation
A customer service application must escalate a case to a supervisor when the SLA goal interval passes without resolution. Which configuration achieves this?
- Define a passed-goal action on the SLA that reassigns or notifies the supervisor Correct answer.
- Add a validation rule that checks the supervisor property
- Set the assignment to route to the supervisor at case creation
- Create a report that lists overdue cases
Explanation
The SLA's passed-goal action fires when the goal interval elapses, and it can reassign the assignment or send a notification to escalate the work. Routing at creation and reporting do not react to elapsed time.
Question 18Customer Service Implementation
Which configuration ensures that a retention offer is presented only to customers who meet eligibility criteria defined by the business?
- A data transform that sets the offer property to null
- A when rule or decision table that evaluates eligibility before the offer action is selected Correct answer.
- An access role that removes the offer privilege from all agents
- A section rule that hides the offer field by default
Explanation
Eligibility logic belongs in decision rules such as a when rule or decision table, which evaluate the customer's context and determine whether the offer action is applicable. Presentation or security tricks do not express business eligibility.
Question 19Customer Service Implementation
A developer must ensure that a newly created case appears in the correct agent's worklist immediately after creation. Which design element determines the initial owner of the assignment?
- The portal's default landing page
- The case type's icon setting
- The data class's key definition
- The routing configuration on the first assignment shape Correct answer.
Explanation
The owner of a new assignment is set by the routing configuration on the assignment shape that creates it. Changing icons, landing pages, or data keys does not affect assignment ownership.
Question 20Customer Service Implementation
An interaction requires that a customer's identity be verified before any account details are displayed. Which design approach best enforces this in Pega Customer Service?
- Store account details in a section that is always visible
- Rely on the agent's judgment to verify identity verbally without recording it
- Model identity verification as a prerequisite step whose completion gates access to account data Correct answer.
- Display account details first and verify identity only if the customer objects
Explanation
Identity verification should be an explicit step in the interaction whose completion is required before account data is exposed, so the control is enforced by the application rather than left to chance. This also produces an auditable record that verification occurred.
Question 21Customer Service Implementation
A team reports that agents occasionally resolve cases without capturing a required disposition code, and the disposition is needed for downstream reporting. Which change most directly prevents this outcome?
- Add the disposition property to a report definition
- Make the disposition property required in the flow action's validation so submission fails without it Correct answer.
- Add the disposition to the case's audit history after resolution
- Increase the SLA goal interval for the resolution assignment
Explanation
Marking the disposition as required in the flow action validation blocks submission until a value is supplied, which directly prevents resolution without a disposition. Reporting, timing changes, and post-resolution logging do not stop the omission.
Question 22Customer Service Implementation
A developer configures a data page with a requestor scope for customer profile data that changes frequently during the day. Which outcome should the developer expect?
- The data page reloads from the source on every single access
- The cached data is reused for the requestor's session and may become stale until the cache is refreshed Correct answer.
- The data page cannot be used in an interaction portal
- The data is shared across all requestors in the node
Explanation
Requestor-scoped data pages cache results for the life of the requestor session, so subsequent accesses reuse the cached copy and can serve stale values until the page is refreshed. Choosing scope is therefore a trade-off between performance and data freshness.
Question 23Customer Service Implementation
An implementation has a stage that can be re-entered after a customer reopens a previously resolved issue. What is the most important design consideration for the data captured in the earlier pass through the stage?
- Determine whether prior values should be retained, reset, or versioned so the reopened case reflects current circumstances Correct answer.
- Delete the case and create a new one to avoid data conflicts
- Disable the reopen capability to avoid the question
- Assume the earlier values are always correct and reuse them without review
Explanation
Re-entering a stage raises the question of data lifecycle: prior values may be outdated, so the design must decide explicitly whether to retain, reset, or version them. Leaving this implicit risks the reopened case carrying stale information into decisions.
Question 24Customer Service Implementation
A business user wants to change the eligibility criteria for a retention offer, and the change must take effect in production without a full application release. Which design best supports this requirement?
- Hard-code the criteria in the section that renders the offer
- Externalize the criteria into a business-managed decision rule governed by the change management process Correct answer.
- Ask developers to edit the case type's process each time criteria change
- Embed the criteria in a Java step inside the activity that builds the offer
Explanation
Placing eligibility criteria in a business-managed decision rule, with proper change management and testing, lets the business update policy without a full release. Embedding the logic in code or UI rules forces a developer change and redeployment.
Question 25Customer Service Implementation
A service application must support both phone and email interactions that share the same underlying complaint case type but differ in their intake steps. Which design approach best balances reuse and channel-specific behavior?
- Create two entirely separate case types with duplicated resolution logic
- Force email customers to use the phone intake process
- Use one complaint case type with channel-specific intake stages or processes that converge on shared resolution stages Correct answer.
- Implement channel differences only in the portal skin
Explanation
A single case type with channel-specific intake that converges on shared resolution stages reuses the common complaint logic while accommodating channel differences. Duplicating case types multiplies maintenance and risks divergence in resolution behavior.
Question 26Customer Service Implementation
In a Pega Customer Service application, which rule type is used to define the sequence of steps an agent follows while working a service case?
- Data transform
- Process flow Correct answer.
- Decision table
- Section
Explanation
Process flows define the ordered shapes and connectors a case moves through, so they express the step sequence an agent executes. Decision tables evaluate conditions to produce values, sections render UI, and data transforms map property values.
Question 27Customer Service Implementation
Which Pega Customer Service component is designed to give agents a single screen that combines customer context, interaction history, and service actions during a live contact?
- Admin Studio
- Interaction portal Correct answer.
- Dev Studio
- Case type explorer
Explanation
The interaction portal is the agent-facing desktop that surfaces customer context and actions for the current contact. Admin Studio and Dev Studio are configuration environments, and the case type explorer is a design-time navigation aid.
Question 28Customer Service Implementation
A developer needs a case to pause until a customer replies to an email before continuing to the next step. Which case lifecycle construct best represents this waiting period?
- A validation rule on the case
- A field value rule for the reply
- An access role for the customer
- A wait shape in the process flow Correct answer.
Explanation
A wait shape suspends processing until a defined condition is satisfied, such as receipt of a customer response. Validation rules check data, field value rules localize text, and access roles control permissions.
Question 29Customer Service Implementation
Which Pega mechanism lets a developer surface a list of related records, such as a customer's open orders, on a case without writing SQL against the source system?
- A when rule on the case type
- A privilege on the access group
- A paragraph rule in the harness
- A data page sourced by a connector Correct answer.
Explanation
A data page backed by a connector or integration retrieves and caches related records for display and reuse. When rules evaluate boolean conditions, paragraphs render text, and privileges grant permissions.
Question 30Customer Service Implementation
An agent must be prevented from closing a complaint case until an investigation summary is entered. Which configuration enforces this at the case level?
- A display-only section for the summary
- A case-wide lock on the assignment
- A read-only field on the summary property
- A required-field validation on the resolution step Correct answer.
Explanation
Validation on the resolution step blocks submission until the required property has a value. Read-only or display-only settings only affect editing, and a lock prevents concurrent edits rather than enforcing completeness.
Question 31Customer Service Implementation
Which Pega Customer Service feature lets a business user define and maintain the categories used to classify incoming customer issues without developer involvement?
- Section rule in Dev Studio
- Java step in an activity
- Taxonomy configuration in Admin Studio Correct answer.
- Access group definition
Explanation
The service taxonomy organizes issue and group categories and is maintained by business users through Admin Studio. Activities, sections, and access groups are developer-level technical artifacts.
Question 32Customer Service Implementation
A developer wants an agent to capture the reason a customer contacted the service center at the very start of an interaction. Which design element most directly supports this?
- A required field on the interaction's initial intent capture Correct answer.
- A scheduled job that runs nightly
- A report definition on closed cases
- A post-processing activity on case resolution
Explanation
Capturing intent at the start of the interaction records the contact reason while context is fresh and can drive routing. Post-processing, scheduled jobs, and reports act later and cannot capture the reason at intake.
Question 33Customer Service Implementation
Which statement describes the purpose of a case type in a Pega Customer Service application?
- It defines the lifecycle, data, and steps for one kind of business transaction. Correct answer.
- It maps external systems to internal property names.
- It stores the list of agents assigned to a work group.
- It controls which operators may log in to the application.
Explanation
A case type models a business transaction end to end, including its stages, steps, and data requirements. Agent rosters, integration mappings, and authentication are handled by other artifacts.
Question 34Customer Service Implementation
During a live call, an agent needs to launch a retention workflow that collects data from the customer and then returns to the main interaction. Which construct is most appropriate?
- A local action configured on the interaction Correct answer.
- A background job scheduled by the system
- A top-level case type with its own portal
- A separate application built for retention
Explanation
A local action runs a focused flow within the current interaction and returns control to it, preserving context. A separate case type, background job, or application would break the live interaction flow.
Question 35Customer Service Implementation
Which Pega feature should be used to make a case's stage progression conditional on data captured earlier in the same case?
- A stage transition with a when condition Correct answer.
- A static stage order with no conditions
- A UI control on the case header
- A report on stage duration
Explanation
Stage transitions can carry when conditions so that progression depends on case data. Static ordering ignores data, UI controls affect display, and reports only observe outcomes.
Question 36Customer Service Implementation
A developer must ensure that two agents working the same case cannot overwrite each other's changes to the same assignment. Which mechanism addresses this?
- A data page refresh strategy
- Field-level encryption
- Assignment-level locking Correct answer.
- A declarative network
Explanation
Assignment locking prevents a second agent from opening and modifying an assignment already in progress. Encryption protects confidentiality, declarative networks compute values, and data page refresh affects caching.
Question 37Customer Service Implementation
Which artifact is used to define the fields and layout an agent sees when working a specific assignment in a Pega Customer Service case?
- A data transform
- A decision tree
- A flow action with its section Correct answer.
- A service level agreement
Explanation
A flow action references the section that renders the assignment's fields and layout for the agent. Data transforms move data, decision trees evaluate logic, and SLAs govern timing.
Question 38Customer Service Implementation
A service team wants supervisors to reassign a stalled case from one agent to another while preserving the case history. Which action best supports this?
- Change the case type of the existing case
- Transfer the assignment to a different work queue or operator Correct answer.
- Delete and recreate the case under the new agent
- Close the case and open a new one for the new agent
Explanation
Transferring the assignment moves ownership while retaining the case and its audit trail. Recreating, retyping, or reopening a new case would break continuity and lose history.
Question 39Customer Service Implementation
Which configuration allows a Pega Customer Service application to show different self-service options to retail and corporate customers on the same web channel?
- Channel-specific configuration with audience conditions Correct answer.
- A developer-only Dev Studio branch
- An operator ID prefix convention
- A single hard-coded menu for all users
Explanation
Channel configuration combined with audience conditions lets the application present tailored options per customer segment. A hard-coded menu, a branch, or an ID convention cannot differentiate audiences at runtime.
Question 40Customer Service Implementation
An implementation needs a case to be created automatically when an external system posts an event to a REST endpoint. Which Pega capability supports this?
- A report definition scheduled hourly
- A section rule with a button
- A service REST integration that creates the case Correct answer.
- A UI gallery control
Explanation
A service REST rule receives inbound requests and can invoke case creation logic. Sections, reports, and UI controls do not accept external event posts.
Question 41Customer Service Implementation
Which Pega Customer Service concept groups agents so that work can be routed to a shared pool rather than to named individuals?
- Work queue Correct answer.
- Access group
- Application definition
- Operator record
Explanation
A work queue is a shared pool from which members of a group pull assignments. Access groups and operator records define permissions and identity, and the application definition scopes the ruleset stack.
Question 42Customer Service Implementation
A developer wants to record a timestamp automatically whenever a case enters a particular stage, without agent input. Which approach is most appropriate?
- A UI label showing the current date
- A declarative or data transform step triggered on stage entry Correct answer.
- A manual field the agent must fill in
- A report that calculates the timestamp later
Explanation
Automation on stage entry, such as a data transform or declarative expression, sets the timestamp reliably without relying on the agent. Manual entry, later reporting, and display labels do not capture the event automatically.
Question 43Customer Service Implementation
Which practice best protects sensitive customer data displayed in the interaction portal from being seen by agents who lack the need to know?
- Masking fields based on the agent's access role Correct answer.
- Storing the data in a report definition
- Displaying all fields to every agent for transparency
- Caching the data in a requestor-scoped data page
Explanation
Field-level masking tied to access roles limits sensitive values to authorized agents. Showing everything, reporting, or caching does not restrict visibility and may widen exposure.
Question 44Customer Service Implementation
A case type must support a sub-process that is reused by three different parent case types. Which design is most maintainable?
- Copy the sub-process into each parent case type
- Hard-code the sub-process steps in each assignment
- Build three separate applications for each parent
- Define the sub-process once as a reusable flow or case type and invoke it Correct answer.
Explanation
A single reusable definition invoked by each parent avoids divergence and duplicated maintenance. Copying, splitting applications, or hard-coding steps multiplies the maintenance burden.
Question 45Customer Service Implementation
An agent reports that a case's status does not change after resolution. Which area should a developer inspect first to diagnose the problem?
- The report definition used by the supervisor
- The stage transition and status configuration on the resolution step Correct answer.
- The customer's contact record
- The operator's locale setting
Explanation
Status changes are driven by stage transitions and resolution configuration, so that is the likely cause. Contact data, reports, and locale do not govern case status.
Question 46Customer Service Implementation
A business requirement states that a case must be routed to a specialist queue when the customer's tenure is under 90 days, otherwise to the general queue. Which configuration implements this cleanly?
- A report that lists short-tenure customers
- A static assignment to the general queue
- A routing decision using a when condition on tenure Correct answer.
- A manual transfer performed by the agent
Explanation
A routing decision with a condition on tenure evaluates the data and sends the case to the correct queue automatically. Static assignment, manual transfer, and reporting do not implement the conditional rule.
Question 47Customer Service Implementation
Which statement best describes how a Pega Customer Service application supports a consistent experience across voice and chat channels?
- Independent databases for each channel
- Shared case types and data model reused by channel-specific portals Correct answer.
- A single portal that ignores channel context
- Separate case types duplicated per channel
Explanation
Reusing shared case types and data while varying the portal per channel keeps process logic consistent. Duplicated case types, channel-blind portals, and split databases create divergence.
Question 48Customer Service Implementation
A developer must ensure that a customer's recently updated address is reflected in a new interaction without restarting the application. Which consideration matters most?
- The color scheme of the interaction portal
- The font used in the case header
- The number of agents in the work group
- The data page scope and refresh strategy for the customer data Correct answer.
Explanation
Data page scope and refresh strategy determine whether updated data is re-read or served from cache. Visual styling, group size, and fonts have no bearing on data freshness.
Question 49Customer Service Implementation
Which Pega Customer Service artifact is best suited to present a guided, multi-step questionnaire to an agent within a single assignment?
- A service level agreement
- A screen flow Correct answer.
- A data page
- An access role
Explanation
A screen flow presents a sequence of screens within one assignment, ideal for guided questionnaires. Data pages supply data, access roles govern permissions, and SLAs manage deadlines.
Question 50Customer Service Implementation
A supervisor needs a dashboard showing how many complaint cases breached their service level agreement this week. Which combination best delivers this?
- A section rule with a single label
- A when rule that blocks case submission
- Report definition on SLA breach data surfaced in a dashboard Correct answer.
- A data transform that copies case data
Explanation
A report definition querying SLA breach data, displayed in a dashboard, gives supervisors the needed view. When rules, data transforms, and static sections do not aggregate and present metrics.