These answers are correct because they achieve the behavior of creating a case ID only when the customer chooses to make changes to their membership. Temporary cases are cases that are not stored in the database until a Persist case step is reached in the case life cycle. This way, the case can be abandoned without creating any records or consuming any resources. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 4: Case Design)

This use case describes the function of the Estimator tool. The Estimator tool is a feature that helps you estimate the time and effort required to build an application or a release based on your scope definition and delivery approach. You can use the Estimator tool to plan your project schedule, budget, resources, and risks. References: https://community.pega.com/knowledgebase/articles/application-development/86/estimating-time-and-effort-application-development

Using the Pega Express delivery approach, governance is established during the prepare phase of the project. The prepare phase involves setting up the project team, roles, responsibilities, tools, processes, and standards that will guide the project delivery. Governance ensures that the project is aligned with the business objectives, follows best practices, meets quality criteria, and delivers value to the stakeholders. References: https://community.pega.com/knowledgebase/articles/pega-express-methodology/86/prepare-phase

To satisfy this security requirement, you need to create a new Analyst role with the required access. A role defines a set of permissions that grant access to specific features and functions in an application. You can create a new role by copying an existing role and modifying its permissions as needed. You can also assign multiple roles to a user or a group of users to grant them combined access. References: https://community.pega.com/knowledgebase/articles/security/86/managing-roles

To ensure that valid data is used in a case, you need to make sure that the data fits the business logic and the data is the correct field type. The data fits the business logic means that the data conforms to the rules and constraints that define the business problem and solution. For example, you can use validations, calculations, and dependencies to ensure that the data fits the business logic. The data is the correct field type means that the data matches the expected format and structure of the field that stores or displays it. For example, you can use different types of fields and controls to ensure that the data is the correct field type. References: https://community.pega.com/knowledgebase/articles/user-interface/86/ensuring-valid-data-used-case

To inform a user by email when an assignment is added to the user’s worklist, you need to configure the case type to send assignment notifications to assigned users. This option enables email notifications for all assignments in the case type. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/sending-email-notifications

To indicate the progress of a case towards resolution, you need to update the case status on the appropriate steps. The case status reflects the current state of a case and helps users track its progress. You can use standard statuses such as New, Pending-Approval, or Resolved-Completed, or define custom statuses for your application. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/updating-case-status