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

The correct answer is A.

UC has three Lead sources: web, trade shows, and partners. Some Lead information is common to all, while other fields are unique to each source. The best configuration is to use Lead record types with separate page layouts so each type of Lead shows the fields relevant to that process. Salesforce documentation states that record types allow different business processes, picklist values, and page layouts for different users or record categories.

B is not ideal because it leaves irrelevant fields visible and relies on users to collapse sections. C unnecessarily creates a different Lead object for the partner community. D is incorrect because separate custom objects would fragment Lead management and prevent standard Lead functionality from being used consistently.

===========

The correct answer is C. AppExchange package.

The key word is daily. Salesforce’s native Data Export Service supports manual and scheduled exports, but Salesforce documentation states that backup files can be generated manually once every 7 days for weekly export or 29 days for monthly export, depending on edition. That does not meet an automatic daily backup requirement.

For daily automated backups, the app builder should recommend a backup solution from AppExchange. Report export is not an org backup, and refreshing a full copy sandbox is not a backup automation tool.

===========

To display Component records as children in a related list on Product, the relationship field must be created on the Component object and point to Product. A lookup relationship provides exactly this parent-child association while allowing the records to remain independently managed. Salesforce explains that a lookup field on a child object relates it to a parent record and that users viewing the parent can then see the child records through a related list. After creating the lookup from Component to Product, the app builder adds the Component related list to the Product page layout. A junction object is unnecessary because the requirement does not describe a many-to-many relationship. Option C places the relationship in the wrong direction, while a roll-up field does not create a relationship or related list. Salesforce

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

Use a Component visibility filter. The issue is not object access or field access. The Contact Lightning record page is shared, but one component should be hidden for users with the Marketing profile. Salesforce Lightning App Builder supports visibility filters on Lightning page components, so the app builder can conditionally show or hide that component based on user/profile criteria.

Why not the others? AppExchange is unrelated. Detail page layouts control field layout, not visibility of a Lightning page component. Field-level security controls field access, not whether a large component appears on a Lightning record page.

===========

Dynamic Forms allows an app builder to place individual fields and Field Sections directly on Lightning record pages and apply visibility rules to them. Salesforce documents that field visibility can respond dynamically to record field values, allowing fields to appear or disappear as users modify data. This produces a more contextual record experience without maintaining numerous page layouts. Multiple page layouts are generally tied to profiles and record types rather than reacting dynamically to field input. A Filtered Related List controls related records, not the visibility of primary record fields. Screen Flows provide guided interaction but are unnecessary when the requirement concerns dynamic presentation of normal record-page fields. Therefore, Dynamic Forms combined with visibility rules provides the most direct declarative solution for adapting record pages according to field values. Salesforce

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

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 answers are B. Assign the page to a combination of apps and profiles, C. Make the page the default homepage for specific apps, and E. Make the page the org default.

When activating Lightning pages, Salesforce supports assigning a page as an org default, assigning it to specific Lightning apps, and assigning it to combinations such as app and profile. Salesforce Trailhead also confirms that Lightning record page activation supports org default, app default, and app/record type/profile assignments.

A is incorrect because Lightning page activation uses profiles, not permission sets, for this assignment model.

D is incorrect because Lightning pages are not activated by role as a standard activation option.

===========

A custom field type change can substantially increase change-set deployment time because Salesforce may need to transform existing stored data to conform to the new field representation. Salesforce ' s official Change Sets Best Practices documentation specifically warns administrators to consider possible deployment delays when a change set includes custom field type changes. The documentation explains that these changes can require modifications across a large number of existing records and therefore can extend deployment for a significant period. Salesforce even recommends considering a manual field-type modification after deployment when avoiding the delay is important. Profiles may increase deployment complexity because they contain access metadata, but they are not the specific documented cause identified here. Dependent fields and roles likewise do not inherently produce the extended data-conversion processing associated with changing a field ' s underlying data type.

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

The formula must evaluate true when:

Stage = Negotiation/Review

Close Date < 1 week from today

Salesforce formula functions used:

ISPICKVAL() for picklist equality checks

AND() to combine multiple conditions

CloseDate < TODAY() + 7 to check the Close Date is within one week

Correct formula:

AND(

ISPICKVAL(StageName, " Negotiation/Review " ),

CloseDate < TODAY() + 7

)

Options A, C, D use invalid syntax (missing quotation marks, incorrect function structure).

Salesforce Help confirms correct syntax for picklist comparison and date arithmetic in formula fields. (Salesforce Help)

This formula evaluates true only when both conditions are simultaneously met.

===========

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========