Practice Free PEGACPLSA88V1 Exam Online Questions
Which two statements are true of Kubemetes capabilities? (Choose Two)
- A . They can orchestrate JVM garbage collection.
- B . They can orchestrate database re-indexing.
- C . They can auto scale pods up and down.
- D . They can orchestrate pods and their dependencies.
C, D
Explanation:
Kubernetes is a powerful orchestration platform for managing containerized applications across a cluster of machines. The two statements that are true about Kubernetes capabilities are: Auto Scaling Pods Up and Down (C):
Kubernetes can automatically scale the number of pods up or down based on the resource usage and
demand. This is done using the Horizontal Pod Autoscaler, which adjusts the number of pod replicas
based on CPU utilization or other select metrics.
Orchestrate Pods and Their Dependencies (D):
Kubernetes orchestrates the deployment, scaling, and operations of application containers across clusters of hosts. It manages the scheduling of pods, ensuring that containerized applications are running as desired and can handle the orchestration of dependencies between containers.
Reference: Kubernetes Documentation on Horizontal Pod Autoscaler Kubernetes Documentation on Pod Lifecycle
An e-commerce application offers special discounts on a seasonal basis. A business manager is authorized to maintain these discounts.
Which of the following options is the best possible solution for maintaining the discounts?
- A . Create a case that performs the data updates.
- B . Use a list landing page without the default data sources.
- C . Provide a Harness to update the discount details.
- D . Use a list landing page and define the default data sources.
D
Explanation:
The best solution for maintaining discounts in an e-commerce application by a business manager is:
List Landing Page with Default Data Sources (D):
A list landing page provides an intuitive interface for business users to view, manage, and update discount details. By defining default data sources, the data is automatically fetched and displayed, simplifying the maintenance process.
This approach ensures that business managers can easily access and modify discount information without needing deep technical knowledge.
Reference: Pega Platform Help on Configuring Landing Pages
You add database connection information to prconfig.xml and want to encrypt the password in the connection information how do you encrypt the password?
- A . create an encrypted keyring password and replace the unencypted password in prconfig.xml
- B . enter a password in an application ID instance and reference the external system
- C . create an encrypted password with PR cipherGenerator and reference the external system
- D . create an encrypted password with passGen and replace the unencrypted password in pconfig.xml
C
Explanation:
Use PR cipherGenerator:
Utilize the PR cipherGenerator tool to generate an encrypted password. This can be done through Pega’s utility tools or via command line. Encrypt Password:
Replace the unencrypted password in the prconfig.xml file with the generated encrypted password.
Configuration:
Ensure that the encrypted password is correctly referenced in the connection information within
prconfig.xml.
Reference: Pega Academy: Configuration and Deployment.
Pega Documentation: Encrypting Passwords and PR cipherGenerator.
The SLA and the customer’s system administrator are reviewing scenarios that do not require an application server restart.
Select three scenarios from this list. (choose three)
- A . When deploying rule only hotflxes
- B . When changing the prweb web.xml file
- C . When changing the system name
- D . When the deploying new rules
- E . When the prlogging.xml file is modified
A, D, E
Explanation:
Certain scenarios do not require an application server restart:
When deploying rule only hotfixes (Answer A):
Rule-only hotfixes update rules in the application without requiring a full server restart, allowing changes to take effect immediately.
Reference: Pega hotfix installation documentation confirms that rule-only hotfixes do not necessitate a server restart.
When deploying new rules (Answer D):
New rules can be deployed and become active without needing to restart the application server, enabling dynamic changes.
Reference: Pega’s rule deployment process supports making changes on-the-fly without server restarts.
When the prlogging.xml file is modified (Answer E):
Changes to the logging configuration file (prlogging.xml) typically do not require a server restart to take effect.
Reference: Pega documentation on logging configuration indicates that prlogging.xml changes are picked up without a server restart.
Your application is deployed to the cloud. A data source outside your application populates a data page by using your data access pattern configuration. You receive complaints that the system takes a long time to fetch data each time the case worker accesses information for a different customer.
Which approach solves this performance issue?
- A . Move to local installation because network traffic in cloud deployment is often slow.
- B . Change snapshot data access method to reference pattern data access method.
- C . Fetch only the targeted data from the database each time data is needed so access is faster.
- D . Access data page with a predefined key so that, once loaded, data access is faster.
D
Explanation:
To improve performance when fetching data from an external source in a cloud-deployed application, you should configure the data page to use a predefined key. This approach allows the data to be loaded once and then accessed quickly for subsequent requests. Understanding Data Pages in Pega:
Data pages in Pega are used to cache data, so it doesn’t have to be retrieved from the source every time it is needed. Using a predefined key means that the data page is loaded with specific data that can be reused.
Configuring Data Pages with Predefined Keys:
Step 1: Define a data page and configure it to use a key for accessing data.
Step 2: Ensure the data page is set to load on demand or at a specific point in the process.
Step 3: Once the data is loaded with the predefined key, subsequent accesses to this data page will be faster because the data is already available in the cache. Advantages of Using Predefined Keys:
This approach reduces the need to repeatedly fetch data from the external source, thereby improving performance and reducing network latency issues in cloud environments.
Reference: Pega Documentation on Data Pages and best practices for caching and data retrieval provides detailed steps and examples on how to configure data pages with predefined keys for optimized performance.
A Customer Service application requires customer data assembled from multiple external systems. The customer data is captured by a parent case. Subcases of that parent case need to reference the same customer data.The customer data must be as current as possible.
Which two options are used as part of the solution? (Choose Two)
- A . Have each subcase load a portion of the customer data prior to updating the parent case.
- B . Use the Snapshot data access pattern to capture the customer data prior to subcase spin off.
- C . Load the customer data in parallel using the Load -Data Page and Connect-Wair methods.
- D . Use the System of Record (SOR) data access pattern when capturing the customer data.
C, D
Explanation:
When designing a solution that requires customer data from multiple external systems and ensuring it is as current as possible, consider the following:
Parallel Data Loading: Use the Load-Data Page and Connect-Wait methods to load the data in parallel. This approach improves performance by reducing the time taken to gather the required customer data since multiple data sources are queried simultaneously.
System of Record (SOR) Pattern: Employ the System of Record (SOR) data access pattern to fetch the most current customer data from the external systems directly. This ensures that the data used is up-to-date and reflects the latest information available from the source systems.
Reference: Pega Platform documentation on data pages, Connect-Wait methods, and data access patterns.
As a part of the DevOps release pipeline, the Center of Excellence team enforced the development teams to use scenario testing to create Ul-based, end-to-end scenarios to test the applications.
Which three of the following statements are true about scenario testing? (Choose Three)
- A . Scenario tests can include another scenario test.
- B . Scenario tests do not support the setup or cleanup of test data.
- C . Scenario tests do not support file uploads or downloads as a part of the test execution.
- D . Scenario tests cannot include another scenario test.
- E . Scenario tests support the setup or cleanup of test data.
A, C, E
Explanation:
Scenario testing in Pega is used to create UI-based, end-to-end tests for applications. The following statements are true about scenario testing:
Scenario Tests Can Include Another Scenario Test (A):
Scenario tests can be nested, allowing one scenario test to include another. This enables the reuse of common test steps and enhances the modularity of test cases. Scenario Tests Do Not Support File Uploads or Downloads (C):
Scenario tests are designed to simulate user interactions but do not support file uploads or downloads as part of the test execution. This limitation ensures tests focus on UI interactions and business logic.
Scenario Tests Support the Setup or Cleanup of Test Data (E):
Scenario tests allow for the setup or cleanup of test data before or after the test execution. This capability ensures that the test environment is correctly prepared and that any test data is appropriately managed.
Reference: Pega Scenario Testing Guide
Pega Platform Test Automation Documentation
DRAG DROP
The following figure depicts a hierarchy of applications that are built on other applications. Specifically, the productionapp application is built on applications customerapp and employeeapp. Each of these applications has additional built-on applications, including the duplicated MYEnterpriseApp application, which has two different versions in use.
All applications are built on the same version of PegaRUUS.
CustomerApp 07.01
ServiceApp 01.01
EmployeeApp 01.01
MyEnterpriseApp 01.02
PegaRULES 07.10
An application is being constructed In multiple phases for a growing company that has over 1000 employees. During the initial development stages, it is determined a button on a section has to be made conditionally visible based on a group of actors.
What should the conditional visibility be based on to minimize the amount of future maintenance?
- A . Privilege
- B . AccessGroup
- C . Role
- D . Work group
B
Explanation:
Using AccessGroup for conditional visibility is optimal because AccessGroups manage the user’s access to different applications and features. This approach provides flexibility and ease of maintenance, allowing changes to user roles or permissions to be managed centrally without modifying individual rules. AccessGroups encapsulate roles, privileges, and access controls, making it simpler to control UI elements based on user groups.
Reference: Pega Security: Access Group Configuration
Pega UI Authoring: Conditional Visibility
You need to create custom workspaces for the manager and for the Customer service representative (CSR), Also, you are asked to display some properties in custom formats that arc not supported by Pega.
Which approach satisfies these requirements?
- A . Each access group can use separate portals, harnesses, and sections. Use Specialty Components and use XML to pass data.
- B . Level age the Case Manager and Case Worker as reference points to create new portals, if required. Use Special Components and use JSON to pass data.
- C . Create different harnesses for each user’s workspace. New portal rules are not needed. Define Specialty Components and use JSON to pass data.
- D . Identify the functionality required for each portal. Customize the portal either by modifying the section or harness. Use Specialty Components and use XML to pass data.
A
Explanation:
To create custom workspaces for different user roles and display custom formatted properties: Separate Portals and Harnesses: Define separate portals, harnesses, and sections for each access group (managers and customer service representatives). This approach allows you to tailor the user interface and functionality according to the specific needs of each role.
Specialty Components and XML: Use Specialty Components to create custom formats for properties.
XML can be used to pass data in and out of these components, allowing for complex and specialized data handling.
Reference: Pega Platform documentation on portals, harnesses, and using Specialty Components with XML.