Get Salesforce Platform-App-Builder Exam Dumps

Answer : C

The deployed permission set will merge with the existing permission set in production, meaning changes made in the sandbox will be added to the existing permission set after deployment. Reference:

Salesforce Help - Permission Sets

Answer : B

Create a validation rule on the Account object is how the app builder can keep accounts with open opportunities from being deleted. According to theSalesforce documentation, ''Validation rules verify that data entered by users in records meet the standards you specify before they can save it.'' A validation rule can check if an account has any open opportunities and display an error message if someone tries to delete it. Create an Apex trigger on the Account object, remove the delete button on the account layout, and remove the Delete permission from the Sales Rep profile are not valid or sufficient solutions for this requirement.

Answer : B, C

Process Builder and Apex are two automation solutions that can meet the business requirements of summarizing the number of open and closed Cases related to an Account. Process Builder can create a process that updates the custom fields on Account based on changes in related Cases. Apex can write a trigger that performs the same logic using code. AppExchange and Workflow are not automation solutions for this requirement, but sources of apps or components and tools for creating workflow rules respectively.

Answer : D

Create a custom action is the recommended solution to meet the requirement of creating additional accounts to form a hierarchy from a Parent Account record. According to theSalesforce documentation, ''Actions let users quickly create or update records, log calls, send emails, and more, in the context of a particular object.'' A custom action can auto-populate fields based on the parent account and make it easier for users to create child accounts. Add Path on Account hierarchy, add a custom link on Account, and customize a Global Quick Action are not valid or feasible options.

Answer : C

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.