Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers | Set: 4

Approval Process is the feature that would be used to handle the requirement of signing off on major show retail deals with more than 30% discount. According to the Salesforce documentation, “An approval process automates how Salesforce records are approved in your org.” Email Alert, Field Update, and Workflow Rule are actions that can be triggered by an approval process, but they are not features for handling approvals.

The selected objects in the sandbox template. This is correct because a partial sandbox only copies a subset of data from production, and the data to be copied is determined by the sandbox template. If the Shipping object was not selected in the template, then its data would not be copied to the sandbox

The three Salesforce functionalities that are ignored when processing field updates in workflow rules and approval processes are:

Field-Level Security: This means that the field update will occur regardless of the user’s profile or permission set settings that determine whether they can see or edit the field1.

Validation Rules: This means that the field update will bypass any validation rules that might otherwise prevent the record from being saved1.

Decimal places and character limits: This means that the field update will round or truncate the value to fit the field’s format, without throwing an error

Ursa Major Solar requires a new field called Planet Details on the Planet object, where users can write detailed descriptions that can include pictures and links. The Rich Text Area field type is the best fit for this requirement.

Option B (Rich Text Area): A Rich Text Area field allows users to enter text with formatting options such as bold, italics, bullets, and numbering. Additionally, it supports inserting images and hyperlinks, which matches the requirement of including pictures and links in the description.

Rich Text Area Fields

Option A (Long Text Area): A Long Text Area field allows for lengthy text input but does not support formatting or embedding of images and links, which are necessary in this case.

Option C (Multi-Select Picklist): A Multi-Select Picklist allows users to select multiple values from a list but is not suitable for detailed descriptions or embedding images and links.

Option D (URL): A URL field is used to store and display a link but does not support text input or embedding images.

In summary, the Rich Text Area field type should be used because it allows formatted text, images, and links, which are required for the Planet Details field.

To connect Testimonial__c records with both the submitter’s Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. Source

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 recommend building a global action to create Contacts. A global action allows users to create records quickly from any page in Salesforce on their mobile devices. The app builder can also specify predefined values for some fields in the global action, such as Account Name or Phone Number, to make data entry easier for users. Option A is incorrect because customizing the mobile menu to move Contacts to the top does not help users create new contacts quickly or follow up later. Option C is incorrect because adding a compact layout to Contacts does not help users create new contacts quickly or follow up later, but rather shows them more fields on record detail pages or list views. Option D is incorrect because using Path and setting pre-defined values does not help users create new contacts quickly or follow up later, but rather guides them through different stages of a record.

A: Setting Sharing Settings to Read Only on both Master-Detail relationship fields ensures that users can view but not edit the master records from the junction object.