Pass the Salesforce App Builder Platform-App-Builder Questions and answers with Dumpstech

The correct answer is B. The deployed permission set will only contain changes related to the change set.

When permission sets are included in change sets, the deployment carries permission settings related to the components included in the change set. The existing permission set in production is not completely overwritten as a whole object, and field-level security changes can be included when the relevant fields are part of the deployment. Salesforce documents permission sets and profile settings as access settings that can be included with change sets.

A is incorrect because the whole permission set is not simply wiped and replaced.

C is incorrect because field-level security can be deployed when included properly.

D is close in plain language, but the more accurate exam answer is that the deployed permission set contains only changes related to the change set.

===========

The correct answer is C.

The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.

So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.

A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.

===========

The correct answer is D. Custom Report Type.

A custom report type defines which records and fields are available in a report based on relationships between a primary object and related objects. Salesforce also references custom WITH or WITHOUT report types for reporting on related records.

Because DreamHouse Realty needs “with” or “without” reports involving a custom object and related lookup data, the app builder must create a Custom Report Type and define the object relationships.

Why others are incorrect:

A. Report Filters filter report results but do not define the reportable object relationship.

B. Row-Level Formula calculates values per row; it does not create with/without relationship reporting.

C. Report Bucket Field groups report values; it does not define related-object report structure.

===========

The correct answer is B. Add the standard Chatter feed component.

In Lightning App Builder, Salesforce provides a standard Chatter component. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed on a record page.

A is incorrect because a custom Chatter feed component is not needed.

C is incorrect because this does not come from the AppExchange/App College.

D is incorrect because Chatter feed is not added by using the standard related list component.

===========

The correct answers are A. Change the Lead Duplicate Rule details to Bypass Sharing Rules and D. Change the Lead Duplicate actions to Block on Create.

Because Lead OWD is Private, users may not have access to existing duplicate Lead records. Salesforce duplicate rules can be configured to bypass sharing rules, allowing the duplicate rule to check possible duplicates regardless of ownership or user visibility. Salesforce Help specifically explains duplicate prevention can block users from creating duplicate records whether or not they have access to the existing record.

D is also required because detecting a duplicate is not enough. The duplicate rule action must be set to Block on Create to stop users from saving new duplicate Leads.

Why others are incorrect:

B is incorrect because Lead Assignment Rules assign leads; they do not prevent duplicate creation.

C may expose more Lead records, but changing OWD from Private to Public Read is not the best security-safe solution when duplicate rules can bypass sharing.

===========

The correct answers are A. Tabs and B. Related record.

Tabs help create a more condensed Lightning record page by grouping information into separate tabbed sections instead of showing everything in one long page. Salesforce Lightning App Builder allows app builders to add, remove, reorder, and customize components on Lightning record pages.

Related Record is required because service agents want to modify the associated Contact and Account directly from the Case Lightning record page. Salesforce Help states that the Related Record component uses quick action metadata and requires an associated quick action to update records.

Why others are incorrect:

Path is used to guide users through stages or status values, not to edit related Account or Contact records.

Rich Text displays formatted guidance or static text; it does not provide editable related-record functionality.

The correct next steps are A. Add the fields to the page layout on the object and C. Create a permission set for access to the object and fields .

This is a two-part access problem in Salesforce: users need both security access and user-interface exposure . Creating a custom object and fields in Schema Builder only creates the metadata. It does not automatically guarantee that end users can see, create, edit, or use those records and fields.

C is required because object permissions define the base-level access users have to records for an object, such as create, read, edit, and delete. Salesforce also uses field permissions / field-level security to control whether users can view or edit individual fields. Permission sets are the correct modern mechanism to grant object and field permissions to selected users without changing their base profile.

A is also required because page layouts control the organization of fields on record detail and edit pages. Even if a user has field-level access, the field must be placed on the relevant page layout for normal record-page visibility and editing in the UI. Salesforce specifically separates field-level security as the access-control layer and page layouts as the UI organization layer.

B is incorrect because “Allow Reports” only makes the object available for report creation; it does not grant users object CRUD access or field-level visibility. D is incorrect because data types are assigned during field creation, not after, and choosing a data type does not grant user access.

The correct answers are A. Create a child record, C. Update a related record, and D. Send an email alert.

Process Builder was designed to automate repetitive business actions. Salesforce documentation describes Process Builder as a tool for automating tasks, emails, and record updates.

Process Builder can improve productivity by performing actions such as:

Create a child record — Process Builder can create a record when criteria are met.

Update a related record — Process Builder can update the record that started the process or related records.

Send an email alert — Salesforce documentation specifically states that a process can send an email by using an email alert.

B is incorrect because “Start an additional message” is not a standard Process Builder productivity capability.

E is incorrect because Process Builder does not delete related records as a standard declarative action.

===========

To display a weather map component only when a house is scheduled for a listing, the app builder should use Component Visibility in the Lightning App Builder.

Component visibility allows setting filters so components appear conditionally based on field values or other conditions.

Salesforce documentation states that conditional visibility rules control when a component is displayed dynamically on a Lightning page. (Salesforce Help)

B. Field-level security controls access to fields, not component visibility.

C. Formula field only calculates values but does not control component display directly.

D. Sharing rules control record access, not UI components.

===========

The correct answer is C. Enhanced List.

Salesforce documentation states that the Enhanced List related list type shows up to 10 fields and allows users to resize columns, sort columns, perform mass actions, and wrap text. This exactly matches the requirement: users need to see ten fields and need the ability to sort and wrap text on related lists.

D. Basic List is incorrect because the Basic List type shows fewer fields and does not provide the enhanced related-list behavior required here. A. List View and B. List Class are not the correct Related List Lightning component type for this requirement.

===========