A report contains columns for Customer, Billing Cycle, Credit Card, and Expiration Date. A manager requests that the report show only those customers who meet the following conditions: - The customer is on a monthly billing cycle - The credit card is either MoreCash or Vista - The credit card expires within 60 days Which set of filtering conditions returns a report with the desired data?
Answer(s): B,D
To fulfill the manager's request for a report showing only customers who are on a monthly billing cycle, use a MoreCash or Vista credit card, and whose credit card expires within 60 days, the filtering conditions need to precisely combine these criteria.B . Credit Card equals MoreCash OR Credit Card equals Vista AND Billing Cycle equals monthly AND Expiration Date equals next 60 days: This set of conditions accurately captures the required filters. The use of "OR" between the Credit Card conditions allows for the inclusion of customers with either MoreCash or Vista credit cards. The "AND" conjunction with Billing Cycle equals monthly ensures that only those on a monthly billing cycle are included. Lastly, specifying that the Expiration Date equals the next 60 days filters for credit cards expiring within the specified timeframe. This combination of conditions ensures the report displays precisely the desired data. Option A incorrectly uses "AND" for credit card types, which is logically impossible since a credit card cannot be both types simultaneously. Option C inaccurately suggests using a condition on the billing cycle that is not aligned with the requirement and incorrectly frames the expiration date condition. Option D simplifies the conditions but lacks the precise logical structure provided in option B, potentially leading to confusion or incorrect implementation.
Pega's reporting features and documentation detail how to construct complex filter conditions in report definitions, ensuring accurate and useful data retrieval based on specified criteria.
A requirement for a hotel reservation case type states that as customers change their room selection, the total cost of the reservation updates. How do you satisfy this requirement?
Answer(s): D
To meet the requirement that the total cost of a hotel reservation updates as customers change their room selection, using a declare expression is the most effective approach. D . Define a declare expression for the total cost field: A declare expression allows for the automatic calculation of the total cost field whenever related properties, such as room selection, change. This setup ensures that the total cost reflects the current room selection dynamically, providing an updated cost to the customer without manual intervention. Configuring a Validate rule (A) is typically used for verifying that entered data meets certain criteria, not for dynamically updating values. Applying a Disable when condition (B) would not contribute to the calculation or update of the total cost but would instead control the editability of the field. Adding a When condition (C) to the room selection step could influence the flow of the case but does not directly result in updating the total cost.
Pega's documentation on declare expressions elaborates on their use for automatically updating property values based on changes in other properties, highlighting how this feature facilitates real-time data adjustments within applications.
A requirement states When a customer applies for a credit card, a credit check must be completed in order for the credit card to be approved.Select the case type relationship that satisfies the requirement.
Answer(s): C
For the requirement that a credit check must be completed for a credit card to be approved, incorporating the credit check as part of the credit card application process is necessary. The most straightforward way to model this is by using case type relationships. C . Make credit check a child case of credit card request: This configuration establishes the credit check as an integral step within the credit card request process, ensuring that the credit check is completed before the credit card can be approved. Making the credit check a child case means it is directly associated with and dependent on the parent credit card request case, aligning perfectly with the requirement.Making both the loan request and credit check top cases (A) does not establish the necessary dependency. Creating a spin-off case (B) suggests a parallel or subsequent process not inherently dependent on the completion of the credit check for the credit card request, which could misalign with the requirement. Making the credit card request a child case of credit check (D) inverts the intended relationship and does not accurately represent the process flow described in the requirement.
Pega's case management documentation provides insights into designing case hierarchies and relationships, including the use of child cases to model dependent processes within an overarching case.
A requirement states: A customer can update an address at any point during case processing by performing the following steps.1. The customer submits the new address.2. The application verifies that the address matches postal service requirements.3. The customer then approves the corrected address. How do you configure this requirement?
Answer(s): A
To configure the requirement that allows a customer to update their address at any point during case processing, including submission, verification, and approval of the new address, an approach that provides flexibility and accessibility throughout the case lifecycle is needed. A . Add a case-wide optional action to the workflow for the address submission: This configuration enables the address update functionality to be accessible at any stage of the case processing. A case- wide optional action ensures that the customer can initiate the address change process whenever necessary, without being constrained by the current stage or step in the case. This approach aligns with the requirement
A requirement states: Loan applicants must enter their annual salary. If the salary is above the qualifying threshold, the application is automatically approved. If the salary is below the threshold, the applicant must identify a cosigner.Select the two configuration options that follow best practices to meet the requirement. (Choose Two)
Answer(s): A,B
To meet the requirement that loan applicants must enter their annual salary and that the application process diverges based on whether the salary is above or below a qualifying threshold, the configuration options chosen must efficiently manage the conditional logic and user interaction. A . Design a user view with an annual salary field and a data relationship for cosigner information:This approach efficiently handles the collection of applicant salary information and conditional display of cosigner information fields. A visibility condition based on the annual salary ensures that additional cosigner information is requested only when necessary, streamlining the application process for those above the threshold.B . Use a collect information step with an annual salary field. Use a decision shape to determine whether to advance to a step to enter cosigner information or complete the process: This configuration leverages the process modeling capabilities in Pega, where a decision shape dynamically directs the flow of the application based on the salary entered. It succinctly captures the requirement's logic, ensuring applicants are either promptly approved or directed to provide cosigner details, as appropriate.Option C proposes an optional action for collecting cosigner information, which might not strictly enforce the requirement for applicants below the salary threshold. Option D, involving manual review by a loan officer, introduces potential bottlenecks and departs from the requirement for automatic approval based on salary.
Pega's best practices for application development emphasize the importance of designing user interfaces and workflows that efficiently manage data collection and conditional processing, aligning with requirements for dynamic and responsive application behavior.
A requirement states: The date of birth submitted for first grade students must be at least five years before September 1 of the current year.Which three validation methods, when applied in combination, satisfy the requirement? (Choose Three)
Answer(s): A,D,E
To ensure that the date of birth submitted for first-grade students meets the requirement of being at least five years before September 1 of the current year, a combination of validation methods is necessary for comprehensive and effective validation.A . When rule: Can be used to determine if the provided date of birth satisfies the age condition relative to September 1 of the current year, serving as a condition in process flows or UI elements. D . Validation rule: Enables the definition of broader validation criteria that can encompass complex logic, including checking the student's age based on their date of birth in relation to a specific cutoff date.E . Edit validate rule: Provides a mechanism for implementing pattern-based validations or more intricate checks, including verifying that a date of birth makes a student eligible for first grade based on age.Calendar control (B) facilitates user input but does not enforce the specific age requirement on its own. Using the Date data type (C) ensures the field accepts dates, but without additional validation logic, it doesn't guarantee compliance with the age requirement.
Pega's official documentation on validation techniques outlines how to use various rules and controls to enforce data integrity and business rules, including age-based criteria for process eligibility.
A requirement states: The tax identification number must contain 10 digits. How do you configure the field to support this requirement?
Answer(s): B
For the requirement that the tax identification number must contain 10 digits, configuring the field to enforce this specific format is crucial.B . Use an edit validate rule: This rule type is designed to enforce specific patterns or formats in data input. By configuring an edit validate rule for the tax identification number field, the system can ensure that only values matching the 10-digit pattern are accepted, directly meeting the requirement.Setting the minimum and maximum values in a text field (A) might control the length of input but does not enforce numeric or pattern-specific constraints. Using a decimal property type (C) ensures numeric input but does not restrict the field to exactly 10 digits or to being treated as a non-numeric pattern. Configuring a validate rule (D) could enforce certain conditions but is generally broader and less specific than an edit validate rule for pattern enforcement.
Pega's documentation on field validation highlights the use of edit validate rules for enforcing specific input patterns, ensuring data entered into the application meets predefined formats.
A requirement states: When a business guest checks out of a hotel, the guest must complete a hotel review to receive a corporate discount. Select the case type relationship that satisfies the requirement.
To satisfy the requirement that a business guest must complete a hotel review to receive a corporate discount at checkout, the relationship between the checkout process and the hotel review process must be appropriately configured.D . Configure hotel review as a child case of the checkout request: This configuration establishes the hotel review
Post your Comments and Discuss Pegasystems PEGACPSA23V1 exam dumps with other Community members:
Amazon S3 Intelligent-Tiering
S3 Lifecycle
S3 Glacier Flexible Retrieval
Amazon Athena
Amazon EFS
EC2 instance store
ElastiCache for Redis
S3 Glacier Deep Archive
AWS Lake Formation
Amazon EMR Spark jobs
Amazon Kinesis Data Streams
Amazon DynamoDB
Defender for Endpoint
Defender for Identity
Defender for Cloud Apps
Defender for Office 365
S3 Object Lock
S3
SFTP
AWS Transfer Family
Amazon SQS
API Gateway
Lambda
usage plan
AWS WAF
Amazon ECS
Application Load Balancer
AWS Global Accelerator
Network Load Balancer
EC2
Auto Scaling group
CloudFront
ALB
AWS PrivateLink
CRR
SSE-S3
Athena
SSE-KMS
RDS Custom for Oracle
s3:GetObject
Amazon OpenSearch Service
CloudWatch Logs
Kinesis Data Firehose
Kinesis
S3 bucket
SQS
AWS Lambda
AWS Secrets Manager
AWS Systems Manager OpsCenter
secretsmanager:GetSecretValue
seq
for h in {1..254}
for h in $(seq 1 254); do
Kinesis Data Streams
Amazon Redshift
secrets:GetSecretValue
aws:PrincipalOrgID
"aws:PrincipalOrgID": "o-1234567890"
Azure Bot Service
Microsoft.Network/applicationSecurityGroups
Microsoft.Network/bastions
Microsoft.Network
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PEGACPSA23V1 content, but please register or login to continue.