Pega Certified System Architect (PCSA) Interview Questions

While some interviewers have their own method of questioning, the majority of job interviews follow a set of questions and responses (including some of the most often-asked behavioural interview questions). Here are some of the most common interview questions, as well as some of the best answers. To begin, consider the following professional advice for preparing for your Pega Certified System Architect (PCSA) interview:

Advanced Interview Questions

Can you explain key concepts of PRPC and how they work together to build a process-driven application?

PRPC stands for PegaRULES Process Commander, it is a business process management framework that enables the development of process-driven applications. It allows developers to create and manage business processes, automate decision-making, and create a unified customer experience across multiple channels.

Some of the key concepts of PRPC include:

Rule-based architecture: PRPC uses a rule-based architecture to model business processes and automate decision-making.
Process flows: PRPC allows for the creation of process flows, which are diagrams that represent the steps involved in a business process.
Rules: PRPC uses rules to define the behavior of the application, including decision-making, data validation, and more.
User interface: PRPC provides a user interface that allows users to interact with the application and view the status of their processes.

Overall, PRPC is a powerful framework that allows developers to build process-driven applications quickly and efficiently, with a focus on automation and decision-making.

How do you design and implement business rules and decision tables in Pega?

In Pega’s PRPC framework, business rules and decision tables are used to define the behavior of the application and automate decision-making.

Designing business rules in PRPC involves creating a rule hierarchy and defining the conditions, actions, and exceptions for each rule. The rule hierarchy is a hierarchical structure that organizes rules into a logical structure, with higher-level rules providing context for lower-level rules.

To create a business rule in PRPC, you can use the Rule Designer, which is a visual tool that allows you to create, edit, and manage rules. You can create different types of rules, such as decision rules, data transform rules, and more.

Decision tables are used to define complex decision-making logic in a clear and easy-to-understand format. In PRPC, decision tables are created using the Decision Table Rule form. You can create a decision table by defining the conditions, actions, and exceptions in a tabular format.

To implement a decision table, you need to:

Define the conditions for the decision table.
Define the actions that should be taken based on the conditions.
Map the conditions and actions to the decision table.
Test the decision table to ensure it is working as expected.

Once you have created and tested your business rules and decision tables, you can use them in your process flows to automate decision-making and define the behavior of your application.

Can you walk me through a recent Pega project you led, including the challenges you faced and how you overcame them?

the project was to build a process-driven application for a retail company to manage their inventory and customer orders. The project would involve creating process flows, business rules, and decision tables to automate the inventory management and customer order processes.

Some of the challenges that may have been faced during the project include:

Complex business requirements: The retail company may have had complex business requirements that required a large number of rules and decision tables to be created.
Integration with other systems: The application may have needed to integrate with other systems such as a warehouse management system or a customer relationship management system.
Data validation and security: The application may have needed to ensure that data was validated and secure, to protect sensitive customer and inventory information.

To overcome these challenges, the following steps could have been taken:

Break down the complex business requirements into smaller, manageable tasks.
Use Pega’s integration capabilities to connect the application to other systems.
Use Pega’s built-in security features to validate and secure data.
Create a detailed test plan and conduct thorough testing to ensure that the application was working as expected.
Continuously review and monitor the application’s performance and make any necessary improvements.

By taking these steps, the project team could have successfully built a process-driven application that automates the inventory management and customer order processes for the retail company.

How do you handle data validation and error handling in Pega?

In Pega’s PRPC framework, data validation and error handling are achieved through the use of rules and data transforms.

Data validation rules are used to ensure that the data entered into the application is in the correct format and meets the business requirements. PRPC provides built-in data validation capabilities, such as the use of regular expressions to validate data, as well as the ability to create custom validation rules.

To handle data validation, you can create a data validation rule and map it to the field or property that you want to validate. The validation rule will be triggered when the user submits the form and will check the data against the validation criteria you have defined. If the data is invalid, the rule will return an error message and prevent the form from being submitted.

Error handling in PRPC is the process of catching and responding to exceptions or errors that occur during the execution of the application. PRPC provides built-in error handling capabilities, such as the ability to catch and handle exceptions, as well as the ability to create custom error handlers.

To handle errors, you can create an error handler rule and map it to the process or flow where you want to catch the error. The error handler rule will be triggered when an exception occurs and will handle the exception based on the criteria you have defined. For example, you can use the error handler to redirect the user to a different page, display an error message, or log the error.

Overall, PRPC provides a flexible and powerful set of tools for data validation and error handling, allowing developers to ensure that the application is functioning as expected and providing a good user experience.

Can you explain how you use Pega’s built-in reporting and analytics features?

Pega’s PRPC framework provides built-in reporting and analytics features that allow you to create, view, and analyze data within the application. Some of the key features include:

Reports: PRPC provides a built-in reporting engine that allows you to create and view reports on various aspects of the application. Reports can be created using a drag-and-drop interface, making it easy to create complex reports without any coding. Reports can be viewed in different formats, such as tabular, chart, and map, and can be exported to different formats, such as PDF, Excel, and CSV.
Dashboards: PRPC provides a dashboard feature that allows you to create customized dashboards to view and analyze data. Dashboards can be created using a drag-and-drop interface, making it easy to create and customize dashboards without any coding. Dashboards can be shared and embedded in other applications, and can be viewed in different formats, such as tabular, chart, and map.
Analytics: PRPC provides built-in analytics features that allow you to analyze data and create insights. The analytics feature provides a set of pre-built data models, algorithms, and visualizations that allow you to quickly and easily analyze data, without the need for complex coding.
Pega Intelligence: Pega Intelligence is a built-in feature in Pega Platform that enables you to create advanced analytics and predictive models, that can be embedded on the platform.

To use Pega’s built-in reporting and analytics features, you would first need to define the data sources you want to use, such as case data, performance data, or external data sources. Once the data sources are defined, you can use the reporting and analytics features to create and view reports and dashboards, as well as analyze data and create insights.

It is worth mentioning that Pega also provides the ability to integrate with third-party reporting and analytics tools like Tableau, Power BI and more, to gain more advanced capabilities and flexibility.

How do you implement and manage security and access controls in Pega?

Implementing and managing security and access controls in Pega’s PRPC framework is achieved through the use of access groups, access roles, and access roles with rules.

Access groups: Access groups are used to group users together based on their role or job function. Each user is assigned to one or more access groups, and each access group is assigned a set of access roles.
Access roles: Access roles are used to define the permissions that a user has within the application. Access roles can be assigned to access groups, and a user’s permissions are determined by the access roles that are assigned to the access groups to which they belong.
Access roles with rules: Access roles with rules allow you to define fine-grained access controls that are based on the specific data or actions that a user is trying to access or perform. Access roles with rules are used to define the conditions under which a user can access or perform a specific action.

To implement security and access controls in Pega, you would first need to define the access groups and access roles that are required for your application. Then, you would need to assign the appropriate access roles to the access groups and assign users to the appropriate access groups.

Once the access roles and access groups are defined and assigned, you can use the built-in security features in PRPC, such as the Data-Admin-Security class, to define the data access and security controls that are required for your application. Additionally, you can use the built-in validation rules to ensure that users can only access or perform actions on data that they are authorized to access or perform actions on.

Managing access controls in Pega can be done through the use of built-in tools, such as the Access Group and Access Role editors, which allow you to view and manage access groups and access roles, respectively. Additionally, you can use the built-in reporting features to view and analyze access control data and detect any potential security issues.

Overall, Pega’s PRPC framework provides a robust set of tools for implementing and managing security and access controls, allowing you to ensure that your application is secure and that users can only access the data and perform the actions that they are authorized to access and perform.

Can you explain your experience with Pega’s integration capabilities, such as SOAP and REST services?

Pega’s PRPC framework provides built-in support for integrating with external systems using SOAP and REST services. Some of the key features and capabilities include:

SOAP integration: PRPC provides built-in support for integrating with SOAP web services. You can create a service rule that defines the SOAP web service and the operations that you want to call. You can then use the service rule to invoke the web service and process the response.
REST integration: PRPC provides built-in support for integrating with RESTful web services. You can create a service rule that defines the RESTful web service and the operations that you want to call. You can then use the service rule to invoke the web service and process the response.
Connectors: Pega provides connectors to integrate with different system, such as Salesforce, SAP, and Oracle.
External system integration: Pega provides the ability to create custom connectors to integrate with external systems that are not supported out of the box. You can use the Connect-SOAP and Connect-REST classes to create custom connectors and invoke web services.
Authentication: Pega supports different authentication methods, such as Basic Authentication, OAuth, and SAML.
Event-Driven Architecture : Pega provides the ability to build event-driven architecture to integrate with external systems.
Pega API : Pega provides the ability to access Pega’s functionality through an API.

To use Pega’s integration capabilities, you would first need to define the external systems that you want to integrate with and the operations that you want to call. Then, you would need to create the appropriate service rule for the type of integration you are using (SOAP or REST) and configure the service rule with the appropriate settings. Once the service rule is configured, you can use the service rule to invoke the external system and process the response.

It is worth mentioning that Pega also provides the ability to integrate with different protocols, such as MQ, JMS, and more, to gain more advanced capabilities and flexibility.

How do you handle performance tuning and optimization in Pega?

Performance tuning and optimization in Pega’s PRPC framework is a multi-faceted process that involves several different techniques and approaches.

Database Optimization: One of the key areas to focus on when tuning Pega performance is the database. This includes optimizing database queries, indexes, and the database schema to improve performance.
Data Model Optimization: Reviewing the data model and simplifying it can help improve performance by reducing the amount of data that needs to be loaded and processed.
Rule Optimization: Reviewing the rules and optimizing them can help improve performance. This includes optimizing the rules that are called frequently and identifying and removing any rules that are not being used.
Caching: Pega’s PRPC framework provides built-in caching mechanisms that can be used to improve performance. This includes caching data and rules to reduce the number of calls to the database and the number of rule evaluations.
Memory Management: Reviewing the amount of memory that Pega is using and optimizing it can help improve performance by reducing the amount of memory that Pega needs to use.
Thread Management: Reviewing and optimizing the number of threads that Pega is using can help improve performance by reducing the number of threads that Pega needs to use.
System Configuration: Reviewing and optimizing the system configuration settings can help improve performance by configuring Pega to use the resources that are available on the system more effectively.
Monitoring: Monitoring the performance of the Pega application and identifying any bottlenecks can help identify areas that need to be optimized.

To implement performance tuning and optimization in Pega, you would first need to identify the areas of the application that are causing performance issues. Once the areas have been identified, you can then use the techniques and approaches mentioned above to optimize the performance of the application. Additionally, Pega provides built-in performance monitoring and diagnostic tools that can be used to identify performance issues and monitor the performance of the application over time.

It’s worth mentioning that Pega 7.4 and above use the Intelligent Decisioning which helps the performance of decisioning by caching and reuse of decisioning data.

Overall, performance tuning and optimization in Pega’s PRPC framework is a process that requires a combination of different techniques and approaches, including database optimization, data model optimization, rule optimization, caching, memory management, thread management, system configuration and monitoring. By using these techniques and approaches, you can improve the performance of your Pega application and ensure that it is running as efficiently as possible.

Can you explain your experience with Pega’s mobile and offline capabilities?

My experience with Pega’s mobile and offline capabilities is that Pega provides several built-in features and tools that can be used to create mobile applications that can function offline.

Pega Mobile App Studio: Pega’s Mobile App Studio is a visual development tool that enables developers to create mobile applications using drag-and-drop functionality. It allows for the creation of native mobile apps for iOS and Android.
Pega Offline: Pega offline allows users to continue working on their case when they are disconnected from the internet. Pega offline stores the data locally and syncs it with the server once the user reconnects to the internet.
Pega Mobile Push Notifications: Pega supports mobile push notifications to alert users of new cases, assignments, and messages.
Pega Mobile Offline Forms: Pega’s offline forms allow users to complete forms and submit them even when they are offline. The forms are automatically submitted once the user reconnects to the internet.
Pega Mobile SDK: Pega provides a mobile software development kit (SDK) that can be used to develop custom mobile applications that can interact with Pega’s PRPC framework.
Pega Mobile App Security: Pega provides built-in security features for mobile applications, including support for single sign-on (SSO) and two-factor authentication (2FA).

To implement mobile and offline capabilities in Pega, you would use the tools and features provided by Pega, such as the Mobile App Studio, Pega Offline, and Pega Mobile SDK. Additionally, you would need to configure the application to work offline and ensure that the data is synced correctly when the user reconnects to the internet.

Overall, Pega provides a robust set of tools and features for creating mobile applications that can function offline, including the Mobile App Studio, Pega Offline, Pega Mobile Push Notifications, Pega Mobile Offline Forms, Pega Mobile SDK, and Pega Mobile App Security. These tools and features can be used to create mobile applications that provide users with a seamless experience, even when they are offline.

How do you handle system upgrades and maintenance in Pega?

Handling system upgrades and maintenance in Pega typically involves the following steps:

Planning: Before upgrading, it’s important to plan the upgrade process and identify any potential issues or challenges that may arise. This includes identifying the version of Pega that you are currently using, the version you want to upgrade to, and any dependencies or customizations that may be affected.
Backup: It is important to take a backup of the current system before upgrading. This includes taking a backup of the database, the application, and any other related files.
Testing: After the upgrade, it is important to test the system to ensure that it is working correctly and that there are no issues or errors. This includes testing the system in a test environment and then in a production environment.
Deployment: Once the system has been tested and any issues have been resolved, the upgrade can be deployed to the production environment. This involves installing the new version of Pega and updating any dependencies or customizations that may be affected.
Monitoring: After the upgrade, it is important to monitor the system to ensure that it is working correctly and that there are no issues or errors. This includes monitoring the system logs and performance metrics, and addressing any issues that may arise.
Maintenance: Once the upgrade is complete, it is important to maintain the system to ensure that it continues to work correctly. This includes performing regular maintenance tasks, such as database maintenance, and applying any necessary patches or updates.

Pega also provides several built-in features and tools to help with system upgrades and maintenance, such as Pega Upgrade Manager, which automates the process of upgrading Pega, and Pega System Management, which provides a single point of control for monitoring, managing, and maintaining your Pega system.

Overall, handling system upgrades and maintenance in Pega requires a good understanding of the Pega platform, the version of Pega that you are currently using, the version you want to upgrade to, and any dependencies or customizations that may be affected. It is important to plan the upgrade process, take a backup of the current system, test the system, deploy the upgrade, monitor the system and maintain it to ensure that it continues to work correctly. Pega also provides built-in features and tools to help with system upgrades and maintenance, such as Pega Upgrade Manager and Pega System Management.

Can you explain your experience with Pega’s case management and workflow capabilities?

Pega’s case management and workflow capabilities allow you to create and manage complex business processes within the Pega platform. This includes the ability to create and manage cases, which are instances of a specific business process, and the ability to create and manage workflows, which are the series of steps that make up a case.

The case management in Pega allows organizations to automate and streamline their business processes, by providing a centralized location for managing and tracking cases. Cases can be created, assigned, and tracked by users, and can be linked to other cases and workflows. This allows for the efficient management of business processes, and allows organizations to easily track and report on the status of cases.

Pega’s workflow capabilities allow you to define and manage the steps that make up a case. Workflows can be created using a drag-and-drop interface, and can include a wide range of activities such as data validation, decision making, and communication. Pega also provides a built-in rule engine, which allows you to create and manage business rules within the workflow. This allows you to define the logic that governs the flow of the case, and to automate decision-making within the workflow.

Pega also provides tools for monitoring and reporting on workflows and cases, such as the Case Explorer and the Work Manager. These tools allow you to view and track the status of cases and workflows, and to generate reports on case and workflow performance.

In summary, Pega’s case management and workflow capabilities provide a centralized location for managing and tracking business processes, allowing for efficient management and tracking of cases, and providing a drag-and-drop interface for creating and managing workflows. Pega’s built-in rule engine allows for the automation of decision-making within the workflow, and Pega provides tools for monitoring and reporting on workflows and cases.

How do you handle testing and quality assurance in Pega projects?

Testing and quality assurance (QA) are critical components of any Pega project, as they help ensure that the application is functioning as expected and meets the requirements of the business.

Here are some ways that testing and QA can be handled in Pega projects:

Unit testing: Unit testing is the process of testing individual units of code, such as rules, activities, and flows, to ensure that they function as expected. Pega provides tools for creating and executing unit tests, such as the Unit Test harness, that allows developers to create and execute unit tests for their code.
Functional testing: Functional testing is the process of testing the application as a whole to ensure that it meets the requirements of the business. Pega provides tools for creating and executing functional tests, such as the Test harness, that allows developers and QA testers to create and execute functional tests for the application.
Performance testing: Performance testing is the process of testing the application to ensure that it can handle the expected load and performance requirements. Pega provides tools for creating and executing performance tests, such as the Performance Test harness, that allows developers and QA testers to create and execute performance tests for the application.
Automated testing: Automated testing is the process of automating the execution of tests, which can be done using tools like Selenium or Test Complete. Pega provides an integration with these tools which allows creating automated test scripts that can run functional and regression tests.
User Acceptance Testing (UAT): User acceptance testing is the process of testing the application with real-world users to ensure that it meets their needs and expectations. UAT can be done by creating test cases and scenarios that mimic real-world usage, and having users test the application using these scenarios.
Data validation: Pega allows creating validation rules and constraints to ensure data integrity and quality. These rules are enforced when the data is entered and are also used for data migration and integration.

In summary, testing and QA in Pega projects can be handled by using a combination of unit testing, functional testing, performance testing, automated testing, User Acceptance Testing (UAT) and data validation, using the built-in tools and integration with other testing tools that Pega provides.

Can you explain your experience with Pega’s deployment and version management process?

Deployment and version management are critical components of any Pega project, as they help ensure that the application is deployed and versioned correctly, and that the appropriate version of the application is running in each environment.

Here are some ways that deployment and version management can be handled in Pega projects:

Environment management: Pega provides a built-in environment management system that allows developers and administrators to manage different environments, such as development, test, and production. This includes creating and configuring environments, and managing the flow of changes between them.
Version control: Pega provides built-in version control capabilities, which allows developers to version their code and track changes to the application. This includes creating branches, merging changes, and rolling back changes if necessary. Pega also integrates with external version control systems like Git, SVN etc.
Deployment: Pega provides built-in deployment capabilities, which allows developers and administrators to deploy the application to different environments. This includes creating and managing deployment packages, and deploying them to different environments.
Continuous integration and delivery: Pega provides built-in integration with CI/CD tools like Jenkins, Bamboo etc. which allows developers to build, test, and deploy the application in an automated way. This can help speed up the deployment process and reduce the risk of errors.
Disaster recovery: Pega provides built-in disaster recovery capabilities, which allows administrators to backup and restore the application in case of a disaster. This includes creating and managing backup packages, and restoring them in case of a disaster.

In summary, deployment and version management in Pega projects can be handled by using a combination of environment management, version control, deployment, continuous integration and delivery and disaster recovery, using the built-in tools and integration with other tools that Pega provides.

How do you provide support and troubleshoot issues in Pega applications?

Providing support and troubleshooting issues in Pega applications involves several steps and processes to ensure that issues are identified, resolved, and prevented in the future. Here are some ways that support and troubleshooting can be handled in Pega projects:

Monitoring: Pega provides built-in monitoring capabilities that allow administrators to monitor the performance and health of the application. This includes monitoring system resources, logs, and performance metrics, as well as setting up alerts to notify administrators of potential issues.
Error tracking and logging: Pega provides built-in error tracking and logging capabilities that allow developers to track and log errors that occur in the application. This includes capturing error messages, stack traces, and other relevant information, as well as setting up alerts to notify developers of potential issues.
Root cause analysis: Pega provides built-in root cause analysis capabilities that allow developers and administrators to identify and analyze the root cause of an issue. This includes analyzing logs, performance metrics, and other relevant information to determine the cause of the issue and how to resolve it.
Resolution and prevention: Pega provides built-in resolution and prevention capabilities that allow developers and administrators to resolve and prevent issues from occurring in the future. This includes implementing solutions, such as code fixes, configuration changes, and performance optimizations, as well as creating and implementing preventative measures, such as monitoring and alerting, to prevent issues from occurring in the future.
Support ticketing and escalation: Pega also provides support ticketing and escalation process where the support team can create and manage support tickets, and escalate them to the appropriate parties as needed. This includes assigning tickets to developers, administrators, or other support team members, and tracking the status of the tickets through to resolution.

In summary, providing support and troubleshooting issues in Pega applications involves monitoring the performance and health of the application, tracking and logging errors, conducting root cause analysis, resolving and preventing issues, and creating and managing support tickets. By using the built-in tools and processes that Pega provides, it helps to ensure that issues are identified, resolved, and prevented in a timely and efficient manner.

Can you explain your experience with Pega’s different tools and utilities like Tracer, Clipboard, and so on?

Pega has a number of different tools and utilities that can be used to help develop, test, and troubleshoot applications built on the PRPC framework. Here are a few examples of some of the tools and utilities that I have experience with:

Tracer: Tracer is a debugging tool that allows developers to trace the execution of a process and view the values of variables and properties at different points in the execution. This can be useful for identifying and resolving issues related to process flow and data validation.
Clipboard: The Clipboard is a tool that allows developers to view and edit the values of variables and properties at runtime. This can be useful for troubleshooting issues related to data validation and process flow.
Work Object: Work Object is the central data structure in Pega and it can be used to store and manage data throughout the life of a case. Developers can use the Work Object to view and edit the data associated with a case and to create new cases as needed.
Rule Inspector: Rule Inspector is a tool that allows developers to view and manage the rules that make up a Pega application. This can be useful for troubleshooting issues related to rule execution and for making changes to the rules in an application.
System Management Application (SMA): SMA is a web-based tool that allows administrators to manage and monitor the performance of a Pega system. This can be useful for troubleshooting issues related to system performance and for making changes to the system configuration.
Performance profiler: Performance profiler is a tool that allows developers to identify and analyze performance bottlenecks in an application. This can be useful for troubleshooting issues related to system performance and for making changes to improve the performance of an application.
Trace Analyzer: Trace Analyzer is a tool that allows developers to analyze log files and trace information generated by Pega applications. This can be useful for troubleshooting issues related to system performance, process flow, and data validation.
Deployment Manager: Deployment Manager is a tool that allows developers to manage and deploy changes to a Pega application. This can be useful for managing the lifecycle of an application and for making changes to an application in a controlled and organized manner.

In summary, Pega provides a wide range of tools and utilities that can be used to develop, test, and troubleshoot applications built on the PRPC framework. These tools and utilities can be used to view and edit data and rules, troubleshoot performance issues, and manage the deployment of changes to an application.

Basic Interview Questions

1. Explain the concept of classes in Pega. What are the many types of classes that Pega has to offer?

Users can reuse rules across case types and apps with the Pega Platform. Developers reuse rules in their systems all the time, from single data points to entire processes. Reusing rules improves an application’s quality while simultaneously reducing development time. Pega Platform categorises rules into classes based on how easily they may be reuse inside an application. A class is the name given to each cluster. Each application consists of three different types of classes.
Work Class: The Work class contains processes, data objects, and user interfaces, as well as the rules that govern how to process a case or cases.
The Integration class contains the rules that govern how the application interacts with external services, such as the integration resources that link it to a customer database or a third-party web server.
Data Class: The Data class stores the rules that specify the data objects used in the application, such as a customer data type or order items data type.
When we add a rule in App Studio, it chooses the appropriate class for us. Instead of focusing on how to build the rule, we might concentrate on what we want it to accomplish. If you need control over the class, we can write the rule in Dev Studio.

2. In the context of Pega, what do you know about SLA in Pega Certified System Architect?

The abbreviation SLA stands for Service Level Agreement. It’s one of the Pega CRM platform’s most useful features. Service Level Agreements allow us to set targets and timetables as part of the case management process. SLA’s main objective is to help the task force complete all jobs on time. Each SLA rule’s performance of a specific event action that was set for that rule will be track by Pega Rules Process Commander. By increasing the urgency number, the assignment’s urgency is adjusted as well. Because it necessitates attention, this may call attention to the item on the employee’s to-do list. As a result, we can order the to-do list by task urgency.

3. In Pega, describe the Requestor Type in Pega Certified System Architect.

A requestor type is define by a Data-Admin-Requestor instance. For example, the BROWSER requestor type denotes interactive user connections, such as guest connections, using Internet Explorer or another web browser. Next, for background processing, agents use the BATCH requestor type.

For the system name we select during installation, Pega Platform provides four requestor types, as well as a reserved requestor type prpc.BROWSER for certain scenarios. We usually only need the four requestor kinds that have your system name in them. After installation, we head to Designer Studio => System => Settings => System Name to access a landing page tab where we can change the system name. When a system’s name is change, new requestor instances are create that correspond to the instances of the prior name. When a system is rename, if the previous name did not include all requestor types for some reason, the missing requestors are also produce.

4. In the context of Pega, explain PRPC in Pega Certified System Architect.

Pega Rules Process Commander (PRPC) is an acronym for Pega Rules Process Commander. The PRPC foundation is use by Pegasystems. It is entirely model-driven, allowing the development of reliable and efficient applications without the need for any code, including SQL, Java, CSS, or HTML. PRPC is a software platform that allows businesses to consolidate their many, complex business procedures and methodologies into a single platform. You may merge multi-stream processing into a single system by automating, documenting, and simplifying business operations.

5. Explain what you’re doing in the context of Pega in Pega Certified System Architect.

Pega Platform activities automate processes. In Dev Studio, activities are programmed as a series of steps that must be complete in the order provided. Activity rules automate the system when more appropriate rule types are unavailable, frequently due to more complex computations or procedures, or when a rule requires an activity to run. Declare When the value of a certain property changes, for example, using an activity to start a process or suspend work is require. After the activity is performed, control returns to the rule that called the action.

An insurance company, for example, is require to submit insurance claims to the Registry of Motor Vehicles. Automated uploads take performed during off-peak hours to reduce the impact on users. In Pega Platform, an activity can be design to allow the system to automate claim uploads without requiring user input.

6. In the context of Pega, explain Rule Resolution in Pega Certified System Architect.

Rule resolution is the search process use by the system to find the best or most appropriate rule instance to apply in a particular situation.

Rule resolution applies to all rule types, except a few rule types — classes that inherit from the Rule- class. Further, rule resolution has no effect on instances of classes derived from the Work-, Data-, or any other base class. Even though the rule resolution process is quick and unobtrusive, it is crucial to understand how it works. When building applications, make important component value selections base on how you want rules to be found via rule resolution. An in-memory rule cache can help speed up the rule resolution process. If the system finds an instance (or instances) of the rule in question in the cache, it accepts the candidate rules and skips many steps in the resolution process.

7. In the context of Pega, explain data pages in Pega Certified System Architect.

A data page in a Pega Platform application retrieves and caches data from a given data source. A data page manages the data source integration, separating business processes from any integration details. App developers can use supplied data in their apps without needing to know the data source or connection details because of this separation. Unlike the majority of Pega Platform pages, applications attempt to populate the contents of a data page only when the page is request, rather than through an explicit action. Since their content is provided on demand, data pages are classed as declarative rules.

8. In the context of Pega, explain Case Management in Pega Certified System Architect.

Case management is a software-based technique for assisting people with day-to-day chores and automating work processes from beginning to end. Case management comprises visualising your business process, which includes people, data, and actions, in order to map out a flexible path to your destination. We use case management to develop goal-oriented solutions by addressing business cases from beginning to end and combining human activities with digital automations.

We can, for example, mimic the process of accepting candidates after reviewing job applications, from collecting documentation from candidates to conducting job interviews to gaining final approval. You can dynamically adjust your work in case management to respond to changing conditions, as well as construct the most typical path to resolution. Your business procedure can incorporate an additional job interview if this phase is relevant to the current situation. With case management, you may successfully address business procedures that follow an ambiguous or unexpected workflow.

9. In the context of Pega, what do you mean by locking? What are the many types of locking mechanisms?

When two or more actions attempt to update the same case at the same time, the more recent action may overwrite the data written by the previous action. Data damage or loss might happen from overwrites, creating delays in case processing and possibly inaccurate case resolution. A case locking approach is essential for data integrity when an application supports several users at the same time.

To avoid data corruption or loss due to overwrites, we configure an appropriate locking strategy for each case type under Locking. Pega Platform offers two techniques for balancing the need for user access with the need for data security: pessimistic locking and optimistic locking.

10. In Pega, what is the Declare Index in Pega Certified System Architect?

Declare Index is a rule type in Pega that exposes aggregate attributes such as Page, List, and Group for reporting reasons. They are Rule-Declare-Index rule instances. It helps to populate the correct index table when an Insert/Update/Delete operation on the work object is follow by a commit. They can be discover in Records Explorer under the SysAdmin Category.

11. In Pega, how can you assess the performance of your application?

The numerous ways we can measure the performance of our application in Pega are as follows:

DBTrace: DBrace is a feature of the Performance Analysis Tool (PAL) that provides a detailed log of calls to the PegaRULES database. DBTrace displays both the time spent on each operation and the SQL queries sent to the database.
Performance Analyzer Tool (PAL): The Performance Analyzer (PAL) displays all of Pega PlatformTM’s performance statistics. You can utilise PAL to determine how much system resources are consume by a single requestor session. PAL is available on the Performance landing page (Dev Studio > System > Performance) as well as the Performance tool in the toolbar.

12. How do you tell the difference between the Page-Validate and Property-Validate methods?

The page-validate method is use to ensure that all of the properties on a page are valid. If a page has embedded pages, this method validates all of the attributes in a recursive manner. This method is time-consuming and uses a lot of system resources. Use the Obj-Validate method with a Rule-Obj-Validate rule to validate specified properties.
Property value constraints are imposed via the property-validate technique. To implement constraints, use the Edit validate rule in conjunction with the Property-Validate method. The Property-Validate method can be use to validate multiple properties.

13. What is the difference between Edit Input and Edit Validate rules?

Edit Validate: Use the edit validate rule to use java code to validate the property value. Property-validate, Rule-Obj-Validate, and Property rules can all be use to edit validate rules.
Edit Input: Edit input rules transform user-entered data into the proper format. If a user types a date in MM/DD/YYYYY format, the edit input rule converts it to DD-MM-YYYY (required format). For this transformation, we’ll need to write java code once more.

14. Where will the work objects be kept in Pega Certified System Architect?

By default, work objects are kept in the pc work table. If you want to store the work objects in a user-created table, however, follow the instructions following.
Make a schema that looks like the pc work table. (It’s advisable to duplicate the pc work schema and change the table and constraint names if necessary.)
Change the Data-Admin-DB-Table class group mapping to the newly created table.

15. What are the rules for StepStatusGood and StepStatusFail?

StepStatusGood is when the rule checks whether the value of the pxMethodStatus property is “Good” according to the condition defined in @baseclass.
StepStatusFail is a when rule that checks whether the value of the pxMethodStatus property is “Fail” as defined in the @baseclass condition.

16. Where can I see the clipboard parameter values (values, etc.) while I’m sending one activity to another?

No, you won’t be able to see it in the clipboard, but you can see it in tracer by clicking the page name in the step method column.

17. How do I use PZinsky to import rules?

Open the rule, select the pzinskey, go to prdbutil, and export the rule using the pzinskey. Import the zips file to wherever you’d like.

18. Is there a distinction between activity and utility?

The Rule-Obj-Activity rule type is an instance of an activity. The Process Commander system’s primary sequential processing unit is an activity.
In a Visio flow diagram, the shape represents an activity that changes a work object without requiring user contact or input. Standard actions for utility tasks are include in your system, and you can add new ones. With an Activity, each utility job refers to a certain activity. We can call a kind of utility ss from a utility shape activity, but not the other way around.

19. Explain the Inheritance concept in the Pega (rules, class).

Rules: inheritance that allows you to reuse your rules as much as possible while allowing for localised overriding when necessary. Inheritance, often known as polymorphism, allows a rule written for one class (perhaps an abstract class) to be applied to other classes that inherit from that class.
To identify available rules, class inheritance searches for rules from a concrete, lower class up the class hierarchy.
Directed inheritance and pattern inheritances are two types of class inheritance.

20. What is the distinction between the Page-Validate and Property-Validate methods?

The page-validate method ensures that all of the properties on a page are valid. If a page has embedded pages, this method validates all of the attributes recursively. This method is time-consuming and uses a lot of system resources. Use the Obj-Validate method with a Rule-Obj-Validate rule to validate specified properties.
Property value constraints are impose via the property-validate technique. To implement constraints, use the Edit validate rule in conjunction with the Property-Validate method. The Property-Validate method can be use to validate multiple properties.

21. Where will the work objects be kept?

By default, work objects are kept in the pc work table. If you want to store the work objects in a user-created table, however, follow the instructions following.
Make a schema that looks like the pc work table. (It’s advisable to duplicate the pc work schema and change the table and constraint names if necessary.)
Change the Data-Admin-DB-Table class group mapping to the newly created table.

22. What are the rules for StepStatusGood and StepStatusFail?

StepStatusGood is when the rule checks whether the value of the pxMethodStatus property is “Good” according to the condition defined in @baseclass.
StepStatusFail is a when rule that checks whether the value of the pxMethodStatus property is “Fail” as defined in the @baseclass condition.

23. Is there a distinction between activity and utility?

24. How are the results of our work in the Pega measure?

DBTrace: The Performance Analysis Tool (PAL) has a function called DBrace that provides a thorough log of calls to the PegaRULES database. DBTrace shows the time spent on each operation as well as the SQL queries delivered to the database.
PAL: “PAL counters” or “PAL readings” are use to store this information. Performance Analyzer (PAL) is a collection of counters and timer measurements saved in the requestor that an application developer can utilise to assess system performance concerns.

25. What is the best way to save a class instance in a database?

Creating a distinct DB table for that working-class within the database, or mapping to an external database and saving to that database.

26. How can I store the class’s instance in the database?