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

The app builder should add the fields to the page layout on the object to ensure users can access the new object and fields. The page layout determines which fields are visible and editable on the record detail page. Option A, B, and C are not necessary for this purpose.

The new object should have a lookup relationship to the Opportunity object. A lookup relationship creates a link between two objects and allows related records to be viewed in a related list. This can be used to track installation information for each opportunity and give sales reps visibility of all the installations associated with their opportunities. Option B, C, and D are not appropriate for this requirement.

The app builder should use a global picklist value set to share the list of values for the Status field across each object. A global picklist value set is a set of values that can be used by multiple picklist fields on different objects. This can ensure data consistency and reduce maintenance efforts. Option A, C, and D are not features that can share picklist values across objects.

The three reasons user A has access but user B is unable to access the record are:

User A is on the same account team as user C. Account teams are groups of users who work together on an account. Users who are on an account team can have access to the account and related records owned by other team members.

User C has manually shared the record with user A. Manual sharing is a way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy.

User A is in a public group that has access via a sharing rule. Public groups are groups of users who can be used to share data or assign permissions. Sharing rules are automatic rules that grant access to groups of users based on certain criteria. Option B and D are not reasons for user A's access.

An app builder can go to two places to see a list of available custom Lightning components in their org:

Lightning App Builder: This is a tool that allows an app builder to create and customize Lightning pages using drag-and-drop components.The app builder can see the list of custom Lightning components in the Custom section of the Lightning Components pane1.

Lightning Components in Setup: This is a setup menu that allows an app builder to view, create, edit, and delete custom Lightning components in their org.The app builder can see the list of custom Lightning components in the Lightning Components section of the Setup menu2. Option A and B are not places where an app builder can see a list of custom Lightning components.

The app builder should use the Path component to meet the requirement of tracking different fields at each stage of the Opportunity sales process. The Path component is a Lightning component that displays the key fields and guidance for each stage of a standard or custom picklist field, such as the Opportunity Stage field.The app builder can configure the Path component to show the fields that need to be filled out and provide recommendations and sales strategies for each stage3. Option A, B, and C are not configuration steps that can meet this requirement.

The app builder should use the Path feature to provide the functionality that the VP of Sales wants. The Path feature allows an app builder to create a visual representation of the stages in a business process, such as the Opportunity sales process.The app builder can also add key fields, guidance, and resources for each stage to help sales reps gather information and complete tasks4. Option A, C, and D are not features that can provide this functionality.

The app builder should create a master-detail relationship field on the gift card object to support the requirement. A master-detail relationship field creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record. In this case, the Account object would be the master and the gift card object would be the detail. By creating a master-detail relationship field, the app builder can meet these requirements:

Track the total number of gift cards opened and gift cards issued on an Account: This can be done by creating roll-up summary fields on the Account object that count or sum up the values from the gift card records related to each account.

Permanently ensure the gift cards are unable to be moved across any other Account once it is created: This can be done by making the master-detail relationship field required on the gift card object, which means that every gift card record must be associated with an account record and cannot be changed once set. Option B, C, and D are not types of fields that can support this requirement.

The app builder should recommend a workflow rule to automate this process. A workflow rule is a type of automation tool that can execute actions based on certain criteria. In this case, the workflow rule can have a criterion that evaluates if the DoNotCall checkbox is checked on a Contact record, and then execute a field update action that sets the Phone field to null. Option A, B, and C are not automation tools that can perform this task.