Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (SP25)

The two reasons to create an unmanaged package are to distribute open-source projects on the AppExchange and to deploy from a Developer Edition environment. An unmanaged package is a collection of components that can be installed in any Salesforce org but cannot be upgraded or controlled by the developer. An unmanaged package can be used to share open-source projects or to deploy components from a Developer Edition environment to another org.

Given the need to automate a welcome email including a customized survey with customization requirements and a tight timeline, the best approach is:

Use Salesforce Flow to build the survey declaratively to meet the criteria and send it to the customer as an email (B). Flow is a powerful tool for automation in Salesforce, allowing the creation of complex workflows and user interactions without needing to write custom code. It can be used to build a survey and integrate it with email services for automated dispatch.

Working with a developer to create custom Apex and LWC (A) might meet the criteria but would not align with the limited time frame. Managed (C) and unmanaged packages (D) from AppExchange can provide pre-built solutions, but they may not offer the needed customization or could require more setup time than building directly in Flow.

Reference for automating processes with Salesforce Flow:

Salesforce Flow: https://help.salesforce.com/articleView?id=sf.flow_considerations_design.htm &type=5

Lookup is the type of relationship that would be set up to meet the specification of pairing experienced Realtors with new Realtors. According to the Salesforce documentation, “A lookup relationship creates a loose association between objects. The lookup field allows users to select a record from another object.” Indirect lookup is used for junction objects on different platforms. Many-to-many is not a type of relationship, but a result of using junction objects. Master-detail is used for creating parent-child relationships.

The validation rule should check if the user role is not Marketing, and if the Retail Opt In field has been changed to Yes. The ISCHANGED function returns true if the field value has been changed, and the ISPICKVAL function returns true if the field value matches a specified picklist value. 

 The app builder needs to have NOT(ISBLANK([Lead].OwnerId)) in the criteria to ensure the process runs without error. This formula checks if the OwnerId field on the Lead object is not blank, which means that the lead is owned by a user or a queue. This will prevent the process from running on leads that are not owned by anyone, which could cause an error. Option A, B, and C are not formulas that can ensure the process runs without error.

The solution that the app builder should configure to meet these requirements is creating three lead record types each with its own page layout containing the relevant fields. This way, the app builder can customize the fields and sections that appear on each record type based on the source of the lead. Option B is incorrect because creating a partner community and a record type for web and trade show leads does not address the requirement of collecting information that is unique to each type of lead, as partner community users may have different fields and layouts than internal users. Option C is incorrect because creating three sections on the lead layout and instructing users to collapse the non-relevant fields does not address the requirement of collecting information that is unique to each type of lead, as users may still see or enter data in the wrong fields. Option D is incorrect because creating custom page layouts for each type of lead only containing the relevant fields does not address the requirement of collecting information that is applicable to all sources, as users may miss some common fields.

To allow quick editing of a record's status and entering a due date from the record's feed in the Salesforce Mobile App:

A. Custom action. This option enables users to perform specific tasks directly from the record page in the Salesforce Mobile App, such as editing fields.

Steps to create a custom action:

Navigate to Setup → Object Manager → select the relevant object.

Click Buttons, Links, and Actions → New Action.

Set Action Type to 'Update a Record'.

Configure the action layout to include the Status and Custom Due Date fields.

Add the action to the Salesforce Mobile layout.

This setup provides an efficient way for users to update key fields without navigating away from the record feed.

For detailed setup instructions, see Salesforce's documentation on Creating Quick Actions.

For tracking whether contracts have been sent for Opportunities:

D. Checkbox. This field type allows users to clearly indicate (Yes/No) whether a contract has been sent. This binary nature of checkboxes makes it simple to filter and report on Opportunities based on whether a contract was sent.

Steps to configure this field:

Navigate to Setup → Object Manager → Opportunity.

Click Fields & Relationships → New → Checkbox.

Define the field with a label (e.g., Contract Sent).

Set the default value to false (unchecked).

Add the field to the relevant page layouts.

This setup facilitates accurate reporting and ensures that opportunities cannot be marked as "Closed Won" without indicating whether a contract was sent.

For guidance on creating fields, see Salesforce's documentation on Custom Field Creation.