A Pega Platform application designed for customer onboarding in a bank involves multiple subprocesses and extensive data entry and retrieval. With over 15 screens to navigate, the Quality Assurance team faces challenges in thoroughly testing the application. Each bug fix requires the team to restart testing from the beginning, adding to the difficulty. What suggestion do you adopt as a Lead System Architect to assist the team?

• A. Encourage the team to write utilities to speed up the testing process.
• B. Advise the team to create Pega test suites to run the bulk test cases in one go and speed up the testing process.
• C. Suggest that the team begins recording with the screen recording feature of the browser, and then replay the recording when testing the application after performing bug fixes.
• D. Advise the team to begin recording the testing performed using the scenario testing feature, and then replay the recording when testing the application after performing bug fixes.

You are a Pega developer working on an insurance application. The application needs to manage different types of insurance policies such as car insurance, home insurance, and life insurance. Each type of insurance policy has some common attributes (policy number, policyholder name, and premium amount), but also has some unique attributes (such as vehicle details for car insurance, property details for home insurance, and beneficiary details for life insurance). Which one of the following approaches to handling this scenario would be most appropriate in a Pega application?

• A. Create a base class for the insurance policy for the common attributes, and then create derived classes for each type of insurance policy with their unique attributes.
• B. Create a single class for all types of insurance policies and dynamically add or remove attributes as needed.
• C. Create a separate class for each type of insurance policy and then define the common attributes in the new class.
• D. Create a single class for all types of insurance policies and define all possible attributes.

As a Lead System Architect, the primary objective is to adhere to the low-code application development methodology and support citizen developers. Relevant records are a feature in App Studio that can help facilitate this process. Which two of the following options outline the benefits of relevant records? (Choose Two)

• A. Relevant records control the run-time availability of rules, which consequently decreases the time consumed during the rule performance.
• B. Users can achieve efficient resource management by promoting a rule from a built-on application, which enables its reuse in another class.
• C. Relevant records regulate design-time prompting and filtering across various areas of App Studio, which reduces the time spent searching through unrelated records in cases.
• D. Users can promote instances from a built-on application for reuse in another application for effective data or case instance management.

The test coverage report in Pega Platform helps to determine the number of rules covered during a test cycle.
It is viewable at the application and user level. Which of the following statements describes the difference between these two levels?

• A. The application level focuses on rules created at the application ruleset level, while the user level focuses on rules created in branch rulesets.
• B. The application level includes the details of testing performed by all users in that session, while the user level pertains only to the user who initiated the testing session.
• C. The application level includes rules created at the enterprise application layer, while the user level involves rules created at the implementation layer.
• D. The application level encompasses details of testing conducted with APIs, while the user level is specific to testing that the user performs.