For offline support, it's necessary to have the access groups configured to allow offline access to

users so that the correct rules and data can be synchronized to the user's device. In addition, the case

types must be configured to function properly in an offline environment, ensuring that users can

create, update, and submit cases without a network connection. Reference: Pega Mobile Client

Developer Guide.

Reference: https://community.pega.com/knowledgebase/articles/configuring-offline-capabilitymobile- application

A: The Application Guardrails landing page does count the number of rules with severe or moderate

warnings, as these can have a significant impact on the application's performance and

maintainability.

B: Guardrail scores exclude Pega Platform core rules since these are established by Pega and are

assumed to be optimized.

C: The landing page also counts the number of rules with no warnings or caution-level warnings,

which contribute positively to the overall compliance score. Reference: Pega official documentation

on the Application Guardrails landing page and guardrail scores.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/PEGA_PEGACPSSA23V1/page_11_img_2.jpg

Reference: https://community.pega.com/knowledgebase/articles/pega-web-mashup/pega-webmashup

Pega Web Mashups enable the embedding of Pega applications within external web pages. A

mashup is initialized by calling a flow or a harness from a Pega application, allowing users to interact

with Pega case management from other applications or portals. Users can also view their worklist in

the external portal and select items to take action on, extending the capabilities of Pega applications

to external platforms. Reference: Pega Platform Help - Pega Web Mashup.

To resolve performance issues caused by resource-intensive queue processors, it's essential to

ensure that these processors are associated with appropriate node types (A) and that application

nodes are configured with node types (D). Associating queue processors with specific node types

allows for the distribution of workload across the application infrastructure, optimizing resource

utilization and improving performance. Configuring application nodes with node types ensures that

tasks are executed on the most suitable nodes, further enhancing system efficiency and scalability.

Reference: Pega Community documentation on queue processors and node types.

The purpose of the Policy Verification landing page in Pega Platform is to test if a user has the

required access to a case (A). This tool allows administrators and developers to verify access control

policies by simulating how the policies would apply to different users, ensuring that the security

configurations align with the application's requirements and that users have appropriate access

levels to cases and data.

Reference: Pega Community documentation on security policies and Policy Verification tool.

The Static Assembler is a Pega tool used to address rules assembly issues specifically when the server

is managing a large number of rules caches. By pre-assembling rules into a static content, the Static

Assembler helps in improving performance in situations where cache management becomes

complex due to the volume of rules. It creates a set of static files that represents the assembled

rules, which can reduce the overhead on the server during rule assembly and cache management.

Reference: Pega official documentation on performance tools and best practices.

To start operations at a specific GMT time regardless of where the server is located, you would use

the Queue-For-Processing method in an activity. This method adds a task to a queue to be processed

either by a standard or a dedicated queue processor. A dedicated queue processor can be configured

to operate on a schedule, so it can start processing at midnight GMT. Reference: Pega SSA course

materials on queue processors and timed events.

You should consider using a field value when the list of allowed values is mostly static. Field values

are best used for properties with values that do not change often and need to be reused throughout

the application. Reference: Pega official documentation on field values.

A: When using a Pega Web Mashup, leveraging the standard authentication service

IACAuthentication and updating the authentication activities to match the external system's

requirements is a common practice.

D: Configuring application permissions by specifying a list of trusted domains in the application rule

is important for security purposes and to control which external domains are allowed to embed the

mashup. Reference: Pega official documentation on Pega Web Mashup configuration.