To adapt the display of property photos to different screen sizes within an apartment hunting

application, the best approach is:

A . Use a dynamic layout with a responsive breakpoint at 800 pixels to change from inline-grid triple

to inline-grid double format. This option uses responsive design principles to adjust the number of

columns based on screen size. When the screen width is below 800 pixels, the layout automatically

changes from three columns (triple) to two columns (double), ensuring optimal display on smaller

devices.

In the context of creating a customer loyalty account where the customer's contact information is

captured and displayed within the case, organizing and relating this data efficiently is key.

B . An Embedded data field: This option allows the contact information (name, email, phone number,

address) to be structured as part of the case data in a coherent and integrated manner. Embedding

this information ensures it is directly associated with each loyalty account case, facilitating data

management and access within the application's data model.

A Data reference field (A) links to data instances outside the case, which is not the primary

requirement here. A Case reference field (C) is used for linking cases together, which does not apply

to this scenario of capturing contact information. A Query field (D) is intended for retrieving data

based on a query, which is not relevant for directly embedding and displaying entered contact

information within a case.

Reference: Pega's platform documentation details the use of Embedded data fields to structure

related data within cases, highlighting their role in efficiently organizing and managing case-specific

information in a structured format.

Understanding data objects in Pega helps clarify their roles and functions within the platform:

A . Data objects can reuse assets from an existing data object through inheritance. Inheritance allows

data objects to extend the properties and behaviors of existing data objects, promoting reusability

and consistency across the application.

C . A data object created in App Studio creates a data type in Dev Studio. This statement is true as

creating a data object in App Studio automatically sets up a corresponding data type in Dev Studio,

ensuring that the data structure is available across both development environments for further

customization and integration.

In the context of assigning components to a Minimum Lovable Product (MLP) release for project

sizing in Pega’s Case Designer, the components typically considered include:

A . An automation. Automations are discrete components that can significantly enhance the

functionality of an application, making them a key feature to include in an MLP for delivering

immediate value to users.

C . An approval decision. Approval decisions are critical elements in many workflows and can directly

impact the user experience and the efficiency of process handling, making them suitable for

inclusion in an MLP release to demonstrate immediate benefits and functionality.

Adding an external data source to a data object in Pega requires specific details to ensure proper

integration and functionality:

A . The authenticating information, if required by the corresponding service. Secure access to

external data services often requires authentication details, such as API keys or login credentials, to

ensure that interactions are authorized.

D . The uniform resource identifier that identifies the web service. The URI is crucial as it specifies the

exact location and endpoint of the web service from which data is to be fetched, acting as a link

between the Pega application and the external data source.

To fulfill the requirement that all managers must be able to view the Employee vacation requests

report in their Manager portal dashboards, the report must be made readily accessible in a manner

that integrates seamlessly with the existing portal structure.

D . Add the report to a public category, and then add the out-of-the-box Reports landing page to the

portal: This approach ensures broad accessibility by placing the report within a public category,

making it available to all managers. Integrating the Reports landing page into the portal provides a

centralized location for managers to access this and potentially other relevant reports directly from

their dashboard, enhancing the usability and efficiency of the portal.

Creating a new landing page (A) specifically for the new report may not be necessary if the existing

Reports landing page structure can accommodate the report, and it may introduce unnecessary

complexity. Adding a report widget and publishing it to the default (B) or without specifying the

target audience (C) might not ensure the report's visibility to all managers as required.

Reference: Pega's reporting and dashboard configuration documentation outlines methods for

making reports accessible within user portals, emphasizing best practices for report categorization

and portal integration to support effective information dissemination.

Top of Form

Configuring a mobile app channel in Pega allows for several adjustments specific to mobile

applications:

C . Establish security behavior for a mobile app, such as the use of biometric identifiers. Security

configurations such as biometric access are crucial for mobile apps to ensure data protection and

user authentication on mobile devices.

D . Define UI behavior for a view when displayed on a mobile device. Customizing the UI behavior

depending on device type or screen size is essential for optimal user experience on various mobile

platforms.

E . Define the role applied to users when they run the mobile app. Setting user roles within the app

ensures that permissions and functionalities are correctly aligned with the user's needs and

authorization levels.

Customer information: This usually pertains to session-specific data that is relevant to the current user, such as user ID and locale. In Pega, this type of information is typically stored in user pages, which are clipboard pages that contain data related to the current user of the application. User pages are created for each session and include data that pertains to that particular user. Previous orders: These are typically a list of orders that are not specific to a session but need to be readily accessible and possibly shared across multiple sessions or users. In Pega, this kind of information is best stored in data pages. Data pages are used to hold data that is loaded once and can be used by multiple users, cases, or processes. They are efficient for data that doesn't change often and is required to be accessed frequently, such as a list of previous orders. Current order: This refers to the specific details of the order the customer is currently placing. It is specific to the user's current session and the case they are working on. Therefore, it should be stored in user pages, which are specific to an individual user session and can manage data related to the work they are currently performing.

Reference: Pega's official documentation on Clipboard and Clipboard pages explains how data is categorized and managed within the application. Training materials from Pega Academy, which go into detail on the types of clipboard pages and their uses within a Pega application.

UI object that represents the combination of data and a template. - Template Preassembled view with a preset template and data requirements. - View Automatically generated view that represents a single case in Pega Platform. - Full case view Generic rendering structure that presents data with visual style and interaction behavior. - Widget Comprehensive Detailed Explanation with Reference: The four descriptions provided relate to elements within the Pega Platform, specifically tailored for the Constellation UI architecture, which is focused on delivering a responsive and user-friendly interface for applications. Template: In Pega, a template refers to a predefined format for presenting dat a. It specifies the layout and structure used to display information. A UI object that combines data and a template can be seen as the blueprint from which UI elements are generated, ensuring consistency and adherence to design standards. View: A view in Pega is a configuration that determines how data is displayed in the UI. It's a preassembled component that combines a specific template with data requirements, thus simplifying the creation of user interfaces by allowing developers to reuse common patterns and layouts with different sets of data. Full case view: This refers to a holistic view of a case in Pega, showing all relevant information and actions that can be taken. It is generated automatically by the platform to represent all the aspects of a case, providing a comprehensive interface for users to interact with case data and perform necessary tasks. Widget: Widgets in Pega are generic, reusable UI components that display data and offer interactive behavior. These can range from simple data fields to complex graphical components. They are styled and have behaviors that allow users to interact with the data presented, such as drop-down menus, charts, or data grids.

Reference: Pega Community articles and documentation provide insights into these concepts. Specifically, you can refer to Pega Community resources for understanding the Constellation UI architecture and the role each component plays within it. Pega Platform Help files, which can be accessed directly through the Pega Platform, offer detailed explanations and guidelines for creating and using templates, views, full case views, and widgets.