PEGACPSA23V1 Exam Dumps : Certified Pega System Architect

To allow operators from two separate units to perform work routed to either unit:

B. On each operator's record, associate the operator with the same workgroup. Associating all operators with the same workgroup, regardless of their unit, allows them to access and perform work routed to the workgroup. This configuration ensures that work can be shared across units within the same group, facilitating collaboration and flexibility in work distribution.

When a service level's goal interval lapses and the urgency is adjusted to 100:

B. Urgency value continues to increment as configured. In Pega, urgency levels can continue to increase based on additional factors configured within the service level. This includes the urgency escalation that may occur at the deadline and passed deadline intervals. The adjustment to 100 does not cap the urgency; instead, it sets a new baseline from which further increments may occur as defined by the service level settings.

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.