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

When attempting to change a master-detail relationship to a lookup relationship, Salesforce imposes specific restrictions to maintain data integrity:

C . The Account record includes Parks roll-up summary fields. Master-detail relationships allow roll-up summary fields to aggregate data from child records onto the parent record. If any roll-up summary fields are present on the master object (Account in this case) that depend on the detail records (Parks), the relationship cannot be changed to lookup until these roll-up summary fields are removed.

To resolve this, follow these steps:

Identify and delete all roll-up summary fields on the Account object that reference the Park object.

Convert the master-detail relationship to a lookup relationship.

Recreate any necessary roll-ups using declarative tools like Process Builder or Flow if needed, as lookups do not support native roll-up summaries.

For more guidance, review Salesforce's documentation on Changing Field Types.

To ensure data integrity where the Region field on the Contact object needs to be filled out conditionally based on the parent Account's status, a validation rule on the Contact is the most effective method:

B . Create a validation rule on Contact. This rule can enforce that the Region field must be filled out for Contacts related to Accounts marked as 'High Priority'.

Steps to create this validation rule:

Navigate to Setup Object Manager Contact Validation Rules.

Create a new validation rule.

In the formula, use:

AND(

ISPICKVAL(Account.Customer_Status__c, 'High Priority'),

ISBLANK(Region__c)

) )

Provide an error message to display when the rule is violated.

Save and activate the rule.

This validation rule checks that if a Contact is associated with an Account marked 'High Priority', the Region field cannot be blank.

For further detail, Salesforce's Validation Rule Considerations provides additional guidance.

To create a custom object along with multiple fields and relationships efficiently from a single interface, the Schema Builder is the ideal tool:

A . Schema Builder. This graphical tool provides a drag-and-drop interface for creating and modifying objects and fields in Salesforce, allowing for a visual layout of database schema.

Steps to use Schema Builder:

Go to Setup Schema Builder.

Drag the 'Object' element into the schema area to create a new custom object.

Define the object's properties (e.g., label, API name).

Drag field elements like Text, Number, or Lookup into the object to create fields.

Configure each field's properties according to your requirements.

Connect objects via lookup or master-detail relationships by dragging the relationship fields between them.

Save the layout to create all elements in Salesforce.

For more information, review Salesforce's Schema Builder documentation.

The issue described occurs due to the settings in the master-detail relationship. Specifically:

The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked (B). This setting prevents changing the parent record (contact) of a child record (service plan) once it has been set. If 'Allow reparenting' is unchecked, it restricts the ability to change the associated contact, leading to the issue observed.

The other options do not directly address the inability to change the associated contact on a service plan record. The 'Read Only' and 'Read/Write' settings (A and C) pertain to access rights to the detail records based on the master record's access but do not affect the ability to reparent a record.

For a detailed understanding of master-detail relationships and their settings, including reparenting, see the Salesforce documentation on relationships:

Master-Detail Relationships: https://help.salesforce.com/articleView?id=relationships_considerations.htm&type=5

To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:

C . Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.

Steps to set up field-level security:

Navigate to Setup Object Manager Solar System.

Select Fields & Relationships Jupiter field.

Click Field-Level Security.

For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.

For the Outer Planets profile, check Visible to grant access.

This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.

For more information on field-level security, check Salesforce's guide on Field-Level Security.

To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established:

D . Read-Only access on Case and Issue__c. Users need read-only access to both Case and Issue__c objects to view associated Case_Issue__c junction object records properly. This is because access to junction object records in Salesforce is determined by the user's access levels to the parent records in a relationship.

Steps to configure access:

Navigate to Setup Profiles or Permission Sets.

Select the profile or permission set of the auditing users.

Under Object Settings, adjust the permissions for Case and Issue__c to at least 'Read-Only'.

Ensure that users have visibility to the Case_Issue__c object itself.

This configuration allows users to view the details of cases and issues as they audit the junction object records.

To allow users access to Flows, Salesforce offers multiple integration points:

A . Quick Action: Flows can be initiated from record pages, the app utility bar, or global actions using Quick Actions. This allows users to execute flows relevant to specific records or global processes.

C . Flow Launcher: A component available in Lightning App Builder that enables users to start flows directly from a Lightning page.

Steps to set up these features:

For Quick Actions, navigate to Setup Object Manager select object Buttons, Links, and Actions New Action Action Type (Flow).

For Flow Launcher, navigate to Lightning App Builder select the page drag the Flow component to the desired section of the page configure it to launch the specific flow.

For more information on integrating Flows, check the Salesforce documentation on Flow Distribution.

In the Lightning App Builder, the following standard components can be used to enhance the functionality of Lightning pages:

B . Rich text: Allows the inclusion of formatted text, links, and images on a page.

D . Report details: Enables embedding of specific report details directly on a page.

E . Recent items: Displays a list of recently accessed items relevant to the user.

Steps to add these components:

Open the Lightning App Builder via Setup Edit Page or when creating a new Lightning page.

Drag and drop the Rich text, Report details, and Recent items components from the standard components section onto the page layout.

Configure each component as needed (e.g., selecting a specific report for the Report details component).

For more on using these components, refer to Salesforce's guide on Standard Lightning Components.

For managers to respond to approval requests for opportunities above $50,000 in the Salesforce mobile app:

B . In-App Notification: Managers receive notifications within the Salesforce mobile app when there is an approval request, allowing them to approve or reject directly from the notification.

C . Record Detail: Managers can access the approval request directly from the Opportunity's detail page in the mobile app, where they can review and respond to the request.

Steps to configure approval process notifications:

Navigate to Setup Approval Processes select the relevant approval process.

Ensure the process is active and configured to send notifications to approvers.

Managers need to have the Salesforce mobile app configured to receive notifications.

For best practices on managing approvals in Salesforce, see Approvals in Salesforce.