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

The correct answer is C. Configure Campaign Hierarchies and Campaign statistics.

To understand return on investment for an advertising buy, Universal Containers should use Salesforce Campaigns, especially Campaign Hierarchies and campaign reporting/statistics. Salesforce campaign hierarchy documentation explains that child campaign metrics roll up to the parent campaign, and Salesforce campaign reports can include campaign-hierarchy statistics for aggregate values.

The private security model does not require changing the whole org to public. The business need is marketing ROI tracking, so Campaigns are the correct feature.

A is incorrect because an opportunity pipeline report does not directly track advertising campaign ROI.

B is incorrect because Account Hierarchies and roll-up summaries are not the standard solution for campaign ROI.

D is incorrect because changing to a public security model is unnecessary and weakens data security.

===========

The correct answer is C.

To show Component records as a related list on Product, the app builder should create a relationship field on the child object, Component, pointing to the parent object, Product. Salesforce documentation explains that when a lookup relationship is defined, the lookup field is added on one object and a related list can be shown on the associated object’s page layout.

A is unnecessary unless the requirement is many-to-many. B is incorrect because a roll-up summary does not create a related list. D is incorrect because the relationship field direction is wrong; the field should be on Component, not Product.

===========

The correct solution is to configure validation rules with help text/error messaging.

Validation rules are the right tool because they evaluate record data before save and stop the save when the record does not meet the defined conditions. They can enforce that a Case status is not changed back to an earlier value by using formula logic such as PRIORVALUE() and picklist checks. They can also require certain fields only when specific Case criteria are met by checking whether those fields are blank under those conditions.

Why the other options are wrong:

Dependent picklists control valid picklist values, but they do not enforce status progression or conditional required fields across all save paths. Approval processes are not the best fit for real-time save validation. Page layout required fields are UI-level requirements and are not flexible enough for criteria-based enforcement.

The correct answers are B. Flow Builder and D. Escalation rules.

Escalation rules are the most direct Salesforce Service feature for this requirement. They are designed to automate case escalation when cases are not resolved or not acted on within a defined time period. Salesforce documentation explains that escalation rule entries can use business hours, and escalation actions can send notification emails when the case escalates.

Flow Builder can also be used because record-triggered flows support scheduled paths, allowing automation to run after a defined time from a triggering record event. A flow can check whether the Case is still in New status and then send a notification. For strict business-hour calculation, the app builder must design the flow carefully around the correct time source/business-hour logic.

A is incorrect because validation rules only prevent invalid data from being saved; they do not wait four business hours and send notifications.

C is incorrect for the Platform App Builder context because Scheduled Apex is a programmatic approach, while declarative automation tools are available and preferred for this requirement.

===========

The correct answer is D. Universal Containers wants the real-time value of the Account’s Support Level picklist to appear on related Case records. The best declarative solution is a cross-object formula field on Case that references the related Account field.

Because Support Level is a picklist, the formula should use the TEXT() function to return the picklist value as text. Salesforce documentation states that cross-object formulas can reference fields from related objects, and Salesforce’s TEXT function supports picklist values in formulas.

Example formula concept:

TEXT(Account.Support_Level__c)

Why others are incorrect:

A is incorrect because the formula must be on Case, not Account.

B is incorrect because Case already relates to Account; a new lookup alone does not display the value.

C is incorrect because roll-up summary fields summarize child records; they do not copy/display a parent picklist value on child Case records.

===========

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.

===========

When deploying from sandbox to production using Change Sets, the following are critical considerations:

A. Transactions will revert if the deployment errors – Salesforce applies deployments as a single transaction; any failure rolls back the deployment to maintain org integrity.

D. Change sets do not include all components and may require manual configuration – Certain components, such as record data or some metadata, may need manual setup or additional deployment steps.

Salesforce documentation emphasizes that change sets cannot deploy everything and must be carefully reviewed before validation. (Salesforce Help)

B. Users being logged out is not required; deployments can occur while users are logged in.

C. Salesforce Connect does not automatically link environments; it is unrelated to change sets.

===========

The correct answer is A. Import Wizard.

Cloud Kicks needs to insert 25,000 records and use deduplication for a custom object. Salesforce Trailhead states that the Data Import Wizard can import data into custom objects and supports up to 50,000 records at a time, so 25,000 records fits within the Import Wizard limit.

Salesforce Help also states that the Data Import Wizard prevents duplicate custom object records by matching records against fields such as the custom object name or Salesforce ID.

B. Data Loader is not the best answer because Data Loader is better for larger or automated loads, but this question specifically requires deduplication and only 25,000 records. C. Lightning Object Creator creates objects from spreadsheets; it is not the correct deduplication import tool. D. Schema Builder is for creating and viewing data models, not importing records.

===========

The correct answers are B. Set organization-wide default to Private, D. Disable Grant Access Using Hierarchies, and E. Create a criteria-based Sharing Rule for the HR Department.

Set the Review object’s OWD to Private so review records are not visible to all employees by default. Organization-wide defaults define the baseline record access users have to records they do not own.

Disable Grant Access Using Hierarchies because this is a custom object and the requirement says only HR and the submitting employee should see the review. Salesforce allows this setting to be disabled for custom objects so managers higher in the role hierarchy do not automatically inherit access.

Create a criteria-based sharing rule for the HR department so HR can see the Review records even though the default access is private. Salesforce sharing rules are used to grant wider access beyond OWD.

Why others are incorrect:

A is not needed and a Master-Detail relationship to User is not the right access-control design.

C is incorrect because removing Review Read permission from non-HR users would also prevent the submitting employee from viewing their own submitted review.

===========

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.

===========