This option fits the scope for the minimum lovable product (MLP) based on Pega best practices. An MLP is the smallest version of an application that delivers value to customers and stakeholders while meeting their core needs and expectations. Pega best practices suggest that you should focus on building an MLP that solves one problem well, provides immediate feedback, and creates positive emotions for users. The option D satisfies these criteria by allowing customers to enter their order number and see the order status and delivery date details in one view. References: https://community.pega.com/knowledgebase/articles/application-development/86/defining-minimum-lovable-product

Pega Mobile Preview is a feature that allows you to view and interact with your Pega application on a mobile device without installing the app. It helps you to test the user interface and functionality of your app on different devices and screen sizes. References: https://community.pega.com/knowledgebase/articles/pega-mobile/86/using-pega-mobile-preview

This scenario is a use case for the Wait step because it involves pausing a case until another case reaches a certain status. The salary increase case can be configured to wait for the approval case to reach a Resolved-Approved status before continuing to process the increase. The other scenarios do not involve pausing a case based on a timer or a case dependency, but rather on user actions or inputs. References: https://academy.pega.com/topic/case-workflow-dependency/v1

A journey is a high-level description of an end-to-end process that delivers value to a customer or stakeholder. A microjourney is a specific path or scenario within a journey that achieves a particular outcome or goal for a persona or role. In this case, customer obtains troubleshooting assistance is a journey, and new customer obtains troubleshooting assistance by using a call center and experienced customer obtains troubleshooting assistance by using the online forum are microjourneys. References: https://community.pega.com/knowledgebase/articles/application-development/86/defining-journeys-and-microjourneys

To display the Select hotel amenities section only if a user selects the Add amenities check box, you need to apply a visibility condition (when rule) to the section. The when rule can check whether the Add amenities check box is selected or not, and show or hide the section accordingly. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/user-interface/87/controlling-visibility-ui-elements

Insights are interactive visualizations that help you explore and analyze data in your application. You can create insights from data queries by selecting the fields that you want to include and choosing a visualization type, such as a chart or a table. You can also share insights with other users or embed them in dashboards or portals. References: https://community.pega.com/knowledgebase/articles/reporting/86/creating-insights

These answers are correct because they prevent the accident claim case from resolving before all vehicle claims are resolved, as per the requirement. By adding each vehicle claim as a child case of the accident claim, you can create a case hierarchy that allows you to manage related cases together. By adding a wait step to the accident claim case, you can pause the parent case until all child cases reach a specific status, such as Resolved. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 5: Case Hierarchy)

To meet these requirements, you need to create four personas: Employee, HR, IT, and Facilities. A persona is a role that represents a group of users who perform similar tasks in your application. You can use personas to define user stories, assign tasks, configure access groups, and design user interfaces for your application. References: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81

To enable sales managers to approve sales quote proposals by email and from a mobile device, you need to add an Approve/Reject step to the case life cycle and enable email and mobile approval. This option allows sales managers to approve or reject the proposal by replying to an email message or by using a mobile app. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/approving-rejecting-cases-email https://docs-previous.pega.com/case-management/87/approving-rejecting-cases-mobile-devices

These two situations require a data type. A data type is a reusable component that defines the structure and behavior of a set of data in your application. You can use data types to access and write data from and to external systems of record, such as databases or web services. You can also use data types to populate fields with values from your application data, such as drop-down lists or radio buttons. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/creating-data-types