Platform-App-Builder Exam Dumps - Salesforce App Builder Questions and Answers

Salesforce states that to make a custom object ' s records searchable, an administrator can create a custom tab set to Default On or Default Off ; creating the tab enables the object ' s search capability. Salesforce also warns that a custom object ' s tab must be visible for the user ' s profile and specifically says not to set the tab to Tab Hidden. A Search Layout controls which fields users see in search results but does not by itself enable object searchability. A search filter similarly refines results rather than enabling the custom object in Global Search. Therefore, among the available options, creating the custom tab with Default Off is the correct configuration.

The correct answer is A. Sharing Hierarchy.

Sales reps want to see who has access to an Account record and why/how they have that access. Salesforce provides this through Sharing Hierarchy. Salesforce documentation states that users can click Sharing Hierarchy from the record action menu to display users who have access to the record. Salesforce release documentation also explains that selecting Sharing Hierarchy lets users view record access and the reason for that access.

C. Sharing is not the best answer because the Sharing button is mainly used to manually grant access, not to view the full access hierarchy and access reasons. B. New Task and D. Edit do not relate to record access visibility.

===========

In the Salesforce mobile app, navigation depends on the Lightning app the user is using. Salesforce documentation states that mobile navigation items depend on the active Lightning app, and when a Lightning app is enabled for desktop and phone, the desktop navigation tabs sync to the mobile navigation menu. Salesforce also notes that different menu configurations cannot simply be set directly for different user types. Therefore, the correct design is to create separate Sales and Marketing Lightning apps with different navigation items, then assign access to the appropriate profiles.

Salesforce provides parent implicit access between certain standard objects. When a user receives access to a child Opportunity, Case, or Contact through ownership or sharing, Salesforce automatically provides that user with Read Only access to the associated parent Account. Sales Rep B therefore receives access to the Account because Rep B was manually granted access to the related Opportunity. No separate Account sharing operation is required. Salesforce specifically states that access to a child Opportunity can grant implicit Read Only access to its parent Account even when Account organization-wide defaults are Private. Territory membership is therefore not required for this particular access path. An Account Team could independently provide access, but the scenario does not state Rep B was added to one. The documented parent implicit-access mechanism directly explains the behavior. Salesforce

================

For an Accounts with Opportunities parent-child report type, Salesforce ' s current documentation confirms that the default report record count is based on the child Opportunity rows , not the number of unique parent Accounts. For example, if one Account has five Opportunities, Salesforce returns five report rows and a record count of five even though only one Account is represented. This occurs because the report output is driven by the child records. Therefore, D most precisely describes the current Salesforce behavior. Option A would incorrectly count unique Accounts, while B suggests both parent and child objects are separately included in the total.

================

The correct answer is A. TODAY().

The formula needs to calculate how many whole days have elapsed since a marketing communication was sent. The TODAY() function returns the current date as a Date value, which is appropriate for whole-day calculations. Salesforce documentation also shows that TODAY() can be used with addition and subtraction operators for date calculations.

NOW() returns a Date/Time value and can introduce fractional day/time calculations. DATEVALUE() converts a Date/Time or text value into a Date, but the question asks which function should return today’s date for calculating elapsed days. DATETIMEVALUE() returns a Date/Time value, not the desired whole-date calculation.

===========

The correct answer is D. Create a new text field and import the formula field values in it.

The existing Specialty__c field is a formula field, so users cannot manually edit it. Formula fields calculate their value automatically from other fields. Since Cloud Kicks now wants Opportunity Specialty__c values to be different from the related Account value, the app builder should create a new editable field, such as a Text field, and then load the existing calculated formula values into that new field for existing Opportunity records.

This preserves historical Opportunity values while allowing sales reps to enter or update Specialty values going forward. Salesforce documentation explains that roll-up/formula-style calculated values are system-derived, while changing custom field types has limitations and requires care when data must be preserved.

A and B are incorrect because a formula field cannot simply become an editable text field while safely preserving all existing calculated values.

C is incomplete because creating a new text field without importing the existing formula values does not preserve the current values on existing Opportunities.

===========

A Salesforce validation rule prevents a record from being saved when its formula evaluates to TRUE. The rule therefore must return TRUE when the Account is locked and the current user ' s profile is not System Administrator. $Profile.Name is the appropriate global variable for testing the current user ' s profile. Salesforce documents $Profile global merge fields for accessing profile properties, including $Profile.Name , and provides validation-rule examples using profile-name comparisons to exempt authorized profiles. Option A tests the user ' s role, but System Administrator is a profile, not a role. Option C introduces an unrelated Opportunity Stage condition. Option D reverses the logic and would block the System Administrator instead of exempting that profile. Therefore, B correctly implements the stated lock exception.

================

The correct answer is C. A record-triggered flow can run automatically when an Opportunity is updated to Closed Won, create a renewal Opportunity, and notify the contracts team. Salesforce Trailhead explains that record-triggered flows are built around trigger, criteria, and action; for example, when an Opportunity is created or updated and meets criteria, the flow can create another record.

Salesforce Flow can also create records and send emails, which fits both requirements: create the renewal Opportunity and notify an external contracts team.

Why others are incorrect:

A Approval Process is for review/approval routing.

B Outbound Message may notify an external system, but it does not handle the full renewal Opportunity creation requirement by itself.

D Validation Rule only prevents bad data; it does not create records or send notifications.

===========

The correct answer is D. The Owner field on the Master record.

In a master-detail relationship, the detail record does not have independent ownership. Salesforce documentation states that the Owner field on the detail object isn’t available and is automatically set to the owner of the related master record.

Sharing is also controlled by the parent/master record. Salesforce Help explains that when a custom object is on the detail side of a master-detail relationship, its organization-wide default is set to Controlled by Parent.

A and C are incorrect because the detail record does not maintain independent ownership in a master-detail relationship. B is incorrect because ownership is not determined by a default owner setting on the parent object; it comes from the actual Owner field on the master record.

===========