Explanation: An Approval Process is the appropriate functionality to ensure all free parts receive the marketing director's sign-off. It allows for setting up a process for record approval.

Explanation: Create a custom action is the recommended solution to meet the requirement of creating additional accounts to form a hierarchy from a Parent Account record. According to the Salesforce documentation, “Actions let users quickly create or update records, log calls, send emails, and more, in the context of a particular object.” A custom action can auto-populate fields based on the parent account and make it easier for users to create child accounts. Add Path on Account hierarchy, add a custom link on Account, and customize a Global Quick Action are not valid or feasible options.

Explanation: Send an email alert, update a related record, and create a child record are three capabilities of Process Builder that can improve productivity for the sales team. Process Builder can automate these actions based on criteria or events that occur on records or objects. Send an outbound message and delete a related record are not capabilities of Process Builder, but of other tools such as Workflow Rules or Apex.

Explanation: The functionality that should be used to set up packages is namespace. A namespace is a unique identifier that distinguishes one package from another and prevents naming conflicts with other packages or customizations. A namespace also allows developers to expose their code or components for use by other developers through APIs or web services. A description is not a functionality that should be used to set up packages, but a text field that provides information about the package contents or purpose. A description does not prevent conflicts with other packages or customizations. Allow sharing is not a functionality that should be used to set up packages, but a setting that controls whether users can share records owned by other users within their role hierarchy. Allow sharing does not prevent conflicts with other packages or customizations. Help setting is not a functionality that should be used to set up packages, but a setting that determines whether users can access help documentation for standard Salesforce features or custom features within a package. Help setting does not prevent conflicts with other packages or customizations.

Explanation:
The app builder should do three things to optimize mobile experience:
Use Global Actions to make it easy to perform vital functionality on mobile: Global actions are actions that allow users to create records or perform tasks from anywhere in Salesforce. They are displayed in various places in Salesforce mobile app, such as action bar, action menu, or publisher. By using global actions, the app builder can make it easy for the appraisal team to perform common tasks on mobile, such as creating a new appraisal record or logging a call.
Minimize the amount of formula fields and lookup fields to reduce page load time: Formula fields and lookup fields are types of fields that can affect the performance of Salesforce mobile app. Formula fields are fields that calculate a value based on an expression or formula. Lookup fields are fields that create a relationship between two objects and allow users to select a value from a list of records. Both types of fields can increase the page load time on mobile devices, especially if they are complex or reference many other fields. By minimizing the amount of formula fields and lookup fields, the app builder can optimize the mobile experience for the appraisal team.
Put the most important fields in the compact layout so they are easy to find: Compact layouts are layouts that display a record’s key information at a glance. They are used in various places in Salesforce mobile app, such as record highlights, list views, related lists, and lookup dialogs. By putting the most important fields in the compact layout, the app builder can ensure that the appraisal team can easily find the information they need on mobile devices. Option B and D are not things that an app builder should do to optimize mobile experience.

Explanation: Research and evaluate products available on AppExchange to send mass emails is the action that the app builder should take to meet the requirement of broadcasting an email to 7,000 contacts in Salesforce on a regular basis. AppExchange is a marketplace where app builders can find products or solutions that can extend Salesforce functionality. There are many products on AppExchange that can send mass emails without hitting the Salesforce limit. Request Salesforce increase the number of maximum daily emails, develop Apex code and Lightning web component to send daily emails, and export Contacts to a CSV file and use an email client to send the emails are not valid or recommended actions.

Explanation: Global actions can be accessed anywhere actions are pages, feed and Chatter groups. This is correct because global actions are not tied to a specific object, and they can be added to any page that supports actions, such as record pages, home pages, feed pages, and Chatter groups.

Explanation:
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.

Explanation: Data is unable to be deployed with change sets. Change sets are used to deploy metadata components such as custom objects, fields, workflows, reports, etc. from one Salesforce org to another. However, change sets do not include any data or records from the source org. Users will need to use other tools such as Data Loader or Data Import Wizard to migrate data between orgs.

Explanation: 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.

Explanation: For an app builder who needs to ensure all fields from the page layout are visible on a Lightning Record Page after using the Lightning Object Creator, the correct component to use is:
Record Detail (C). The Record Detail component automatically displays all fields that are included on the assigned page layout for the object. It is designed to reflect the layout configuration and is the simplest way to ensure all fields are presented as configured in the layout editor.
Highlights Panel (A) is used primarily to display key fields at the top of the record page, providing a summary view rather than full field visibility. Recommendations (B) is used for displaying prompts or suggestions and does not display record fields. Path (D) is useful for displaying stages in a process (like sales stages or service processes) and does not show field data directly.

Explanation: Updating the account search layouts search results columns displayed and updating the account search filter fields can improve an end user’s search experience by showing more relevant information and allowing more refined filtering. The view filter settings and the accounts tab columns displayed are not related to the search functionality.