Pegasystems PEGAPCSSA87V1 Exam Dumps & Practice Test Questions

Question 1:

In which type of rule can an Edit Validate rule be applied directly in Pega?

A. Properties
B. Flow actions
C. Activities
D. Case types

Correct Answer: A

Explanation:

Edit Validate rules in Pega are designed to enforce strict formatting requirements on user input. These rules are applied to data elements to ensure that the information entered meets predefined syntactic or structural criteria before it can be saved or processed. A typical use case might involve checking if a value conforms to a ZIP code pattern, validates an email address format, or ensures a phone number consists of only digits.

The correct option is A, which refers to Property rules. Property rules define the individual data fields used in a Pega application, such as .Email, .PhoneNumber, or .ZipCode. When an Edit Validate rule is applied to a property, it automatically validates the input value against the specified logic when the data is entered through a user interface. This validation typically occurs on form submission, and if the input doesn’t match the expected format, an error message is displayed to the user, prompting correction before proceeding.

The validation logic inside an Edit Validate rule is often written in Java and may use regular expressions or custom code to evaluate the input. This makes it suitable for enforcing strict data entry standards early in the workflow, helping to reduce errors and improve data integrity.

Now let’s look at why the other options are incorrect:

• B. Flow actions manage user navigation through assignments in a case but do not directly support attaching Edit Validate rules. Validation in flow actions is typically handled using other rule types like Validate rules or post-processing logic, not Edit Validate rules.

• C. Activities are procedural constructs used to perform tasks such as setting values or calling other rules. While an activity can invoke a property that has an Edit Validate rule attached, the Edit Validate rule itself is not configured within the activity.

• D. Case types define the overarching structure of a workflow or business process. Although validation can be part of a case's life cycle—such as entry/exit criteria or stage validation—Edit Validate rules are not applied directly on case types.

In conclusion, Edit Validate rules are directly linked to Property rules in Pega. Their role is to ensure that the data entered into specific fields complies with formatting rules at the property level, making A the correct and only valid answer.

Question 2:

When building reports with multiple data sources in Pega, which two statements distinguish an association rule from a class join? (Choose 2.)

A. Class joins allow linking multiple classes, but associations are limited to one class only
B. Users with proper permissions can use associations in the User portal when creating reports
C. Class joins are specific to individual reports, while associations can be reused across reports
D. You must define a class join to apply filter conditions in a report 

Correct Answer: B, C

Explanation:

In Pega’s reporting framework, combining data from multiple classes is a common requirement, especially when generating insightful reports that span across various case types, subcases, or related data objects. Two primary mechanisms to achieve this are class joins and association rules. While both serve to connect different classes (tables) in reports, they differ significantly in scope, accessibility, and reusability.

Option B is correct. Associations are defined independently of any single report and can be accessed by multiple users, including business users with reporting privileges in the User portal. This makes associations particularly useful in environments that support self-service reporting. Users don’t need to understand the database schema to join related data—they can simply select a pre-defined association, which streamlines the process and reduces errors.

Option C is also correct. Associations are reusable objects stored at the system level. Once created, they can be used in any number of reports, making them an efficient way to standardize how data relationships are established. In contrast, class joins are defined within the context of an individual report and are not retained for use elsewhere. Each time a user wants to create a similar join in another report, they must rebuild it from scratch.

Let’s evaluate the incorrect choices:

• Option A is misleading. Both associations and class joins can be configured to handle multiple relationships depending on the design. Associations can support complex mappings between classes just like class joins, though they are pre-built and often more structured.

• Option D is also incorrect. Adding a filter condition in a report does not require a class join. Filters can be applied directly to the main class or to fields accessed through associations. Joins are only necessary when additional data from related classes is required—not for basic filtering.

In summary, associations enhance reusability and accessibility in report building, especially for non-technical users. Class joins, while flexible, are localized and must be recreated per report. Therefore, the distinguishing characteristics are captured in B and C.

Question 3:

In an application using the class group MyCo-HR-SelfService-Work, there are two child classes: MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense. 

If a report is built on the MyCo-HR-SelfService-Work class group, which instances will it include in the report results?

A. All instances from every class derived from Work-
B. Instances from MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense, but only if they share the same database table
C. Instances from both MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense
D. Only instances directly from the MyCo-HR-SelfService-Work class

Correct Answer: C

Explanation:

In Pega, a class group is used to collect multiple work types under a common parent class. This parent, known as the class group, allows different related work object types to share a single database table for easier data access and unified reporting.

In this scenario, the class group is MyCo-HR-SelfService-Work, and its child classes—MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense—are structured as subclasses under this group. Since these subclasses inherit from the class group and follow a consistent naming convention, they are assumed to share the same database table as defined by the class group. This shared data structure is what enables consolidated reporting.

When a report is created at the class group level, it is designed to include records from all of its child classes, provided they are part of the same class hierarchy and use the same underlying database table. That’s precisely the case with the TimeOff and Expense classes mentioned here. Therefore, a report built on MyCo-HR-SelfService-Work will include all records created in the TimeOff and Expense classes, since they belong to the same reporting scope.

Now, examining the incorrect choices:

• Option A is incorrect because it overstates the scope. While MyCo-HR-SelfService-Work derives from Work-, that does not mean a report on it includes all Work- derived classes across the application. It only includes its subclasses.

• Option B introduces a condition about different tables, but the question doesn't indicate that the subclasses are stored in different tables. Since they are part of the same class group, the assumption is they share the table, making this option less precise than C.

• Option D is wrong because the class group itself rarely stores direct instances. It acts as a container for the actual concrete work types like TimeOff and Expense.

Therefore, the most accurate response is C, as it correctly reflects that the report pulls from both TimeOff and Expense classes under the shared class group.

Question 4:

A Fulfillment report needs to show the user ID of the employee who handled packaging in an Order case. The report uses data from MyCo-Orders-Work-Ship and Data-Admin-Operator-ID. 

Which two methods independently allow the report to display the required user information? (Choose 2.)

A. Define a class join between the report’s primary class and the operator class
B. Pass the user ID as a parameter in the report definition
C. List both classes under the Pages & Classes tab in the report definition
D. Create an association rule to link operator data to the shipping case data

Correct Answers: A, D

Explanation:

To generate a report that combines data from different classes—specifically, work class data from MyCo-Orders-Work-Ship and operator details from Data-Admin-Operator-ID—a valid relationship must be established between the two classes. This enables the report to display fields, such as the packager's user ID, from both sources.

Option A is correct. A class join allows you to merge data from two classes based on a shared key—usually the operator ID. In this context, you would configure a join in the report definition to connect the shipping work class to the operator class. This join fetches operator-specific fields, like user ID or full name, allowing those fields to appear in the Fulfillment report alongside case data.

Option D is also correct. Using an association rule is a clean and reusable way to create a predefined relationship between two classes. Once set up, the association can be reused across multiple reports and referenced easily within the report definition. For example, an association that maps the packaging operator ID in the case to the corresponding record in Data-Admin-Operator-ID will enable seamless data retrieval without requiring a manually configured join in each report.

Now, reviewing the incorrect options:

• Option B is not valid. While parameters can be used to filter or drive conditions in a report, they cannot fetch fields from unrelated classes. A parameter is a runtime value—not a link between data sources—so it doesn’t enable reporting across two classes.

• Option C refers to the Pages & Classes tab, which is used in rule forms like activities or flows—not reports. Merely declaring both classes here does not establish any actual relationship between the data sources, and thus cannot be used to display cross-class data in a report.

In summary, to include the user ID from Data-Admin-Operator-ID in a report built on MyCo-Orders-Work-Ship, you need to either configure a class join or define an association rule—both of which establish the necessary connection to pull in user-specific data.

Question 5:

Which three elements are included in calculating and displaying the compliance score of a Pega application?

A. Application rules that generate warnings
B. Core rules from the Pega Platform used in the application
C. Application rules with unresolved or unjustified warnings
D. Raw, unweighted compliance score
E. The proportion of rules that comply with best practices

Answer: A, C, E

Explanation:

In Pega, the compliance score serves as a crucial indicator of how closely an application adheres to Pega’s recommended development standards, commonly referred to as guardrails. This score is automatically generated and presented to help developers and architects monitor application health, maintainability, and long-term scalability. The score evaluates how well the application's custom rules follow best practices and highlights areas that may need remediation.

One component of the compliance score (A) is the presence of rules that generate warnings. These warnings typically indicate deviations from guardrails—for example, excessive use of custom Java steps, complex decision logic, or data access patterns that may lead to performance or maintainability issues. Such warnings reduce the overall score, signaling potential problems in the code base.

Another key factor (C) is the number of rules with unjustified warnings. In Pega, developers are encouraged to justify certain warnings if they must intentionally diverge from best practices for valid reasons. However, if these warnings remain unjustified, the score is penalized more heavily. This helps enforce accountability and ensures developers consciously evaluate every deviation from best practice.

Additionally, the compliance report includes (E) the percentage of compliant rules, which gives a direct measure of how many rules meet Pega’s guardrails without generating any warnings. This is one of the most straightforward indicators of development quality. A higher percentage suggests the application is well-structured, easier to maintain, and more aligned with upgrade-safe practices.

As for the incorrect options:

• B refers to Pega Platform core rules, which are part of the system’s foundation and are not factored into the compliance score. The score evaluates custom application rules, not those from the base platform.

• D, the unweighted compliance score, is not a standard metric reported in the compliance dashboard. The system presents a weighted score that accounts for rule counts, severity, and whether warnings are justified.

To summarize, the compliance score provides meaningful insights into development discipline and code health by focusing on rules with warnings, unjustified warnings, and the overall percentage of compliant rules. The correct items included in this metric are A, C, and E.

Question 6:

A user reports that it takes five seconds for a step in a process to complete and display the next screen. Which diagnostic tool should be used to collect and assess performance metrics for this issue?

A. Tracer
B. Database Trace
C. Performance Analyzer (PAL)
D. Performance Profiler

Answer: C

Explanation:

When users report sluggish behavior in a Pega application—such as noticeable delays during transitions between steps—the most appropriate tool to investigate overall system performance is the Performance Analyzer (PAL). This tool is specifically designed to monitor and analyze runtime performance metrics for individual requestors and sessions.

PAL provides valuable statistics including CPU time, database query duration, rule resolution times, cache hits, and overall system resource usage during a user’s session. By using PAL, developers or administrators can capture performance snapshots before and after specific user actions—such as form submissions or screen loads—and identify exactly where the delay occurs.

Option A, Tracer, is primarily a debugging tool used to trace rule execution paths, such as when rules are triggered, in what order, and what values are being passed. While it helps in debugging logical errors and rule configurations, it does not provide a comprehensive performance overview or real-time system metrics.

Option B, Database Trace, focuses narrowly on SQL interactions. It logs queries sent to the database, their execution times, and parameters. Although useful for pinpointing specific database bottlenecks, it doesn’t give a holistic picture of performance across the entire user transaction flow.

Option D, Performance Profiler, is useful for identifying how much time is spent executing individual rules—such as activities or data transforms. It offers more detail at the rule level but lacks PAL’s broader ability to analyze end-to-end transaction performance, including things like network latency or general resource usage.

In summary, when diagnosing a user-reported performance delay like the one described, PAL is the best starting point. It provides both macro-level and granular insights into what is affecting system response time. By capturing PAL readings before and after the step, developers can isolate problem areas and take corrective actions, whether they involve optimizing database queries, refactoring rules, or reallocating system resources. Thus, the correct answer is C — Performance Analyzer (PAL).

Question 7:

What is the primary function of the Purge/Archive wizard in Pega when aiming to enhance system performance?

A. Erase properties that have been exposed in database columns from the BLOB
B. Eliminate unused cached rule data stored in memory
C. Remove outdated stored SQL procedures from the database
D. Delete historical case data from the work object table

Correct Answer: D

Explanation:

The Purge/Archive wizard in Pega is a vital tool for improving application performance by managing the volume of data stored in the system. As applications accumulate more data—especially completed or obsolete cases—system performance can begin to degrade due to the increasing burden on storage and database operations.

Option D, which refers to deleting old cases from the system's work object database table, accurately describes the wizard’s main use. As applications age and grow, they tend to retain thousands—or even millions—of cases that are no longer active but remain stored in the database. These stale records can slow down system queries, reporting, indexing, and general responsiveness. By purging (deleting) or archiving (moving) these outdated cases, administrators can reduce the size of the active data set and, in turn, improve the system’s efficiency.

The wizard enables administrators to define purge criteria—such as age, status, or case type—and choose whether to permanently delete the data or archive it to external storage for future retrieval. This dual functionality supports both performance goals and compliance with data retention policies.

Let’s examine why the other options are incorrect:

Option A refers to deleting exposed properties from the BLOB. In Pega, "exposed" properties are stored in separate database columns for improved reporting and querying. Managing these properties is done through property optimization or de-optimization—not through the Purge/Archive wizard.

Option B suggests that the wizard can remove cached rules, which is false. Rules cache is managed through Pega’s internal cache management mechanisms or during system restarts. Clearing or rebuilding the rules cache is outside the scope of the Purge/Archive wizard.

Option C discusses deleting updated SQL procedures. This refers to database-level actions typically handled by DBAs. The Purge/Archive wizard does not interact with stored procedures and is not intended for managing procedural code.

In conclusion, the Purge/Archive wizard is designed specifically to remove historical or obsolete case data from the database, which directly contributes to better performance and cleaner data management in high-volume environments. This makes Option D the correct choice.

Question 8:

If you need to prevent an application from using a rule in a locked ruleset with an Apply-To class of TGB-HRApps-Work-Review, which method is appropriate?

A. Recreate the rule in the TGB class, mark it as Final
B. Recreate the rule in TGB-HRApps-Work-Review and set it to Not Available
C. Recreate the rule in TGB-HRApps-Work-Review and mark it as Blocked
D. Recreate the rule in TGB-HRApps-Work-Review and set the availability to Withdrawn

Correct Answer: D

Explanation:

In Pega, when dealing with rules stored in a locked ruleset, direct modifications or deletions are not allowed. However, Pega provides mechanisms to override or suppress the behavior of such rules through availability settings. If you want to prevent a rule in a locked ruleset from executing, the most effective approach is to create a new version of the same rule in a higher, unlocked ruleset and set its availability to “Withdrawn.”

Option D is correct because setting a rule’s availability to Withdrawn within the same class (TGB-HRApps-Work-Review) instructs Pega’s rule resolution algorithm to stop searching for lower versions of the rule in the stack. This includes any copies of that rule in locked rulesets. Therefore, the system will completely skip that rule, effectively suppressing its execution without throwing an error.

Why the other options don’t work:

Option A suggests saving the rule in the TGB class and setting it as Final. This would prevent it from being overridden in subclasses, but it doesn’t block the use of the original rule in the subclass (TGB-HRApps-Work-Review). The rule in the subclass would still take precedence during resolution.

Option B uses the “Not Available” status, which prevents the specific version of the rule from being used but does not stop the system from falling back to earlier versions in the stack—such as the one in the locked ruleset. Therefore, this doesn’t fully solve the issue.

Option C sets the rule to “Blocked,” which forces the system to throw a runtime error if the rule is invoked. This is typically used to intentionally disable a rule due to security or functional risks. However, it leads to system failures and is not a graceful way to override behavior.

To summarize, the Withdrawn availability setting is the cleanest and safest method to prevent rule resolution from reaching a specific rule—especially one in a locked ruleset—without introducing runtime errors or affecting other parts of the system. Therefore, Option D is the most appropriate choice.

Question 9::

When configuring case types in Pega, which two features help streamline and automate case lifecycle management? (Choose 2.)

A. Stage-based case design
B. Data page caching strategies
C. Decision table validation
D. Case dependency management
E. Guardrails enforcement

Correct Answers: A, D

Explanation:

In Pega, case lifecycle management is a core aspect of application development. Managing how cases move through their stages and how they depend on other cases or subcases is crucial for delivering scalable and maintainable business processes.

Option A is correct because stage-based case design is a foundational concept in Pega’s case management model. It organizes the case lifecycle into clear stages (e.g., New, In Progress, Resolution), each containing multiple processes or steps. This structure provides a visual and intuitive framework for managing how cases progress. Stages make it easier to define and automate workflow logic, such as entry criteria, routing, and escalations, ensuring that the process reflects real business logic.

Option D is also correct. Case dependency management allows developers to create relationships between parent and child cases or between peer cases. For example, you can configure a parent case to wait for all its child cases to reach a certain status before continuing. This feature is especially useful for coordinating complex business workflows where multiple parallel tasks must be completed before advancing.

Option B, data page caching, is more related to optimizing data retrieval and not directly tied to managing the lifecycle of a case.

Option C, decision table validation, relates to decision-making logic but doesn’t streamline the case lifecycle itself. It helps in ensuring business rules are correct but is more about rule validation than lifecycle automation.

Option E, guardrails enforcement, helps maintain application quality but is not a feature that directly automates or structures the case flow.

To summarize, stage-based design and case dependencies are both essential tools that Senior System Architects use to model efficient and maintainable workflows in Pega. These features support scalability and reduce development complexity while aligning automation with real-world business requirements.

Question 10:

What are two primary benefits of using data transforms in Pega application development? 

A. Dynamically create UI layouts for user portals
B. Automate property value assignments during case processing
C. Invoke REST APIs from external systems
D. Pre-populate forms with default values
E. Schedule background jobs and batch processes

Correct Answers: B, D

Explanation:

Data transforms in Pega are powerful tools used for manipulating and setting property values within an application. They are primarily used for assigning values, transforming data between structures, and initializing data during case processing.

Option B is correct. One of the core uses of data transforms is to automate the assignment of property values. Developers can use them to set values based on expressions, constants, or by copying from other properties. This is especially helpful during case creation or when transitioning between stages, as it ensures consistency and reduces manual intervention.

Option D is also accurate. Data transforms can be configured to pre-populate user forms with default values. For instance, when a case type is instantiated, a data transform can run automatically to assign default values to fields like the current date, logged-in user, or standard rates. This enhances user experience and speeds up data entry.

Option A is incorrect because data transforms are not involved in UI design or layout creation. UI configuration is handled through section rules and dynamic layouts, not through data manipulation tools like data transforms.

Option C is misleading. While Pega does allow calling external systems via REST APIs, this is typically done using connect rules, data pages, or integration connectors. Data transforms may support the structuring of request/response data before or after a call, but they don’t directly handle the invocation.

Option E refers to scheduling and running batch processes, which is handled by Job Schedulers or Queue Processors, not data transforms.

In conclusion, data transforms simplify the process of managing data throughout the application. They ensure consistency in value assignments and reduce the complexity of custom Java or decision rules for handling data logic. The correct answers—B and D—represent the most typical and impactful uses of data transforms in Pega application development.