An internet provider has a quiz that gives customers a recommended internet speed based on their typical internet use. The questions differ based on the selections that the customer makes, for example, whether they are seeking a recommendation for a residence or a business. Once the customer completes the quiz, how do you determine the recommended internet speed?
Answer(s): A
For an internet provider's quiz designed to recommend internet speeds based on varying customer usage profiles, including differentiating between residential and business needs, employing a decision mechanism that efficiently handles multiple input factors is key. A . Configure a decision table: Decision tables are ideal for scenarios where the output (recommended internet speed) depends on multiple conditions (quiz answers about internet use). They offer a clear, concise way to map various combinations of inputs to their corresponding outputs, making it easy to update and manage as new conditions or outcomes are introduced. This configuration supports dynamic and nuanced decision-making based on customer responses. Configuring a view with quiz questions (B) is necessary for collecting inputs but does not determine the outcome. A decision tree (C) could also be used but might become complex with multiple branching conditions. A process with multiple decision shapes (D) could handle the logic but may be less efficient and harder to maintain than a decision table.
Pega's decision management tools, including decision tables, provide a structured approach to making rule-based decisions based on multiple input conditions, as outlined in Pega's official documentation on decision rules.
An on-demand transportation application has a Conversation preference data type. When customers use the application to request a ride, they can specify their conversation pReference: whether they would like to talk to their driver or if they would prefer silence. Company stakeholders are interested in analyzing the conversation preference data.How is the Conversation preference data type sourced?
Answer(s): B
For an on-demand transportation application collecting conversation preferences from customers, the nature of the data--preferences stated during the booking process--suggests it is generated dynamically rather than stored in a pre-existing database. B . No system of record: This option acknowledges that conversation preferences are specified by customers in real-time and are specific to each ride request, rather than being pulled from a pre- established database (local or external). The data is generated by user input within the application itself and used for analysis without necessitating a traditional system of record for storage. A local system of record (A) refers to data stored within the application's database but is more relevant for static or semi-static data rather than dynamic preferences. An external system of record (C) is used for data that the application retrieves from outside sources, which does not
whether they would like to talk to their driver or if they would prefer silence. Company stakeholders are interested in analyzing the conversation preference data.How is the Conversation preference data type sourced?A. Local system of recordB. No system of recordC. External system of recordAnswer(s): B
An online retailer allows customers to select a courier service for deliveries. The list of available courier services is drawn from a data type sourced in the Pega database. The Fulfillment department wants to allow local warehouse managers to add courier services to mitigate increases in delivery times and remove courier services that fail to meet delivery metrics. Which two options are required to allow local warehouse managers to update courier service records in production? (Choose two.)
Answer(s): B,C
To enable local warehouse managers to dynamically update the list of courier services based on performance and delivery metrics directly in the production environment, specific functionalities need to be leveraged within Pega.B . Delegate the records for the courier service data type: Delegation is a powerful feature in Pega that allows certain data types or rules to be managed by business users directly in production. By delegating the courier service data type, local warehouse managers can add or remove courier services as needed without requiring changes to the application code or direct database access. C . Define an approval process for adding and removing courier services: Implementing an approval process ensures that changes to courier services undergo review before becoming effective. This step maintains data integrity and service quality by ensuring only justified updates are made to the list of courier services.Creating an access group for local warehouse managers (A) is a necessary step for defining user permissions but on its own does not specifically enable the updating of courier service records. Enabling rule checkout (D) is more related to the development environment and rule versioning, not directly applicable to the business user's management of data records in production.
Pega's official documentation on data delegation and workflow configuration provides insights into enabling business users to manage specific types of data directly and securely, including the setup of approval processes for such changes.
An online sales application supports both laptop and mobile devices. You are configuring the application skin and you notice the responsive layout in the mobile device is not displaying views as stakeholders require.Which two options allow you to resolve this situation without negatively impacting the laptop users? (Choose two.)
Answer(s): A,D
When configuring an application skin to ensure responsive layouts are displaying correctly across different devices, such as laptops and mobile devices, without impacting the user experience negatively for laptop users, careful adjustments to the skin and its responsive settings are required. A . Use the same application skin in all portals: Utilizing a single application skin across all portals ensures consistency in branding and design. The same skin can be configured to adapt responsively to various screen sizes, ensuring a seamless user experience across devices. D . Adjust the responsive behavior in the skin for optimal viewing in the mobile portal: The skin's responsive behavior settings allow for adjustments specific to how UI elements are rendered on different screen sizes. By fine-tuning these settings, the application can ensure that views are displayed as required on mobile devices without affecting the layout on larger screens, like laptops. Updating the process to give mobile users a separate portal (B) could be an approach but might introduce complexity and maintenance overhead, as well as potentially fragment the user experience. Not using a skin for the mobile application version (C) is not advisable as it disregards the benefits of a unified and controlled UI design across devices.
Pega's documentation on skin configuration and responsive UI design principles highlights how to manage and adjust application skins to accommodate various display requirements, ensuring a consistent and effective user experience across device types.
An online shopping application allows customers to select the item quantity of different goods and add items to the shopping cart. In the shopping cart, the application displays the price for each item type, indicates the quantity of each item type, calculate the total item prices, and calculate the total cost for all items in the shopping cart. The application pulls the price of each item type from a data page that references an external inventory management system. Select two unit tests useful in developing the shopping cart page. (Choose Two)
For an online shopping application, ensuring accurate item pricing and total cost calculations in the shopping cart is crucial for functionality and user trust. Unit testing focused on verifying these aspects is essential during development.A . Verify the data page has the correct item prices: This test ensures that the prices pulled from the external inventory management system into the application via the data page are accurate. Correct item pricing is foundational to calculating the total cost for items in the shopping cart. D . Verify the order total cost property is accurately calculated: This test checks whether the application correctly calculates the total cost of all items in the shopping cart, considering both the individual item prices and their quantities. Accurate total cost calculation is crucial for the final order summary and checkout process.Verifying the data transform copies the correct value (B) is important for data integrity but is a more granular detail compared to the overarching need to ensure accurate pricing and total calculations. Verifying the price fields are displayed in the correct format (C) is also significant but focuses more on UI presentation than on the underlying functional correctness of pricing and total cost calculations.
Unit testing best practices in application development emphasize the importance of verifying core functionalities, such as accurate data retrieval and calculations, to ensure the application operates correctly and provides a reliable user experience, as outlined in Pega's development documentation.
An order form provides four options from which customers select one option. According to best practice, which of the following two UI control types can be used to minimize clutter on the order form? (Choose Two)
Answer(s): A,C
To minimize clutter on an order form where customers select one option out of four, using UI controls that efficiently manage screen real estate while ensuring user-friendliness is crucial. A . Dropdown: A dropdown menu consolidates the four options into a single interactive element. When not in use, it takes up minimal space on the form, contributing to a cleaner, less cluttered appearance. It expands when interacted with, allowing the user to make a selection from the list. C . Radio buttons: Radio buttons allow all options to be visible at once, ensuring immediate visibility of choices without additional interaction. Because selecting one option automatically deselects any other, radio buttons are ideal for single-choice scenarios. They can be designed to be compact, minimizing their impact on the form's layout.Checkboxes (B) are typically used for selections where multiple options can be chosen simultaneously, which does not align with the requirement for a single selection. Autocomplete (D) is useful for forms with a large number of options or for facilitating quick selection from a list through typing, which might not be necessary or as efficient for a small, fixed set of four options.
Best practices in UI design suggest dropdowns and radio buttons for single-choice scenarios to balance clarity and economy of screen space, as detailed in UI design guidelines and Pega's documentation on form design principles.
An order fulfillment case type allows a customer to update user profile information during the order placement stage. The user profile consists of the following three pages:Account ID and password Customer contact information A list of open orders with the status of each order.How do you configure the case type to allow customers to update any of the user profile pages at any time during case processing?
Answer(s): D
To enable customers to update any of the user profile pages (Account ID and password, Customer contact information, A list of open orders with the status of each order) at any time during case processing in an order fulfillment case type, flexibility and accessibility are key. D . Add a set of optional actions to the case workflow: Optional actions provide a mechanism for incorporating activities that can be initiated by the user at their discretion, outside the primary progression of the case. By defining optional actions for updating each area of the user profile, customers are afforded the flexibility to make updates whenever necessary throughout the case lifecycle, without being constrained to specific stages or assignments.Adding an optional process (A) could introduce the functionality but might be less direct than optional actions for specific updates. Adding a button for each profile page to each assignment (B) might unnecessarily complicate each assignment's UI. An alternate stage (C) typically represents a divergent path in the case lifecycle for handling exceptions or additional processes and might not provide the anytime accessibility characteristic of optional actions.
Pega's case management documentation outlines the use of optional actions within case workflows to enhance user flexibility and case adaptability, supporting a wide range of user-initiated activities throughout the case lifecycle.
An organization has two lines of business: selling books for children and reselling college textbooks. The division selling books for children can use the same basic user interface (Ul) as the division reselling textbooks with the exception of the payment methods. How do you apply the Situational Layer CakeTM in this scenario ?
In a scenario where an organization operates two lines of business with similar UI needs but differing payment methods, applying the Situational Layer CakeTM concept allows for efficient reuse of common functionalities while accommodating specific differences. B . Place the UI rules and generic payment method rules in the base layer, and create a new layer for the division-specific payment rules: This approach maximizes reuse by placing the shared UI components and any generic payment functionalities that apply to both divisions in the base layer of the application. Division-specific payment methods are then managed in separate layers on top of the base layer, allowing for tailored handling of payment options without duplicating the common UI elements.Option A suggests a new layer for both lines of business, which might not efficiently leverage the commonalities between them. Creating a parallel base layer for payment rules (C) deviates from the hierarchical structure intended by the Situational Layer CakeTM. Option D, creating a new layer for each division's payment rule, aligns with option B but is less clearly articulated regarding the placement of shared UI rules.
The Situational Layer CakeTM is a Pega concept for organizing application layers to support efficient reuse and specialization. Placing shared resources in the base layer with specialized configurations in higher layers supports scalable and maintainable application design, as outlined in Pega's development best practices.
Post your Comments and Discuss Pegasystems PEGACPSA23V1 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PEGACPSA23V1 content, but please register or login to continue.