Platform-App-Builder Exam Questions

Explanation: Roll-up summaries allow MAX, MIN, SUM, COUNT, and AVG functions on numeric fields from child records related by a master-detail relationship. Roll-up summaries are limited to master-detail relationships and cannot be used with lookup relationships. An object can have up to 40 roll-up summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

Explanation: 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.

Explanation: To provide a help guide to enable reps to easily get help where needed during the different sales processes, an app builder should recommend Path. Path is a component that displays the key fields and guidance for each stage of a sales process on an object’s record page. Users can see where they are in the process, update the stage and fields, and access resources such as tips and links.

Explanation: 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.

Explanation:
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.

Explanation: To insert a list of 25,000 records using deduplication for the Race_Track__c custom object, an app builder should use Data Loader. Data Loader is a tool that allows users to insert, update, delete, or export large amounts of data in Salesforce. Data Loader can also perform deduplication by matching records based on external ID fields or Salesforce record IDs.

Explanation:
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.

Explanation: Customers who are invited to Chatter groups can only interact with members of their groups. They cannot invite other members, @mention accounts, or request access to public groups.

Explanation:
To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:
C. Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.
Steps to set up field-level security:
Navigate to Setup Object Manager Solar System.
Select Fields & Relationships Jupiter field.
Click Field-Level Security.
For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.
For the Outer Planets profile, check Visible to grant access.
This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.
For more information on field-level security, check Salesforce's guide on Field-Level Security.

Explanation: NOT(ISBLANK(Job_Accepted__c)) && ISCHANGED(Hire_Date__c) is the validation formula that the app builder should use to meet the requirement of preventing changes to Hire Date after Job Accepted is entered. This formula will return TRUE if Job Accepted is not blank and Hire Date is changed, which will display an error message and prevent saving the record. The other formulas are not correct or valid.