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

The correct answer is D. Deselect auto add to custom report type.

When creating a new custom field, Salesforce provides an Auto Add option that can automatically add the new field to applicable existing custom report types. If the app builder does not want the new field to appear on pre-existing custom report types, they should deselect the Auto add to custom report type option during field creation. Salesforce release documentation confirms that Auto Add automatically adds custom fields to custom report types based on that object.

Why the other options are incorrect:

Removing the field from page layouts only affects record-page visibility, not report type availability.

Changing profile visibility or read-only access affects field security, not whether the field is added to the custom report type layout.

===========

The correct answer is A. Configure Campaign Interactions and Campaign statistics.

The option text appears to contain an OCR/wording issue. The intended Salesforce feature is Campaign Hierarchies and Campaign statistics. For advertising ROI, Salesforce Campaigns are the correct feature because Campaign ROI reports calculate return on investment using campaign cost and won opportunity value. Salesforce also states that campaign hierarchy metrics roll up from child campaigns to parent campaigns, which helps analyze campaign performance across related marketing efforts.

B is incorrect because Account interactions and roll-up summary fields are not the standard marketing ROI solution.

C is incorrect because changing the whole org to a public security model is unnecessary.

D is incorrect because an opportunity pipeline report alone does not provide campaign ROI analysis.

The correct answer is C. Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field.

A roll-up summary field is the recommended declarative solution when Salesforce needs to summarize child-record data on a parent record. Salesforce documentation states that roll-up summary fields calculate values from related records and are defined on the master side of a master-detail relationship.

In this scenario, Opportunity is the parent and Detailed_Sales__c is the child. The roll-up summary field can summarize sales metrics and use filter criteria so only child records where Status = Active are included.

Why others are incorrect:

A is incorrect because a third-party AppExchange app is unnecessary when native roll-up summary functionality meets the requirement.

B is incorrect because Apex is not recommended when a declarative feature can solve the requirement.

D is incorrect because lookup relationships do not support standard roll-up summary fields. Salesforce documentation states that lookup relationships are similar to master-detail relationships, except they do not support roll-up summary fields.

===========

The correct answers are C. Use Data Loader to update leads using the CSV file and D. Select Insert Null Values in Settings.

Universal Containers wants to delete values from fields on 5,000 Lead records. The correct method is to use Data Loader Update with the record IDs in the CSV file, leave the target field cells blank, and enable Insert Null Values so Data Loader treats the blank CSV values as null up dates. Salesforce Help explains that to change field values to blank/null with Data Loader, export IDs and fields, clear the values in the CSV, select Insert Null Values, and run an update.

Why others are incorrect:

A is unrelated because record type selection does not delete field values.

B is not the best choice because the Import Wizard is not the proper tool for mass clearing field values using null updates.

The correct answer is B. Field-level security.

Only users with the Outer Planets profile need to see the Jupiter field. Salesforce field-level security, also called field permissions, controls whether users can view or edit individual fields on an object. This is the proper way to restrict a field by profile or permission set.

Sharing rules control record-level access, not field visibility. Filtered views affect list views, not field security. Classic encryption protects sensitive data but is not the correct feature for profile-based field visibility.

===========

The correct answer is A. Existing reports created under the Sun__c with Planet__c report type made by Salesforce will be unusable, but not deleted.

When a relationship is changed from master-detail to lookup, the available standard report types can change. Salesforce documentation notes that converting a lookup relationship to master-detail or vice versa can make existing custom reports unusable because of differences in available standard report types.

B is incorrect because roll-up summary fields are not automatically deleted from reports as part of the conversion. In fact, Salesforce states that a master-detail relationship cannot be converted to lookup while roll-up summary fields exist on the master object.

C is incorrect because roll-up summary fields do not remain and simply stop updating.

D is incorrect because the reports are not deleted; they become unusable.

===========

The correct answer is A. Quick Action on the Account object.

Universal Containers wants users to create Opportunity records related to an Account, with many Opportunity fields automatically populated from the Account and some fields entered by the user. The best solution is an object-specific Quick Action on Account that creates an Opportunity. Object-specific actions run in the context of the parent record, and predefined field values can automatically populate fields to make record creation faster and more consistent.

C is incorrect because a Quick Action on Opportunity would not naturally start from the Account context. B and D are incorrect because assignment rules are not used for creating related Opportunities or prepopulating fields.

===========

The correct answer is A. Make the Opportunity Type a required field on the initial Opportunity page layout and use automation to update the record type based on the Opportunity Type.

The requirement has two phases: first, show users only the fields needed to create the Opportunity; after save, show the full record page based on the Opportunity type. This can be handled by using a required Opportunity Type field first, then automation can update the Opportunity record type. Salesforce page layouts can be assigned by profile and record type, which allows different Opportunity types to show different layouts after the record type is set.

B is incomplete because it only mentions page layouts based on profile, not dynamically changing the layout based on Opportunity Type after creation. C is incorrect because sharing rules control record access, not field display. D relies on users manually expanding sections and does not meet the streamlined requirement.

The correct answers are A and B .

The requirement is to display a visual flag image based on Case Priority. Salesforce’s own sample image formula for Case Priority uses the IMAGE() function with CASE() to display green, yellow, or red flag images.

Both formulas are valid because:

A uses IMAGE() with nested IF() and ISPICKVAL() checks.

B uses IMAGE() with CASE() to return the correct image URL.

C and D are incorrect because they return only the image URL text, not the actual image. The formula must use IMAGE() to display a visual flag.

===========

The correct answer is B. Custom action.

The user wants to edit a record’s Status and enter a custom Due Date quickly from the record feed in the Salesforce mobile app. A custom action, specifically an object-specific quick action, can expose selected fields for fast updates on mobile. Salesforce documentation states that object-specific actions let users quickly create or update records in the context of a specific record, and the Salesforce mobile action bar displays actions in mobile places such as feeds and record pages.

Custom button and URL formula field are not the best mobile feed-editing tools. Custom quick access link is not the correct Salesforce feature for this requirement.

===========