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

The correct answers are A. Lightning App Builder and D. Quick Action.

A Lightning component can be exposed for use in Salesforce pages through supported targets such as App Page, Home Page, and Record Page, which are configured through Lightning App Builder. Salesforce developer documentation also confirms that components can be configured as quick actions using targets such as lightning__RecordAction or lightning__GlobalAction .

C. Validation Rule is incorrect because validation rules are business logic formulas, not places where Lightning components are placed or rendered. B. Time Failure is not a valid Salesforce area for using Lightning components based on the given option wording.

Actions and Related Records identifies an after-save record-triggered flow . Salesforce states that this optimization should be selected when automation must perform actions after the triggering record has been saved, including updating related records, creating records, and sending notifications or email. The flow can trigger when an Opportunity changes to Closed Won, reference the related Account and Account owner, perform any required related-record operation, and invoke the appropriate email action. Fast Field Updates is a before-save configuration optimized only for changing fields on the triggering record itself. A validation rule cannot invoke an autolaunched flow, and a Screen Flow requires user interaction. Because this automation requires post-save related-record processing and an email notification, D is the Salesforce-supported architecture.

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

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.

===========

A Global Picklist Value Set is used when the same picklist values must be reused across multiple objects and fields. Salesforce states that global picklist value sets let admins share values across objects and custom picklist fields.

Why not others:

A. Shared Custom Field is not a Salesforce feature for this requirement.

C. Dependent Picklist controls values based on another field.

D. Related Picklist is not the correct Salesforce feature.

===========

The correct answer is D. Accordion.

For an object with 100+ fields, the app builder should avoid one large monolithic Record Detail area. Salesforce Trailhead explains that Dynamic Forms breaks the Record Detail component into individual field and section components, which can be placed in separate tabs and accordion sections.

Salesforce also states that moving lower-priority fields into tabs or accordion sections can improve page performance because the content is not visible when the page first loads.

A. Highlights panel is for key record fields and actions at the top of the page. B. Record detail would keep fields together in one large block. C. Field section groups fields, but the better component for breaking a large page into collapsible organized areas is Accordion.

===========

Page layout visibility depends not only on the existence of the deployed page-layout metadata but also on the layout assignments associated with profiles and, where applicable, record types. Salesforce documents that page layout assignments are profile metadata and that deployments can affect or remove assignments when the required profile, record type, and page layout metadata are not included together. After deployment, the app builder should therefore verify and update the page layout assignments so users receive the intended layout containing the new fields. Redeploying the same components without correcting the assignment does not address the configuration issue. Recreating the fields is unnecessary because deployment already created them. Field-level security controls whether users may access fields, but the question specifically identifies their absence from the assigned page layout.

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

The correct answer is C. To make a Contact’s Twitter profile available in the Salesforce mobile app, the app builder should add the Twitter component to the mobile Lightning record page. Salesforce guidance states that to make Twitter accessible on Account or Contact record pages and in the Salesforce mobile app, add the Twitter component in Lightning App Builder.

Why others are incorrect:

A is wrong because mobile navigation is for navigation items, not displaying a Contact Twitter profile.

B is unnecessary because Salesforce provides the component declaratively.

D may show a link, but it does not provide the standard Twitter profile component experience.

===========

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

To add Chatter feed functionality to a custom object Lightning record page, the app builder should use the standard Chatter component in Lightning App Builder. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed combination on a record page.

A is incorrect because no custom Chatter feed component is required. B is incorrect because related lists do not add the Chatter feed. D is incorrect because the standard Chatter component is already available; an AppExchange component is unnecessary.

===========

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.

===========

The correct answer is C. Internal profiles.

When a new custom field is created using Schema Builder, Salesforce sets field-level security by default as visible and editable for internal profiles. This does not mean every possible profile, such as external/community profiles, automatically gets access. Salesforce Help specifically notes this default behavior for fields created in Schema Builder.

===========