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

The correct answers are B. AppExchange and D. Lightning Components.

Salesforce Trailhead states that custom Lightning components can be created with Lightning Web Components or Aura, and existing Lightning components can also be installed from the AppExchange. Custom components configured for Lightning App Builder appear in the Lightning Components pane and can be added to Lightning pages.

Why others are incorrect:

A. Import Wizard is a data import tool, not a source of UI components.

C. Apex Code provides server-side logic, but Apex itself is not a Lightning page component resource.

===========

An indirect lookup relationship is used when an external object must relate to a standard or custom Salesforce object and the external data does not contain Salesforce record IDs. Salesforce requires the parent Salesforce object to contain a custom field marked External ID and Unique . Values from the external object ' s indirect lookup field are matched against this external ID field to establish the relationship. Salesforce specifically states that indirect lookups link a child external object to a parent standard or custom object using a custom unique External ID field. TEXT(Id) does not create such a relationship key, and CASESAFEID() merely converts Salesforce IDs to their 18-character representation. A normal Salesforce Record ID is used for standard lookup relationships, not indirect lookups.

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

Use a Record-Triggered Flow optimized for Actions and Related Records.

Submitting a record for approval is an action in Flow. Salesforce provides a Submit for Approval action, and after-save record-triggered flows are used when the automation needs to perform actions or work with related records after Salesforce saves the triggering record.

Option A is wrong because Fast Field Updates is the before-save path, mainly for updating fields on the triggering record. It is not the right optimization for submitting an approval request. Option B still requires a custom button and manual user action. Option C is unrelated because this requirement is based on an Opportunity record change, not a platform event.

===========

The correct answer is B. Queue.

The approval request must go to department members who can approve overnight shipments. In Salesforce approval processes, routing an approval to a queue is appropriate when a group of users can own or act on the approval request and any one of the queue members can handle it. Salesforce approval documentation describes approval processes as automation that specifies each approval step, including who receives the approval request.

A queue is better than a role or hierarchy field when the request needs to be handled by a department group rather than a single manager or a specific user from a hierarchy field.

A. Role is less appropriate because roles are for hierarchy-based access and routing.

C. Hierarchy field is used when routing to a user identified through a manager-style field.

D. Public group is used for sharing and grouping users, but approval queues are the standard routing choice for a group of approvers in this scenario.

===========

The correct answer is B. Edit a record page using Lightning App Builder > Drag the component onto the page.

A custom Lightning component installed from AppExchange is configured on a Lightning record page through Lightning App Builder. Salesforce documentation states that Lightning App Builder supports custom Lightning components, including Aura and Lightning web components, and record pages are edited as Lightning pages.

The Page Layout editor is used for fields, buttons, related lists, and layout behavior, not for placing Lightning components on a Lightning record page. App Manager manages apps and utility bars, but the page canvas configuration is done in Lightning App Builder.

Text Area (Rich), commonly called a Rich Text Area field, is the appropriate Salesforce field type when users need formatted content rather than plain text. Salesforce ' s rich text editor supports formatting such as bold and italics, numbered and bulleted lists, hyperlinks, alignment, indentation, and embedded images. This makes it suitable for white-paper-style material containing structured text, lists, links, and graphics. A standard Text Area provides only limited plain-text content. Text Area (Long) increases the amount of text that can be stored but does not provide the rich formatting and image capabilities required here. An encrypted text area is intended to protect sensitive information and is unrelated to formatted document presentation. Therefore, Rich Text Area is the correct declarative field type.

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

The correct answers are C. My Domain must be deployed and D. The component is tagged for record pages instead of home pages.

Salesforce custom Lightning components must be properly configured before they appear in Lightning App Builder. Salesforce Trailhead explains that custom components configured for Lightning App Builder appear in the Lightning Components pane, and the component bundle must be compatible with Lightning App Builder and Lightning pages.

C is correct because Salesforce requires My Domain for adding custom Lightning components in Lightning Experience/App Builder scenarios. Salesforce Help notes that users cannot add a custom Lightning component without enabling and deploying My Domain.

D is correct because Lightning components must be exposed for the correct page type. A component exposed only for record pages will not appear for a Lightning Home page. Salesforce Developer documentation states that lightning__HomePage enables a component to be used on a Home page, while record-page-only configuration is separate.

Why others are incorrect:

A is incorrect because a custom tab is not required to add components to a Lightning Home page.

B is incorrect because “developer permission” is not the normal reason a downloaded component cannot be added to a Lightning Home page.

===========

The correct answer is C. Create a Partial Copy Sandbox and use a sandbox template.

A Partial Copy Sandbox includes metadata plus selected production data and supports the use of a sandbox template to control which objects and data are copied. This allows the app builder to exclude confidential custom objects. It also meets the weekly refresh requirement because Salesforce allows Partial Copy sandboxes to be refreshed every 5 days.

B. Full Copy Sandbox can use a sandbox template, but it does not meet the weekly refresh requirement.

A and D are incorrect because Developer and Developer Pro sandboxes are not the correct choice when the sandbox must include selected production data records through a sandbox template.

===========

A Partial Copy sandbox is specifically intended for testing scenarios that need representative production data without requiring an entire production dataset. Salesforce states that Partial Copy sandboxes contain production metadata plus a selected sample of production data defined through a sandbox template and explicitly identifies User Acceptance Testing, integration testing, and training as appropriate uses. The template also lets administrators select the objects required for testing and exclude sensitive or irrelevant data sets when necessary. Developer and Developer Pro sandboxes primarily copy metadata and do not automatically provide representative production data. A Scratch Org is a temporary source-driven development environment rather than the preferred UAT environment for actual business users and realistic production-derived data. Therefore, A is the appropriate sandbox type.

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

The correct answers are C. Users, D. Public Groups, and E. Roles and Subordinates.

Manual sharing is used when the org-wide default is private and users need to share individual records on a case-by-case basis. Salesforce documentation confirms that manual sharing allows users to share individual records with other users, public groups, and roles.

A public group can include users, roles, and roles with subordinates, which makes it useful when sharing records with departments or groups of people.

A. Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.

B. Private Groups is not the standard manual-sharing option tested here.

===========