Free Practice Questions for Salesforce Platform-App-Builder Exam

For a formula to evaluate to true when the stage is set to "Negotiation/Review" and the close date is less than one week away, the correct formula is:

Option B. This formula uses the ISPICKVAL function to check the text value of a picklist and compares the CloseDate to a week from today:

AND( I AND(

ISPICKVAL(StageName, "Negotiation/Review"),

CloseDate - 7 < TODAY()

)SPICKVAL(StageName, "Negotiation/Review"), CloseDate - 7 < TODAY() )

This formula checks that both conditions are met: it confirms the stage name is "Negotiation/Review" and that the CloseDate is within the next 7 days from the current date.

Option A lacks the ISPICKVAL function necessary for evaluating picklist fields. Option C uses DAY(7) which is not a valid Salesforce formula expression. Option D also uses DAY(7) incorrectly and fails to use the ISPICKVAL function.

Reference for creating formula fields in Salesforce:

Formula Field Reference: https://help.salesforce.com/articleView?id=sf.customize_functions.htm &type=5

To have automatic posts on a record whenever a travel request has been approved, feed tracking should be used. Feed tracking enables field updates to be displayed in the Chatter feed of a record or a user profile. Users can follow records or users to see updates in their own feed. Feed tracking can be enabled for standard or custom objects and selected fields.

 The app builder should use two options to ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved:

Create an approval process on the Contract object with criteria set on a second approval step set as ‘Amount__c > 10,000’ and set the approver as director. An approval process is a type of process that automates how Salesforce records are approved in an organization. An approval process can have multiple steps with different criteria and approvers. In this case, the app builder can create an approval process on the Contract object with two steps: one for the sales manager approval and one for the director approval if the contract amount is over $10,0001.

Create a validation rule on the Contract object that prevents updates to the contract record while it is being reviewed. A validation rule is a type of rule that checks data quality by verifying that the data in a record meets certain standards before it can be saved. A validation rule can prevent users from making changes to a record that is in a certain status or stage. In this case, the app builder can create a validation rule on the Contract object that prevents updates to the contract record if its Approval Status field is not equal to Not Submitted2. Option B and D are not options that can ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved.

Guided Action Flows on the record page can help service agents meet the requirement of confirming a user identity before providing support information over the phone. Guided Action Flows are a series of screens that guide agents through a predefined process, such as verifying user information, collecting case details, or resolving issues

The solution that the app builder should use to meet DreamHouse Realty’s needs is Master-Detail Child Object. A master-detail relationship can be used to create a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a roll-up summary field on the parent object to calculate the highest value of all child records. Option B is incorrect because Text Area (Long) is a field type that allows users to enter up to 131,072 characters on one line, which is not suitable for this requirement. Option C is incorrect because Multi-select Picklist is a field type that allows users to select multiple values from a predefined list, which is not suitable for this requirement. Option D is incorrect because Lookup Object is not a valid term, but rather Lookup Relationship, which is a type of relationship that links two objects together, but does not support roll-up summary fields.

 An external ID field can be a number field or a text field, but not a URL field or a phone field. A URL field is used to store web addresses and a phone field is used to store phone numbers. An external ID field is used to store unique identifiers from an external system and it can be used for upsert operations

Criteria-based sharing rules are the best tool to use for automatically sharing records based on specific criteria, such as the opportunity type being "Service Agreement." This rule can share opportunities with all users in a particular role, such as the Service Manager role, when the criteria are met, thereby adhering to the private sharing model while still providing necessary access.

A: Owner-based sharing rules focus on the record owner's role or group, not the record type.

C: Apex sharing is used for more complex scenarios not easily handled by declarative sharing settings.

Schema Builder provides a graphical representation of all standard and custom objects and their field and relationship structure. It’s the best tool for visualizing how data objects are interconnected.

Why D (Schema Builder) is correct:Exact Extract:“Schema Builder provides a dynamic environment for viewing and modifying all the objects and relationships in your organization. You can add new custom objects, fields, and relationships directly in the schema.” — Salesforce Help | Schema Builder Overview

Why not A (Fields & Relationships):That section displays fields for a single object only, not overall relationships.

Why not B (Object Manager):The Object Manager allows object configuration but doesn’t visually display relationships.

Why not C (Lightning App Builder):That tool is for UI layout, not data model visualization.

Create a master-detail relationship field on Applicant__c to Application__c is what the app builder should recommend to meet the requirements of allowing the same applicant to apply for multiple open positions using a single application. This will create a many-to-many relationship between Applicant__c and Open_Position__c using Application__c as a junction object. Create a master-detail relationship on Open_Position__c to Application__c, create a master-detail relationship field on Application__c to Open_Position__c, and create a lookup relationship field on Applicant__c to Application__c are not valid or correct ways to create a many-to-many relationship.

The app builder should provision a Partial Data sandbox to the developer. A Partial Data sandbox can have up to 5 GB of data, which meets the requirement of having at least half a gigabyte of data. A Partial Data sandbox can also be refreshed every 5 days, which meets the requirement of refreshing after each three-day sprint. Option A is incorrect because a Developer sandbox can only have up to 200 MB of data, which does not meet the requirement. Option B is incorrect because a Full Copy sandbox can only be refreshed every 29 days, which does not meet the requirement. Option C is incorrect because a Developer Pro sandbox can only have up to 1 GB of data, which may not be enough for the requirement.