Using the information shown in the case structure below, which option is always true?
To determine which option is always true based on the case structure, let's analyze each option:
A . Resolution of the Event Booking case requires the Parking case to be resolved.
This may not always be true unless explicitly defined in the case dependencies or resolution conditions within the application.
B . Parking, Weather, and Hotel cases must be instantiated for the Event case to process correctly.
This is not necessarily true unless the Event Booking case is designed to always require these sub-cases.
C . The Weather case can be instantiated without a parent Event Booking case.
This is always true as sub-cases can typically be instantiated independently of their parent cases. The Weather case can be a standalone case type or instantiated through other means.
D . The Parking class must inherit from the Event Booking class.
This is not always true as class inheritance depends on the application design and how classes are structured in the hierarchy.
Based on this analysis, the verified answer is:
C . The Weather case can be instantiated without a parent Event Booking case.
Pega Documentation on Case Types: Case Types
Pega Documentation on Sub-Cases: Sub-Cases
Security policies need to be configured for a newly developed Pega application using basic credential authentication. The lockout policy configuration must lock out users after three failed login attempts. The configuration must exclude Administrator or Executive operators from the lockout.
How do you achieve this requirement?
The Exclude Operators option in the Security Policies landing page allows administrators to specify certain operators, such as Admin or Executive roles, who should be exempt from the lockout policy. This ensures that critical users retain access even after multiple failed login attempts, aligning with the requirement to exclude specific roles from lockout policies.
Pega Security Policies: Configuring Security Policies
Pega Authentication: Authentication and Access Control
APP Studio created a data type in the Organization layer for Quote data called BCO-Data-Quote. How do you help users find rules from this data class when working in APP Studio?
To help users find rules from the BCO-Data-Quote class when working in APP Studio, you should:
Relevant Records Configuration: Mark each rule you want to reuse as a relevant record. This makes these rules easily discoverable and reusable within APP Studio.
Implementation in APP Studio: Navigate to the data type and mark the necessary rules as relevant records. This action ensures that these rules are available in the relevant contexts when users work within the application.
Using relevant records in App Studio
BigCo receives complaints from existing customers and new prospects that BigCo representatives contact them with irrelevant offers and products.
Which two Pega solutions do you suggest to help solve this problem? (Choose Two)
To address the complaints from customers and prospects about receiving irrelevant offers and products, the following two Pega solutions can be implemented:
Pega Marketing: This solution helps in creating personalized marketing campaigns. By leveraging predictive analytics and customer data, it ensures that the marketing efforts are relevant and targeted. This reduces the chances of customers receiving irrelevant offers.
Customer Decision Hub: This hub centralizes the decision-making process by using real-time data and analytics to personalize interactions with customers. It helps in understanding customer needs and preferences better, thus preventing the delivery of irrelevant offers.
Pega Marketing Overview
Customer Decision Hub
APP Studio created a data type in the Organization layer for Quote data called BCO-Data Quote. How do you help users find rules from this data class when working in APP Studio?
To help users find rules from the BCO-Data-Quote class when working in APP Studio, follow these steps:
Relevant Records: By selecting each rule you want to reuse as a relevant record, you make these rules available and easily accessible in APP Studio.
Configuration: In the application, configure the data type and select the necessary rules as relevant records, ensuring that these rules are visible and usable in the required contexts.
Using relevant records in App Studio
