Free PEGACPSA25V1 practice test: 30 questions with answers

A case type is divided into stages, each stage holds one or more processes, and processes are built from steps such as assignments. The other options reverse or skip levels in this hierarchy, so they do not match how Pega organizes case flows.

Pega SLAs use a goal and a deadline, and urgency increases as time passes toward the deadline, which brings the riskiest items forward. Sorting by name, assigning to one operator, and a validation rule do not change priority over time based on the deadline.

Work groups and work queues let any qualified operator take the next item without naming individuals. Routing to the manager, to one named operator, or to a data page does not let the whole team share the workload.

An authority matrix ties approval authority to amount thresholds, so the right approver is selected from the amount. A fixed chain ignores the amount, a validation rule rejects rather than routes, and copying a fixed operator ID does not respond to the amount at all.

A data page caches data from a source, and its refresh strategy controls when the data is reloaded, which avoids calling the service on every screen. Calculated values derive values from inputs, when rules control visibility, and validate rules check entered data, so none of them manage a cached external source.

A calculated value recalculates automatically when its source properties change, which matches the requirement. A button-triggered activity needs a user action, a report fetches stored results rather than deriving a live value, and a validate rule checks values on submit rather than updating them.

A validate rule checks property values and displays messages when the user submits or saves the form, which fits this requirement. A batch decision table gives no immediate feedback on the form, a data page only caches data, and a report-triggered activity runs too late to stop bad entries.

A data transform sets property values at a defined point such as case creation, which suits a default value that can be overridden by intake. A validate rule only checks entries, a calculated value derives a value from other fields, and a data page supplies a list of options rather than setting the value.

Pega searches rules from the most specific class upward, so the child class rule is found first and used. Parent rules do not override child rules, both rules do not run in sequence, and a missing-rule error occurs only when no matching rule exists at all.

Branches let developers work on separate changes within the application and merge them when ready, which keeps in-progress work isolated. Shared operator IDs do not separate work, copying database tables is not how rule changes are managed, and renaming rules does not isolate changes.

Tracer records the rules executed during a case run, which shows the sequence needed to find where the flow diverged. The Agile Workbench manages backlog items, Insights charts aggregate data, and refreshing a data page only reloads cached data.

Meaningful labels, keyboard access and visible focus with good contrast are standard accessibility practices for users of assistive technology. Relying only on colour and hiding error messages from screen readers both exclude users, so they are not good practice.

Authentication confirms the identity of the user, while authorization determines which records and functions that identity may use. Swapping these roles, treating the browser as the access control, or running authorization only at deployment are all incorrect descriptions.

The Security Checklist reviews an application's security configuration against recommended practices and highlights gaps. The Clipboard shows runtime data, the Tracer records rule execution, and the Agile Workbench manages backlog items, so none of them performs a security review.

Operators receive access through the access groups assigned to them, and an access group bundles roles and a default portal. Access roles are not attached to individual case instances, and privileges are not stored in personal data pages, so those statements misdescribe how access is managed.

Least privilege grants only the permissions needed, and a read-only access role assigned through an access group achieves this within Pega's access model. Full access depends on user discipline, a supervisor's ID grants rights the analyst should not have, and copying the case type creates an unmanaged duplicate.

A when rule evaluates a condition, here the claim type value, and controls whether the section or field group appears. Access groups control permissions rather than layout, data pages cache data, and channels define entry points, so none of them shows or hides sections based on a field value.

A field group is a reusable collection of fields, so editing it updates every form that references it. Copying fields creates separate versions that drift apart, a separate case type is unnecessary for layout reuse, and validate rules check values rather than arrange fields.

A theme defines visual styling such as colours and fonts, and the portal applies it across its screens. A decision table, data transform and validate rule each handle logic or data rather than the portal's visual appearance.

Channels separate experiences such as customer self-service and employee portals, each with its own entry point and layout. Field groups organize fields within forms, decision tables compute outcomes, and access roles control privileges rather than what each audience sees.

Pega Blueprint uses generative AI to propose an application design from requirements, which the architect then reviews and refines. Knowledge Buddy answers questions from knowledge sources, a GenAI Connect rule configures a call to a model, and a validate rule checks property values rather than generating designs.

Knowledge Buddy answers natural-language questions using connected knowledge sources, which matches the scenario. Pega Blueprint generates application designs, an activity without reference documents would answer without grounding, and a keyword decision tree returns only fixed answers rather than drawing on documents.

GenAI Autopilot helps developers generate application components with generative AI, and the developer reviews the output before using it. Knowledge Buddy serves end-user questions, a GenAI Connect rule is a runtime call inside a flow, and a decision table evaluates conditions rather than drafting components.

A GenAI Connect rule configures how the application calls a generative AI model, so the flow can use the response. A calculated value derives values from other properties, a when rule controls conditional visibility, and Knowledge Buddy serves end-user questions rather than calling a model from a flow.

Continuous integration merges and tests changes frequently with automation, and passing builds feed a delivery pipeline toward production. The other options describe infrequent manual releases, ad hoc copying, or reporting exports, none of which involves automated testing on each commit.

Automated tests that run in the pipeline and must pass before promotion stop broken functionality from moving forward. Manual screenshot reviews are slow and late, disabling an environment does not test the build, and a quarterly log review happens far too rarely to protect a release.

Unit tests verify individual rules against expected results, and regression tests confirm that existing functionality still works after changes. Visual reviews by one stakeholder lack repeatable checks, and load tests run after go-live cannot prevent a faulty deployment.

An insight presents case data as a chart or table, and placing it on a dashboard gives managers a shared page that reflects the current data. A validate rule checks entries, a data transform copies values, and adding a stage changes the case flow rather than producing a view.

Explore Data lets users build charts from case data without code and save the result as an insight that can be placed on dashboards. The Clipboard and Tracer are developer tools for inspecting runtime data and rule execution, and a data transform sets property values rather than producing a chart.

Insights gives business users self-service analysis, so they can explore data and build visual views without waiting on a developer. Automatic approval, replacing case types with one table, and editing records from a chart do not describe the benefit, and the last one would bypass the case flow.