A permission set is the standard and most appropriate tool for granting additional permissions to specific users without changing their base profile. The administrator should create a permission set that grants "Read" object permission for Leads and the "View All" system permission for the Lead object. Assigning this permission set to the contractor will grant the required access to all lead records while leaving their existing profile and app access intact. This adheres to the principle of least privilege and is a scalable solution.

B. Adding an app or tab only controls visibility in the user interface; it does not grant the underlying object permissions or record access required.

C. A public group is a collection of users for sharing purposes; it does not grant permissions itself. It is used as a target for sharing rules.

D. Creating a new profile is inefficient. A user can only have one profile, and changing it could remove their necessary access to the project management app.

1. Salesforce Help, Permission Sets. "A permission set is a collection of settings and permissions that give users access to various tools and functions. Use a permission set to grant additional permissions to users without changing their profiles."

2. Salesforce Help, Object Permissions. This document lists "View All" as a specific object permission that can be enabled in a profile or permission set to grant a user read access to all records of that object, regardless of sharing settings.

The best practice for declaratively controlling Apex logic execution for specific users is to use a custom permission. The Apex trigger code would be written to check if the running user has this specific custom permission before executing its logic. An administrator can then create a permission set that includes this custom permission and assign it to the required users or profiles. This approach allows for flexible, declarative control without modifying the Apex code.

A. Process Automation Settings are org-wide configurations, such as setting a default workflow user, not for controlling trigger execution for specific users.

B. While a standard system permission could be checked, a custom permission is the correct, scalable, and purpose-built solution for custom application logic.

C. Apex Class Access controls whether a user can invoke methods from a class (e.g., via a custom button), not whether a trigger fires during their DML operations.

1. Salesforce Developer Documentation, Apex Developer Guide. "Custom Permissions". The guide states, "Custom permissions let you define access checks that can be assigned to users via permission sets or profiles... For example, you can define access logic in Apex that makes a button on a Visualforce page available only if a user has the appropriate custom permission." This principle applies directly to controlling trigger logic.

2. Trailhead, Salesforce Developer. "Apex Triggers" module, "Trigger Context Variables" unit. This module explains that triggers run in system context, but best practices often involve checking the running user's permissions for conditional execution.

3. Salesforce Help. "Custom Permissions". "You can use custom permissions to provide a way for administrators to grant access to custom processes or apps declaratively."

Flows deployed with change sets are inactive by default and need to be manually activated in the

destination org before they can run. Deploying or redeploying a flow with change sets creates a new

version of the flow in the destination org, which preserves the previous versions and allows for

rollback if needed. All flow dependencies, such as custom fields, objects, or variables, are

automatically added to the change set when a flow is added

Roll-up Summary field calculations occur after record-triggered flows, processes, and workflows in Salesforce's order of execution. When a new appointment record is created, the Flow will fire immediately upon record creation, but at that moment, the Roll-up Summary field on the parent record hasn't been updated yet. This means the Flow would send outdated appointment count information to the agent unless specifically designed to account for this timing issue.

A. Roll-up Summary fields work with both standard and custom objects when master-detail relationships exist.

B. Flows can be triggered from both standard and custom object records without restriction.

C. Roll-up Summary calculations do not prevent Flows from being triggered; they execute in sequence.

1. Salesforce Developer Documentation: "Triggers and Order of Execution" - Section on System Validations and Roll-up Summary calculations

2. Salesforce Help: "Considerations for Time-Dependent Actions and Triggers" - Process automation timing

3. Salesforce Architect Documentation: "Platform Events and Process Automation" - Execution order details

4. Salesforce Administrator Guide: "Roll-up Summary Fields" - Chapter on calculation timing

5. Salesforce Developer Guide: "Flow Builder" - Record-triggered flow execution context

Field-Level Security (FLS) controls whether a user can see, edit, and delete the value for a particular field on an object. This is managed through Profiles and Permission Sets. The administrator should configure the sales reps' profile to have 'Visible' access to the 'Profit' field and the partner consultants' profile to have 'Hidden' access. Alternatively, a permission set granting visibility to the field could be created and assigned only to the sales reps, providing a more granular and additive approach to permissions.

B. Record types control page layouts and picklist values. Hiding a field on a page layout does not prevent access via reports or the API.

C. Organization-Wide Defaults (OWDs) control record-level access (which records a user can see), not field-level access (which fields they can see).

1. Salesforce Help. (2024). Set Field-Level Security for a Single Field on All Profiles. "Field-level security settings let you restrict what fields users can view and edit based on their profile."

2. Salesforce Help. (2024). Permission Sets. "You can also use permission sets to grant access to... field-level security."

3. Trailhead. (2024). Data Security Module, Control Access to Fields Unit. "You can control the visibility of fields in any part of the app, including... reports... You can set field-level security through profiles or permission sets."

Roll-up summary fields have specific characteristics. They must be created on the master object in a master-detail relationship to aggregate data from detail records (B). Furthermore, the existence of a roll-up summary field on the master object creates a dependency that prevents the master-detail relationship from being converted to a lookup relationship until the field is deleted (C). These are fundamental considerations for data modeling in Salesforce.

A. The available roll-up types are COUNT, SUM, MIN, and MAX. AVG (Average) is not a standard function for roll-up summary fields.

D. Roll-up summary fields are calculated and updated asynchronously after a record on the detail side of the relationship is saved, deleted, or undeleted.

- Salesforce Help, "Roll-Up Summary Field". This document explicitly states, "You can create roll-up summary fields on any master object in a master-detail relationship." It also lists the available functions as COUNT, SUM, MIN, and MAX.

- Salesforce Help, "Considerations for Relationships". Under the section for converting relationships, it notes, "You can’t convert a master-detail relationship to a lookup relationship if the master object has a roll-up summary field that summarizes a field on the detail object."

- Salesforce Object Model and Customization, Trailhead Module "Data Modeling". Unit on "Create Object Relationships" covers the properties and limitations of roll-up summary fields.

The standard Salesforce solution for selling the same products at different prices is to use Price Books. The administrator should create a new "Retail" Price Book and add the products to it with their specific retail prices. When sales reps create an Opportunity for a retail deal, they will select this new Price Book. This ensures that when they add Opportunity Products (line items), the correct retail prices are used, leading to accurate sales data tracking for the new business channel without creating duplicate product records.

A. Creating new Product records for each price point is inefficient, creates duplicate data, and complicates inventory management and reporting.

B. An Order Process defines the stages for an Order. This is irrelevant to setting the correct price on the preceding Opportunity record.

D. Linking an Order to an Opportunity is good practice but does not solve the fundamental problem of ensuring accurate pricing on the Opportunity itself.

Salesforce Help, "Products, Price Books, and Schedules": This documentation states, "Price books let you create a custom collection of products with associated list prices for specific uses."

Trailhead, "Products, Quotes, and Contracts" module, "Set Up Products" unit: This module explains, "To sell a product, you have to add it to a price book with a price... You can have a standard price book and any number of custom price books."

Delegated administration allows administrators to assign limited administrative privileges to non-administrator users, enabling them to manage users within specific roles and subordinates. This feature is specifically designed for scenarios where certain users need to create, edit, and manage other users within their organizational scope without having full system administrator access. Division leaders can be granted the ability to manage users only within their division's role hierarchy, perfectly addressing Cloud Kicks' requirement for divisional user management autonomy.

B. Territory hierarchies are for organizing sales territories and account assignments, not for user management delegation.

C. Permission set groups bundle permissions for functional access but don't provide user management capabilities for specific divisions.

D. Profiles control object and field permissions but cannot grant selective user management rights limited to specific divisions.

1. Salesforce Help Documentation: "Delegated Administration" - Setup section, User Management subsection

2. Salesforce Administrator Guide: "Managing Users" - Chapter on Delegated Administration Groups

3. Trailhead Module: "User Management" - Unit on Delegated Administration

4. Salesforce Platform Administration Study Guide - Section 2.3: User Setup and Management

5. Official Salesforce Release Notes - Delegated Administration Enhancement Features

Salesforce Flow is the only declarative automation tool that can be triggered when a record is deleted. The administrator can create a record-triggered flow that initiates when a star record is deleted. This flow can then be configured to perform actions, such as sending a custom email notification to the relevant scientists. The notification can include details from the deleted record and identify the user who performed the deletion, fulfilling all aspects of the requirement.

A. Heroku is an external platform for building custom applications and is not a standard, declarative automation tool within Salesforce for this type of task.

B. Process Builder cannot be triggered by a record deletion event; it only works on record creation and updates.

C. Workflow Rules, like Process Builder, do not support triggers on record deletion. They are limited to record creation and update events.

1. Salesforce Help, Record-Triggered Flow. "A record-triggered flow starts when a record is created, updated, or deleted. The flow runs in the background."

2. Salesforce Architects, Record-Triggered Automation Decision Guide. "Use a record-triggered flow when you need to... perform actions after a record is deleted." The guide explicitly contrasts this with Workflow Rules and Process Builder, which cannot trigger on delete.

A Cross-Filter allows a report to be filtered based on the child records of the primary object without displaying the child records themselves. The administrator can create an Account report and add two cross-filters: one for "Accounts with Opportunities" (filtered by this year's close date) and another for "Accounts with Activities" (filtered for completed tasks in the last 30 days). This configuration will produce a list of only the Account records that meet both criteria, fulfilling the request precisely.

A. Joined Report: This would show blocks for Accounts, Opportunities, and Activities, which is explicitly what the request wants to avoid (no opportunity details).

C. Summary Report: This report type groups rows of data but does not provide the "with/without" filtering capability needed to check for related records.

D. Filter Logic: This applies to standard filters on the primary object's fields, not for filtering based on the existence of related child records.

1. Salesforce Help. (2023). Filter Reports by Child Objects with Cross Filters. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.reportscrossfilters.htm&type=5. (This article explains the use case for cross-filters, stating, "Use a cross filter to fine-tune your results by including or excluding records from related objects and their children, without having to write formulas or code.")

2. Salesforce Help. (2023). Report and Dashboard Objects. Reports and Dashboards REST API Developer Guide. Retrieved from https://developer.salesforce.com/docs/atlas.en-us.apianalytics.meta/apianalytics/analyticsapireportanddashboardobjects.htm. (The documentation on report metadata describes crossFilters as a component for filtering by related objects.)