Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers | Set: 8

The correct answers are A. Task, B. Email Alert, and D. Outbound Message.

In a Salesforce approval process, automated actions can be configured when a record is submitted, approved, rejected, or recalled. Salesforce approval process setup supports workflow action types such as tasks, email alerts, field updates, and outbound messages.

C. Invocable Flow is not one of the classic approval-process action types in this exam context. E. Decision Element is a Flow element, not an approval-process action.

===========

The correct answer is C.

A junction object is commonly created with two master-detail relationships. Salesforce documentation states that sharing access to a junction object record is determined by the user’s access to both associated master records and the sharing setting on the relationship fields.

Here, Account Interest is the junction object between Account and Interest. If users do not have read access to the Interest object, they cannot view the Interest records. Because access to the junction object depends on access to both master records, they also cannot view the associated Account Interest records.

Why not others:

A is wrong because lack of read access to Interest does not give read-only access automatically.

B is wrong because the user can still view the Account if they have Account access.

D is wrong because junction object access is not simply “show junction but hide Interest details.”

===========

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 answer is B. Feed Tracking.

DreamHouse Realty wants changes to selected fields, such as Asking_Price__c and Real_Estate_Agent__c , to appear prominently in Chatter. This is exactly what Chatter Feed Tracking is used for.

Salesforce documentation states that feed tracking is available for record fields and can be configured for custom objects. Salesforce guidance also says admins can enable feed tracking from Setup, select an object, enable feed tracking, and choose fields to track.

A. Topics is used for categorizing Chatter posts, not automatically tracking field changes.

C. Pin Field is not the Chatter feature for tracking field updates.

D. Publisher Actions are actions users can take from the publisher, not automatic field-change tracking.

===========

Global actions are designed to be available broadly, not only from one object’s record page. Salesforce Trailhead states that global actions can be placed anywhere actions are supported and can let users send email without leaving the page they are on.

This fits the requirement because users need a Send New Email action available from Leads, Contacts, and Accounts in the Salesforce mobile app.

Why others are incorrect:

A is incorrect because a global action layout does not automatically clone the default page layout.

B is incorrect because the Lightning Component Library is not the reason to use global actions.

C is incorrect because global actions are not record-specific; object-specific actions are record-specific.

===========

The correct solution is to add a Rich Text component to the Case Lightning record page and then use component visibility so it only appears when the related Account’s support level is Platinum.

Salesforce Lightning App Builder supports visibility rules that show or hide components based on field criteria. Salesforce documentation confirms that visibility filters on record pages rely on field data associated with the page’s object, and related lookup fields can be used in visibility-rule considerations.

This is the best declarative solution because the requirement is only to display a text notification. A custom Lightning Web Component or cloned Lightning page is unnecessary.

Why others are incorrect:

A is incorrect because assigning a Case page to “platinum accounts” is not the correct assignment model.

C and D are incorrect because custom Lightning Web Components add unnecessary development effort for a simple text notification.

===========

The correct answer is A. Web-to-Case is the Salesforce feature designed to let visitors submit case information from a public-facing website. Salesforce documentation states that Web-to-Case is set up by enabling the feature, creating and customizing a web form, and adding that form to a website.

Why others are incorrect:

B. Outbound message sends data out of Salesforce; it does not create cases from a website.

C. Screen flow could require extra site/guest-user setup and is not the standard feature for this requirement.

D. Email-to-case creates cases from inbound email, not directly from a public web form.