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

Answer : A

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.

Answer : A, D

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.

D: Creating an owner-based sharing rule that gives Read access to the junction object allows specific users or groups to access and edit records in the Junction object while maintaining the private OWD setting. References:

Salesforce Help - Sharing Settings

Answer : D

The best solution to enable reps to see and access the most-used components from anywhere within the app without leaving the page they are working on is Utility bar. This is a footer that can be added to any Lightning app and can contain tools such as history, notes, or softphone. Favorites, home page, and global actions are not solutions that provide access to components from anywhere within the app. See [this article] for more information on Utility bar.

Answer : C

The primary object selection is locked once the custom report type has been saved. This means that the app builder cannot change the primary object later. The other options are not true.

Answer : B

Partial Copy is the type of testing environment that the app builder should create to use a sandbox template for Accounts, Projects, and Project Milestones. According to theSalesforce documentation, ''Partial Copy sandboxes copy your production org's configuration (metadata) and some of your production org's data as defined by a sandbox template.'' Developer, Developer Pro, and Scratch Org are not types of testing environments that support sandbox templates.

Answer : A, D

The two actions that an app builder should take to meet the requirements are: Implement a sharing rule. A sharing rule is a way to grant additional access to records based on certain criteria, such as record owner, role, profile, or field value. The app builder can create a sharing rule that grants read access to all accounts with the VIP Account field value to all users. This way, all users can view these accounts, but only the owners can edit them. Change organization-wide defaults. Organization-wide defaults are the baseline level of access that users have to records they do not own. The app builder can change the organization-wide default for accounts from Public Read Only to Private. This way, only the owners can view and edit their own accounts, unless additional access is granted by other means, such as sharing rules. Configuring a permission set is not a valid action, as it does not affect record-level access. A permission set is a way to grant additional permissions and access settings to users on top of their profile settings, such as object permissions, field permissions, app permissions, etc. Setting up an Account Team is not a valid action, as it does not restrict record-level access. An Account Team is a way to share an account and its related records with a group of users who work together on the account, such as sales reps, managers, or support agents. An Account Team grants additional access to team members based on predefined roles and access levels.

Answer : B

The app builder should go to the Account object to build these new rollups. A roll-up summary field is a type of field that can aggregate numeric values from child records related to a parent record by a master-detail relationship. The app builder can create two roll-up summary fields on the Account object that count the number of open Opportunities and the number of won Opportunities related to each Account. Lightning App Builder is not a place where the app builder can build these new rollups. Lightning App Builder is a tool that allows the app builder to customize the layout and components of Lightning pages, such as record pages, home pages, or app pages. It cannot create new fields or relationships on objects. Lightning Object Creator is not a place where the app builder can build these new rollups. Lightning Object Creator is a tool that allows the app builder to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot create roll-up summary fields or relationships on existing objects. Opportunity object is not a place where the app builder can build these new rollups. The Opportunity object is the child object in the relationship with the Account object, and roll-up summary fields can only be created on the parent object.