Free PEGACPSSA23V1 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

For offline support, it's necessary to have the access groups configured to allow offline access to

users so that the correct rules and data can be synchronized to the user's device. In addition, the case

types must be configured to function properly in an offline environment, ensuring that users can

create, update, and submit cases without a network connection. Reference: Pega Mobile Client

Developer Guide.

Reference: https://community.pega.com/knowledgebase/articles/configuring-offline-capabilitymobile- application

A: The Application Guardrails landing page does count the number of rules with severe or moderate

warnings, as these can have a significant impact on the application's performance and

maintainability.

B: Guardrail scores exclude Pega Platform core rules since these are established by Pega and are

assumed to be optimized.

C: The landing page also counts the number of rules with no warnings or caution-level warnings,

which contribute positively to the overall compliance score. Reference: Pega official documentation

on the Application Guardrails landing page and guardrail scores.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/PEGA_PEGACPSSA23V1/page_11_img_2.jpg

Reference: https://community.pega.com/knowledgebase/articles/pega-web-mashup/pega-webmashup

Pega Web Mashups enable the embedding of Pega applications within external web pages. A

mashup is initialized by calling a flow or a harness from a Pega application, allowing users to interact

with Pega case management from other applications or portals. Users can also view their worklist in

the external portal and select items to take action on, extending the capabilities of Pega applications

to external platforms. Reference: Pega Platform Help - Pega Web Mashup.

To resolve performance issues caused by resource-intensive queue processors, it's essential to

ensure that these processors are associated with appropriate node types (A) and that application

nodes are configured with node types (D). Associating queue processors with specific node types

allows for the distribution of workload across the application infrastructure, optimizing resource

utilization and improving performance. Configuring application nodes with node types ensures that

tasks are executed on the most suitable nodes, further enhancing system efficiency and scalability.

Reference: Pega Community documentation on queue processors and node types.

The purpose of the Policy Verification landing page in Pega Platform is to test if a user has the

required access to a case (A). This tool allows administrators and developers to verify access control

policies by simulating how the policies would apply to different users, ensuring that the security

configurations align with the application's requirements and that users have appropriate access

levels to cases and data.

Reference: Pega Community documentation on security policies and Policy Verification tool.

The Static Assembler is a Pega tool used to address rules assembly issues specifically when the server

is managing a large number of rules caches. By pre-assembling rules into a static content, the Static

Assembler helps in improving performance in situations where cache management becomes

complex due to the volume of rules. It creates a set of static files that represents the assembled

rules, which can reduce the overhead on the server during rule assembly and cache management.

Reference: Pega official documentation on performance tools and best practices.

To start operations at a specific GMT time regardless of where the server is located, you would use

the Queue-For-Processing method in an activity. This method adds a task to a queue to be processed

either by a standard or a dedicated queue processor. A dedicated queue processor can be configured

to operate on a schedule, so it can start processing at midnight GMT. Reference: Pega SSA course

materials on queue processors and timed events.

You should consider using a field value when the list of allowed values is mostly static. Field values

are best used for properties with values that do not change often and need to be reused throughout

the application. Reference: Pega official documentation on field values.

A: When using a Pega Web Mashup, leveraging the standard authentication service

IACAuthentication and updating the authentication activities to match the external system's

requirements is a common practice.

D: Configuring application permissions by specifying a list of trusted domains in the application rule

is important for security purposes and to control which external domains are allowed to embed the

mashup. Reference: Pega official documentation on Pega Web Mashup configuration.

To ensure that only HR Managers have read access to a candidate's reference letter attachment, the

tasks involved include restricting read access according to a When condition (B) and configuring

attribute-based access control on the Attachment Category (C). The When condition can specify

criteria that must be met for the attachment to be accessible, such as the user's role being an HR

Manager. Attribute-based access control allows for the definition of access rules based on attributes

of the data or user, providing a flexible and granular approach to securing sensitive attachments like

reference letters.

Reference: Pega Community documentation on attachment security and attribute-based access

control.

The two most common ways to expose your application to an external system are to leverage the

Pega API (B) and to create a web service with the Service wizard (D). The Pega API provides a set of

out-of-the-box RESTful endpoints for performing operations within the Pega Platform. The Service

wizard simplifies the creation of SOAP or REST services, enabling external systems to interact with

Pega applications.

Reference: Pega Community documentation on Pega API and Service wizard.

The correct configuration for two parallel cases that run independently is the Subprocess shape with

the Spinoff flow option enabled (Option C). This allows the Retirement planning case to proceed in

parallel without waiting for, or reporting to, the Account review case. Reference: Pega official

documentation on case design and flow shapes.

A Declare OnChange rule is designed to perform an action when a specified property changes. The

action that a Declare OnChange rule can perform includes executing a data transform, which allows

for the automated update of properties when a change is detected in the specified property.

Reference: Pega official documentation on Declare OnChange rules.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/PEGA_PEGACPSSA23V1/page_52_img_2.jpg

Reference: https://academy.pega.com/topic/log-files/v1

To satisfy the requirement where service level intervals vary according to multiple criteria (passenger

status, class of service, and fare type), you would create a multivariate circumstanced rule, a

circumstance definition, and a circumstance template. This allows you to create SLAs that vary based

on the combination of these criteria. Reference: Pega official documentation on circumstancing rules.

In Pega's ruleset hierarchy, a ruleset can reference rules in its own ruleset as well as in any

prerequisites (and their prerequisites, recursively). Since MyCo lists MyCoInt and Customer as its

prerequisites and MyCoInt, in turn, lists Pega-ProcessCommander (which is not relevant here), MyCo

can reference rules in both Homelns and HomelnsInt. However, since only Homelns is explicitly

mentioned in the options, the correct answer is that MyCo can reference rules in Homelns.

Reference: Pega SSA course materials on ruleset hierarchy and ruleset validation.

Pega best practices recommend keeping activities short to enhance maintainability and readability.

Custom Java steps should be limited to reduce complexity and potential errors. Activities should also

be limited in general, with preference given to other rule types that are more declarative and less

procedural, like data transforms, to improve application performance and maintainability. Reference:

Pega SSA course materials on activity best practices.

In Pega's Enterprise Class Structure (ECS), standard functionalities that are shared across multiple

applications within an organization, such as sending a confirmation email, should be placed at the

Organization layer. This allows for reusability and standardization across various implementations

within the organization. Reference: Pega best practices for class design and ECS.

To create a class join in a report definition, you must select the type of match for key values (A) and

create a prefix for the joined class (C). Selecting the type of match, such as Inner Join or Left Outer

Join, determines how records from the primary class and the joined class are combined based on

matching key values. Creating a prefix for the joined class helps in distinguishing properties from the

joined class from those of the primary class, preventing naming conflicts and clarifying the report

definition. These actions are fundamental steps in setting up class joins in report definitions to

retrieve and display data from multiple related classes.

Reference: Pega Community documentation on report definition and class joins.