Salesforce Certified Platform App Builder Practice Test - Questions Answers, Page 15

The app builder should do three things to optimize mobile experience:

Use Global Actions to make it easy to perform vital functionality on mobile: Global actions are actions that allow users to create records or perform tasks from anywhere in Salesforce. They are displayed in various places in Salesforce mobile app, such as action bar, action menu, or publisher. By using global actions, the app builder can make it easy for the appraisal team to perform common tasks on mobile, such as creating a new appraisal record or logging a call.

Minimize the amount of formula fields and lookup fields to reduce page load time: Formula fields and lookup fields are types of fields that can affect the performance of Salesforce mobile app. Formula fields are fields that calculate a value based on an expression or formula. Lookup fields are fields that create a relationship between two objects and allow users to select a value from a list of records. Both types of fields can increase the page load time on mobile devices, especially if they are complex or reference many other fields. By minimizing the amount of formula fields and lookup fields, the app builder can optimize the mobile experience for the appraisal team.

Put the most important fields in the compact layout so they are easy to find: Compact layouts are layouts that display a record's key information at a glance. They are used in various places in Salesforce mobile app, such as record highlights, list views, related lists, and lookup dialogs. By putting the most important fields in the compact layout, the app builder can ensure that the appraisal team can easily find the information they need on mobile devices. Option B and D are not things that an app builder should do to optimize mobile experience.

The app builder should use Apex code to update a field on the parent record when a child record connected via lookup is deleted. Apex code is a programming language that allows developers to execute complex logic on the Salesforce platform. Apex code can be triggered by certain events, such as insert, update, delete, or undelete of records. In this case, the app builder can write an Apex trigger that runs after a child record is deleted and updates a field on the parent record accordingly. Option A, B, and D are not automation tools that can perform this task.

The app builder should create a new roll-up summary field called First Order Date, using Type MIN on the Opportunity Close Date with a filter where IsWon = TRUE. A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. In this case, the app builder can create a roll-up summary field on the Account object that calculates the minimum (earliest) value of the Opportunity Close Date field from the related opportunities where IsWon = TRUE. This will show when customers made their first purchase. Option B, C, and D are not correct ways to use a roll-up summary field to meet the requirement.

The app builder needs to do two steps to make the custom Lightning App available to the internal users at Universal Containers:

Create a subdomain using My Domain: My Domain is a feature that allows an organization to set up a custom domain name for their Salesforce instance.This is required to use custom Lightning components and apps in Salesforce1.

Build a Custom Tab for the app: A custom tab is a tab that displays any custom object or web page in Salesforce.This is required to make the custom Lightning App accessible from the navigation menu or app launcher2. Option A and B are not necessary steps to make the custom Lightning App available to the internal users.

The app builder should verify that there is an Apex test that provides test coverage for the Flow. An Apex test is a unit test that verifies the functionality and quality of Apex code.Apex tests are required to deploy any change that contains Apex code or references Apex code, such as an auto launched flow3.The app builder should ensure that there is an Apex test that covers at least 75% of the Flow logic before deploying it to production in an active state4. Option B, C, and D are not things that the app builder should take into consideration when planning the deployment.

The app builder needs to have NOT(ISBLANK([Lead].OwnerId)) in the criteria to ensure the process runs without error. This formula checks if the OwnerId field on the Lead object is not blank, which means that the lead is owned by a user or a queue. This will prevent the process from running on leads that are not owned by anyone, which could cause an error. Option A, B, and C are not formulas that can ensure the process runs without error.

The app builder should add the field to the custom report type field layout to troubleshoot this issue. A custom report type is a type of report that defines which objects and fields are available for reporting. The app builder can customize which fields are included in each custom report type by editing its field layout. If a new field is added to an object that is part of an unmanaged package, it will not be automatically added to the custom report type field layout. The app builder needs to manually add it to make it available as an option to add as a column in reports based on that custom report type. Option A, B, and D are not steps that can troubleshoot this issue.

The app builder should know that a field type change is included in the change set and that it can cause a delay in the deployment. A field type change is a change that modifies the data type of an existing field, such as changing a text field to a number field. A field type change can affect many aspects of Salesforce functionality, such as validation rules, formulas, workflows, reports, dashboards, and more. Therefore, deploying a change set that contains a field type change can take longer than usual and require more testing and verification. Option A, C, and D are not changes that can cause a delay in the deployment.

The app builder should create a sharing rule that grants the users Read/Write access to the Application records. A sharing rule is a type of rule that can extend record access to groups of users based on certain criteria. In this case, the app builder can create a sharing rule that grants Read/Write access to the Application object to the recruiters based on their role, public group, or queue. This will allow them to edit the Application records related to any Internship record, regardless of the ownership. Option A, B, and C are not ways to configure the proper access.