Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (Plat-Admn-202)

 A custom button, a validation rule, and record types can be used to meet the requirement of hiding the convert button on leads until the lead status picklist is set to qualified. The custom button can replace the standard convert button and invoke a validation rule that checks the lead status. The record types can be used to assign different page layouts with different buttons for different lead statuses

When configuring an approval process, the available initial submission actions (triggered when a record is first submitted for approval) include sending notifications, creating tasks, and sending outbound messages.

Why A (Outbound Message) is correct:Exact Extract:“Outbound messages can be configured as approval actions to send information to external systems when a record is submitted or approved.” — Salesforce Help | Approval Processes Overview

Why C (Task) is correct:Exact Extract:“Approval processes can create tasks for users as part of approval actions to ensure follow-up on record changes.” — Salesforce Help | Approval Actions

Why D (Email Alert) is correct:Exact Extract:“Email alerts can be sent automatically when a record is submitted, approved, rejected, or recalled.” — Salesforce Help | Approval Processes Overview

Why not B (Invocable Flow):Invocable Flows are not selectable as approval actions — they are used in Process Builder or Flow itself, not Approval Process configuration.

Why not E (Decision Element):Decision elements are Flow components, not part of the Approval Process action set.

 The app builder wants to create a formula field on an Account to include data from related Contacts but cannot find the relationship in the formula editor. This limitation occurs because formula fields in Salesforce cannot reference child records directly.

Option A (Unable to reference the child records): In Salesforce, formula fields can reference parent objects but not child objects. In this case, Contacts are child records of Accounts in a lookup relationship, and Account is the parent. This is why the formula editor does not provide access to the child records (Contacts) from the Account.

Formula Field Considerations

Option B (A master-detail relationship should be created): While master-detail relationships allow for roll-up summaries, creating a master-detail relationship is not applicable here since the standard Account-Contact relationship is a lookup, and changing it to master-detail is not possible.

Option C (Formula field limit reached on the Account object): This would limit the number of formulas but is not the root cause of the issue described.

Option D (More than 5,000 characters in the formula): This limit refers to formula field complexity, but it does not explain the inability to reference child records.

In summary, the limitation is due to Salesforce not allowing formula fields to reference child records.

The requirement is to auto-populate the “Last Maintenance Date” field on the Asset record whenever a Maintenance-type Work Order is closed. This can be achieved declaratively using Flow — specifically, a Record-Triggered Flow that updates the parent record (Asset).

Why D (Flow) is correct:Exact Extract:“Record-triggered flows can update related records when specific changes occur, such as when a Work Order’s status is updated to Closed.” — Salesforce Help | Record-Triggered FlowsIn this scenario, the flow can:

Why D (Flow) is correct:Exact Extract:“Record-triggered flows can update related records when specific changes occur, such as when a Work Order’s status is updated to Closed.” — Salesforce Help | Record-Triggered FlowsIn this scenario, the flow can:

Trigger when a Work Order is updated to “Closed.”

Check if Type = “Maintenance.”

Update the related Asset record’s Last Maintenance Date field with the Work Order’s Closed Date.

Why not B (Roll-up Summary):Roll-up summary fields can only summarize numeric or date values using MIN, MAX, COUNT, or SUM, but only on Master-Detail relationships. Work Order → Asset is a Lookup relationship, so roll-up summaries are not supported natively.

Why not A (Einstein Next Best Action):NBA provides recommendations, not field updates.

Why not C (Apex Trigger):Apex could achieve this, but Salesforce recommends Flow first as a best practice.

 Groups is available in the Chatter section of the navigation menu, not in the selected list for the navigation menu. According to the Salesforce documentation, “Groups appear in Chatter, not in Navigation Menu.” Groups is not available in the recent section of the navigation menu, nor is it included in the Smart Search items but unavailable on the navigation menu. Groups is unavailable in the selected list for the navigation menu.

The validation rule should be AND(ISNEW(), ISBLANK(Lead.Owner:User.Id)). This rule will prevent saving a new lead record if the owner is not a user. This will ensure that campaign members have a sales owner. Option A is incorrect because it will prevent saving any lead record if the owner is blank, which is not the requirement. Option B is incorrect because it will prevent saving an existing lead record if the owner is a queue, which is not the requirement. Option D is incorrect because it will prevent saving any lead record if the owner is a queue, which is not the requirement.

The app builder should use the Path feature to provide the functionality that the VP of Sales wants. The Path feature allows an app builder to create a visual representation of the stages in a business process, such as the Opportunity sales process. The app builder can also add key fields, guidance, and resources for each stage to help sales reps gather information and complete tasks4. Option A, C, and D are not features that can provide this functionality.

Schema Builder is a tool that presents a comprehensive view of all relationships in one place. It allows app builders to see how objects are connected and create new relationships. Lightning Object Creator, Object Manager, and Lightning Record Page are not tools for viewing relationships, but for creating objects, managing fields, and customizing record pages respectively.

To import leads while preventing duplicates:

B. Data Import Wizard is the appropriate tool. The Data Import Wizard in Salesforce includes functionality to check for duplicates based on matching records by certain criteria (like email or lead ID) during the import process, thus preventing duplicate lead records from being created.

More details on using the Data Import Wizard can be found in the Salesforce Data Import Wizard guide.

An AppExchange solution is a pre-built application or component that can be installed from the Salesforce AppExchange, which is an online marketplace for Salesforce products. AppExchange solutions can help you meet your business needs quickly and efficiently, without requiring much development effort or expertise. You can browse and search for AppExchange solutions by category, industry, rating, price, and more.