Pegasystems PEGACPSA23V1 - Certified Pega System Architect

When transitioning from planning to development, populating the backlog with work items that clearly articulate business requirements and enhancement requests is key. User stories are well-suited for capturing these needs in an Agile development environment.

C. Create stories: User stories are a fundamental element in Agile methodologies, used to describe features, functionalities, or enhancements from the perspective of the end user. They are concise yet comprehensive, detailing what needs to be done and why. For the scenarios mentioned — grouping steps into a multistep form as a future enhancement, and addressing a missing option in a dropdown list — creating user stories allows these requirements to be clearly defined and prioritized in the backlog.

Importing stories (A) might be a method to bulk add pre-defined stories from external sources but does not pertain to the action of creating new stories based on the spreadsheet contents. Creating bugs (B) is more appropriate for issues or errors that need to be fixed, not for new development work or enhancements. Creating feedback (D) could capture suggestions or comments but lacks the structured format of user stories for development purposes.

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.

Creating a new rule in Pega Platform is appropriate when a specific behavior or functionality not provided by out-of-the-box features is needed. In this case, a developer creating a parallel process to audit changes made by a service agent requires a new rule. This rule will handle the logic and flow for tracking and documenting changes in a separate process, ensuring that the audit trail is maintained without affecting the primary case processing, aligning with best practices for maintaining system integrity and traceability.

To pause case processing after the Client Intake stage and provide a timeframe for clients to upload recordings:

A. Configure a case-wide optional action to allow uploads. Add a Wait shape with a Timer Wait type set to 72 hours. This configuration meets the requirement by allowing an optional action for clients to upload their recordings and then using a Wait shape to pause the case. The Timer Wait type ensures that the case will not proceed to the Client Consultation stage until 72 hours have passed, giving clients ample time for uploads.

To design the case so that the Item Return stage is skipped if the item will not be returned, the best approach is:

B. Add a condition to skip the Item Return stage when a return is not necessary. This configuration involves setting a condition at the beginning of the Item Return stage or prior stages, determining whether the return is necessary based on case data (e.g., a property indicating item condition or customer decision). If the condition evaluates to true (no return needed), the process skips the Item Return stage and proceeds to the next appropriate stage.

To ensure that hospital staff can efficiently provide patients with a summary of their visit, the system needs to generate a document (PDF) and then email it. Configuring a "Create PDF" automation that references the detailed Patient visit summary view allows for the automatic generation of a comprehensive document containing all relevant visit details. Following this, adding a "Send Email" step with the capability to include attachments enables the system to attach the newly created PDF to the email sent to the patient. This combination ensures a streamlined process for distributing important healthcare information securely and efficiently.

The Tracer tool in Pega is used for debugging and provides real-time diagnostics of rule execution. It can trace various events, including:

C. Data transforms. Tracer can be used to trace the execution of data transforms, which are rules that define how data is set or copied from one or more sources to a target.

D. Service-level agreements. The tool can also trace the execution of service-level agreements (SLAs) to ensure that they are triggered and actioned as configured, particularly useful for understanding and troubleshooting the timing and escalation actions within case processing.

While Tracer is a powerful tool for rule execution diagnostics, it is not typically used for tracing user authentication events directly; other logging and auditing mechanisms would generally handle that. Data sources are usually traced through the use of the Data Page debugging tools rather than the Tracer, although the Tracer can show the execution of rules that interact with data sources.

Delegation is used in Pega to enable business users to manage specific business rules or parameters directly. It addresses:

B. A risk officer wants to adjust the income threshold for automobile loans. This requirement is ideal for delegation as it involves a business parameter (income threshold) that may need frequent adjustments based on market conditions or internal policies. Delegating this allows the risk officer to make adjustments independently without requiring changes through IT or development teams.

When designing a mobile app, it's important to consider how users interact with the device and how the app will be presented across different devices:

B. Test applications in the mobile preview. Using the mobile preview feature allows designers to test how the application will look and operate on mobile devices, ensuring usability and optimal user experience.

C. Design for finger taps. Mobile interfaces should be designed for touch interaction, with controls that are sized and spaced to accommodate finger taps, which is the primary mode of interaction on mobile devices.

Configuring a mobile channel in App Studio supports various features that enhance the user experience and application security on mobile devices:

C. Configure a left swipe behavior to open a message. This use case is supported by configuring gesture-based interactions in a mobile app, allowing users to use swipe gestures to access functionalities like opening messages, which enhances usability and interaction in the mobile environment.

D. Lock the application after 20 minutes of inactivity. Setting security features such as automatic locking after a period of inactivity is crucial for maintaining security on mobile devices, protecting sensitive data from unauthorized access.