PEGACPSA88V1 Pegasystems Certified Pega System Architect (V8.8) Free Practice Exam Questions (2025 Updated)

To localize correspondence into a language that is unavailable in the Pega language pack, you can create the Translation rule manually and include the rule in the application ruleset. A Translation rule is a rule that defines how to translate text from one language to another. You can create a Translation rule manually by using the Create menu in Dev Studio and selecting Rule > Integration-Resources > Translation. You can then specify the source and target languages, the text to be translated, and the translated text. You can also use a decision table or a connector to provide the translated text. You must include the Translation rule in the application ruleset so that it can be used by the application. References: https://community.pega.com/knowledgebase/articles/integration/86/translation-rules

To achieve the requested behavior, you can use a checkbox and a decision shape to branch the case flow based on whether the customer wants catering or not. You can also use a visibility condition to show or hide the menu preferences and appointment date fields depending on the checkbox value. References: https://community.pega.com/knowledgebase/articles/case-management/88/branching-case-flow-based-decision

These two requirements can be supported by configuring a mobile channel in App Studio. A mobile channel allows you to define various settings and features for your mobile app, such as security, branding, navigation, gestures, push notifications, offline support, and so on. References: https://community.pega.com/knowledgebase/articles/mobile/86/configuring-mobile-app-channels

When the goal interval lapses and the assignment urgency is adjusted to 100, the urgency value continues to increment as configured for the deadline and passed deadline intervals. The urgency value determines how quickly an assignment needs attention and affects how assignments are prioritized in worklists and work queues. References: https://community.pega.com/knowledgebase/articles/case-management/86/configuring-service-levels

To implement this requirement, you can configure a data page to store the make, model, and year vehicle data and configure a connection to an external system of record that contains the make, model, and year vehicle data. A data page is a rule that defines how and when to load data into memory for use by an application. You can configure a data page to source its data from an external system by using connectors or integrations. This way, you can access up-to-date vehicle data from an external database or web service without storing it locally in your application. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/sourcing-data-page-data-external-systems

To meet the requirement, you can add an Identify service animal process within the Travel booking case life cycle and apply a condition to determine when to run the process. The condition can be based on a property that indicates whether the passenger is traveling with a service animal or not. References: https://community.pega.com/knowledgebase/articles/case-management/88/adding-processes-case-life-cycle

The data page is reloaded at 06:42. A data page is a rule that defines how and when to load data into memory for use by an application. The Reload if older than field specifies the maximum age of the data page before it is reloaded from its source. In this case, the data page’s Reload if older than field is set to 15 minutes, which means that the data page will be reloaded if it is older than 15 minutes when it is requested. The data page is created at 06:12, so it will expire at 06:27. At 06:20, the user requests product information, but the data page is not reloaded because it is not expired yet. At 06:42, the user requests product information again, but this time the data page is reloaded because it is older than 15 minutes. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages

To implement this requirement, you can configure a data page to store the make, model, and year vehicle data and configure a connection to an external system of record that contains the make, model, and year vehicle data. A data page is a rule that defines how and when to load data into memory for use by an application. You can configure a data page to source its data from an external system by using connectors or integrations. This way, you can access up-to-date vehicle data from an external database or web service without storing it locally in your application. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/sourcing-data-page-data-external-systems

In these two situations, it is appropriate to use a decision table because they involve deriving values that have one of a few possible outcomes based on multiple variables. For example, the dance studio can use a decision table to recommend different membership types based on different combinations of number and type of dance classes. The hair care company can use a decision table to suggest different product lines based on different combinations of hair characteristics. References: https://academy.pega.com/topic/decision-tables/v1

On a service level, the passed deadline interval is measured from the end of the goal interval. The goal interval defines when to take action because a step or case is taking too long to complete. The passed deadline interval defines when to take further action because a step or case is past the deadline. References: https://academy.pega.com/topic/passed-deadline-interval/v1

To enforce these restrictions when requesting an instant loan, you can use a single Validate rule with two conditions one for income and one for credit card debt. A Validate rule is a rule that tests property values for errors or omissions during case processing. You can define multiple conditions in a Validate rule to check whether the property values meet your business requirements. References: https://community.pega.com/knowledgebase/articles/case-management/86/validating-case-data

Optional actions are actions that users can perform at any time during a stage in the case workflow. They are not required to advance the case to the next stage or step. Optional actions can be used to allow customers to update any of the user profile pages individually during the order placement stage. References: https://community.pega.com/knowledgebase/articles/case-management/88/configuring-optional-actions

These two field types are specialized versions of the Query field type. A Query field type allows users to select a value from a list that is populated by running a report definition rule or by referencing another field value rule. A Case reference field type allows users to select an existing case from a list that is populated by running a report definition rule on the Work- class or one of its subclasses. A Data reference field type allows users to select an existing data object from a list that is populated by running a report definition rule on a specific data class. References: https://community.pega.com/knowledgebase/articles/user-experience/86/configuring-field-types

You should consider using a field value when the list of allowed values is mostly static or shared across all case types. A field value is a rule that defines a single value for a field that is used in multiple places in an application. Field values are useful when the list of values does not change frequently or when the same values are used in different case types. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/field-values