Salesforce DEX-403 Declarative Development for Platform App Builders in Lightning Experience Exam Practice Test

Answer : C

To ensure sales reps input contacts into Salesforce rather than their personal devices:

C . Enable offline create, edit, and delete in Salesforce for Android and iOS. This feature allows sales reps to enter contact information directly into the Salesforce Mobile App even when they are offline, which syncs back to Salesforce once connectivity is restored.

Steps to enable offline capabilities:

Navigate to Setup Mobile Administration Salesforce Mobile App Offline Settings.

Configure offline settings to allow for creating, editing, and deleting records.

Ensure that the Contact object is available for offline access.

This functionality encourages reps to use Salesforce directly by mitigating connectivity constraints.

For implementation details, refer to Salesforce Mobile App Offline.

Answer : D

For tracking whether contracts have been sent for Opportunities:

D . Checkbox. This field type allows users to clearly indicate (Yes/No) whether a contract has been sent. This binary nature of checkboxes makes it simple to filter and report on Opportunities based on whether a contract was sent.

Steps to configure this field:

Navigate to Setup Object Manager Opportunity.

Click Fields & Relationships New Checkbox.

Define the field with a label (e.g., Contract Sent).

Set the default value to false (unchecked).

Add the field to the relevant page layouts.

This setup facilitates accurate reporting and ensures that opportunities cannot be marked as 'Closed Won' without indicating whether a contract was sent.

For guidance on creating fields, see Salesforce's documentation on Custom Field Creation.

Answer : C

To add components to the utility bar of an existing app:

C . App Manager. This is where Salesforce apps are configured, including the utility bar which can house components like a chat tool, recent items list, or custom Lightning components.

Steps to edit an app's utility bar:

Navigate to Setup App Manager.

Locate the desired app and click on the dropdown next to it select Edit.

In the App Builder, navigate to the Utility Items tab.

Click 'Add' to include new components to the utility bar.

Configure the properties of the utility item as needed.

Save the app configuration.

For step-by-step instructions on modifying apps, see Salesforce's guide on Managing Apps in Lightning Experience.

Answer : A, C

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.

Answer : D

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.

Answer : D

The 'Accordion' Lightning component is designed to break up content into collapsible sections. This component would be suitable for managing the visibility of large numbers of fields by grouping them into separate tabs or sections that can expand and collapse. This makes navigation easier and declutters the interface.

A: Highlights panel is used for displaying key record information at the top of the page and is not designed for managing multiple fields.

B: Record detail displays all fields on a single layout, which does not suit the requirement to break up the fields.

C: Field section does not exist as a standard Lightning component. Reference: Accordion Component in the Lightning Component Library

Answer : C

Formula fields in Salesforce can use various functions including text, mathematical, and logical functions to create simple or complex expressions. They can handle data from fields of the same record. Option C, 'A combination of the Opportunity's Text and a Description fields,' is a valid configuration for a formula field as it involves simple concatenation of text fields, which is supported. Options A, B, and D exceed the capabilities of formula fields:

A: Hyperlinks to other objects using formula fields do not directly support navigation to parent records of a different object.

B: Rich Text and HTML formatting are not supported in formula fields.

D: Formula fields have limits in their complexity and field references which would make mixing numerous fields from different related objects impractical and likely exceed formula size limits. Reference: Formula Field Overview on Salesforce Developer Guide