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

Page: 1 / 14
Total 234 questions
Question 1

The sales Operations team at AWS Computing deletes accounts for a variety of a reasons. The sales ops director is worried that the Sales team may delete accounts that sales reps are actively selling into.

Now should the app builder keep accounts with open opportunities from being deleted?



Question 2

The finance manager at Universal Containers wants to receive a new business notification email each time a new client is won. The sales manager wants to receive a task letting them know to onboard the new client unless it is a top-tier client.

Which automation tool should an app builder use to best address all these requests?



Question 3

An app builder at Northern Trad Outfitters created a sandbox template for Accounts, Projects, and Project Milestones to reconfigure some flows for the project management app.

Which type of testing environment should the app builder create?



Question 4

Northern Trail Outfitters wants the field sales team to only see the accounts that they own Separate North American and European marketing teams should only see accounts m their respective regions. The inside sales team needs to see all accounts in Salesforce.

How can this be accomplished?



Answer : C

Set the Organization-Wide Default to Private for accounts and create criteria-based sharing rules for each marketing team are the actions that can accomplish the requirement of restricting access to accounts based on region and role. Setting the Organization-Wide Default to Private will limit access to accounts to only owners and administrators. Creating criteria-based sharing rules will grant additional access to accounts based on region for each marketing team. Creating an Inside Sales Team profile with the ''View All'' setting for accounts will grant access to all accounts for the inside sales team. Update the Sales profile, update the organization-wide defaults to Public for accounts, create profiles for each marketing team, create permission sets for each marketing team, and create an Inside Sales Team role are not necessary or sufficient actions for this requirement.


Question 5

Ursa Major Solar wants to create a relationship between the standard Contact object and a custom Solar Project object Contacts potentially be related to multiple Solar Project objects, and a Solar Project can have multiple Contacts associated with it.

How should an app builder configure the data model?



Answer : D

Two Master-detail relationships on a new custom object is how an app builder should configure the data model to create a relationship between Contact and Solar Project objects where each Contact can be related to multiple Solar Project objects, and each Solar Project can have multiple Contacts associated with it. This is an example of a many-to-many relationship that requires a junction object with two master-detail relationships. One Master-detail relationship on Contact and one Master-detail relationship on Solar Project, two Lookup relationships on a new custom object, and one Lookup relationship on Contact and one Lookup relationship on Solar Project are not valid or correct ways to create a many-to-many relationship.


Question 6

Universal Containers has a private sharing model for Accounts and Opportunities and uses Territory Management to grant access to records.

* Sales rep A manually shares an opportunity record with sales rep B.

* Sales rep B has access to the Account even though the Account Is NOT In sales rep B's territory.

* Sales rep C CANNOT see either record.

Based on the information given, why can sales rep B see the Account related to the Opportunity?



Answer : A

Sales rep B has implicit access to the Account because of the manual sharing of the Opportunity. Implicit sharing grants access to parent records when a user has access to a child record. Sales rep B was not added to the Account team, sharing set is not applicable for private sharing model, and Account was not manually shared.


Question 7

Cloud Kicks Is redefining its entire business process to convert the Manager Notes field from a long text area files. The goal is to encourage managers to be more concise In their comments and stay at 255 characters or less. There is preexisting information In the Manager Notes field that often is well beyond the character limit.

What would happen to any existing information if the app builder tries to convert a preexisting long text area field to text area'



Answer : C

Preexisting information will remain even if it was over 255 characters if the app builder tries to convert a preexisting long text area field to text area. However, users will not be able to edit or save records with more than 255 characters in that field until they reduce the number of characters. Preexisting information will not truncate, be lost, or cause an error message.


Page:    1 / 14   
Total 234 questions