The Rebate Member Product Aggregate object is the standard aggregation object used by Rebate Management to store summarized transaction information for members, products, payout periods, and rebate types.

Salesforce explicitly permits administrators to add custom fields to the Rebate Member Product Aggregate object when additional analytical or aggregation dimensions are required. For example, administrators can add fields representing country, region, industry segment, or other organization-specific criteria and use those fields when aggregating transaction data.

This makes the object particularly relevant to rebate analytics. Rebate Program Analysis evaluates program performance across areas such as member performance, product sales, rebate types, tiers, quantities, revenue, and payout. The aggregate records provide the summarized transactional foundation required for this type of analysis.

Program Rebate Type and Program Rebate Type Benefit are primarily configuration objects defining calculation and benefit rules. Rebate Program represents the overall incentive program. They are important to rebate processing but do not serve as the standard customizable aggregate transaction structure.

Therefore, Rebate Member Product Aggregate is the appropriate object when custom fields are required to enrich rebate-program analysis.

Study Guide references/topics: Configure and Build — Rebate Management; Analytics for Manufacturing; Rebate Member Product Aggregate; Rebate Program Analysis; Custom Analytics Dimensions.

This requirement combines visit execution, task standardization, and measurable outcomes, which maps directly to Partner Visit Management, Action Plans, and Generic Visit Key Performance Indicators.

Partner Visit Management allows sales managers to plan distributor or partner visits, assign field representatives, establish visit contexts, and capture business information. Salesforce explicitly identifies negotiating Sales Agreement renewals as an example of a task that can be performed during distributor visits.

Action Plan Templates provide repeatability. Administrators or managers can define a standardized group of visit tasks and associate the resulting action plan with each visit. This ensures representatives consistently perform the activities required by the business.

Generic Visit KPIs provide the measurement layer. They capture expected and actual values associated with assessment indicators, enabling management to evaluate whether visits are achieving their intended objectives. Salesforce's documented Partner Visit Management workflow specifically combines tasks, assessment indicators, Generic Visit KPIs, and Action Plans.

Forecasting and CRM Analytics can support broader analysis but do not replace standardized visit execution. Experience Cloud and Service Console address different engagement and service requirements.

Study Guide references/topics: Configure and Build — Partner Visit Management; Action Plans; Visit Tasks; Generic Visit KPIs; Assessment Indicators.

An external object is appropriate when Salesforce users need access to information maintained in an external system without physically copying that information into Salesforce.

Salesforce Connect provides this architecture by allowing users to view, search, and—in supported configurations—modify information stored outside the Salesforce org through external objects. Salesforce specifically identifies ERP information as a common use case: instead of synchronizing ERP records into standard or custom Salesforce objects, the external data can be accessed in real time through the external system's service interface.

This design directly meets UC's stated constraint that order information must not be replicated. The ERP remains the system holding the order data, while Salesforce exposes the relevant records to the sales team in the context of the customer's account.

Using the standard Order object would generally require the order records to be created or synchronized into Salesforce. A custom object has the same fundamental issue and additionally introduces unnecessary custom data modeling.

Salesforce also identifies integration with ERP systems as a core Manufacturing Cloud architectural requirement because manufacturing organizations commonly maintain operational transactions in back-office platforms.

Study Guide references/topics: Design — Integration Architecture; ERP Integration; Salesforce Connect; External Objects; Systems of Record.

Mobile testing must be performed with users whose access configuration accurately represents the intended production mobile personas. Among the choices, B reflects the necessary testing principle: mobile test users must have the permissions and access required to exercise the mobile implementation.

Current Manufacturing Cloud supports Manufacturing objects, including Sales Agreements, in the Salesforce mobile experience when administrators enable the required objects and configure the corresponding mobile layouts. Salesforce specifically documents improved mobile support for Manufacturing Cloud objects and identifies Sales Agreement as an example of an object that can be enabled in the Salesforce Mobile App.

Sales Agreement page configuration also includes Mobile & Lightning actions such as Submit for Approval, demonstrating that Sales Agreement workflows are no longer inherently desktop-only.

Testing should therefore include representative users, appropriate permissions, object visibility, mobile layouts, record access, and authentication/API access. Current Salesforce guidance also identifies API Enabled access as relevant to operation of the Salesforce Mobile App.

A Wi-Fi connection is not inherently required; mobile access can use supported network connectivity. Likewise, the premise that Sales Agreements cannot be accessed from mobile is no longer consistent with current Salesforce functionality.

Study Guide references/topics: Validate and Deploy — Mobile Testing; User Permissions; Sales Agreement Mobile Experience; UAT and Cross-Device Validation.

The Account Insights dashboard in Advanced Account Forecasting Analytics is designed for detailed account-level analysis of forecasts, actual performance, forecast composition, products, and configured dimensions. Salesforce specifically describes Account Insights as supporting analysis of account performance against forecasts and analysis based on custom dimensions.

The Advanced Account Forecasting Analytics app can be configured to include custom dimensions from the Advanced Account Forecast Fact object. Salesforce allows selected custom dimensions to become part of the analytics application, enabling users to analyze forecast information according to business-specific dimensions rather than being limited to standard product and account structures.

The Forecast Analysis dashboard has a related but distinct purpose. It focuses primarily on forecast accuracy, adjusted forecasts, actual-versus-forecast variance, forecast trends, and the magnitude of adjustments over time. It is therefore the appropriate destination when the primary question concerns forecasting accuracy rather than a dimensional deep-dive into a specific account.

Account Health provides higher-level health and performance indicators. Account Insights supplies the required detailed analysis across forecast, actual, and dimensional information.

Study Guide references/topics: Configure and Build — Advanced Account Forecasting Analytics; Account Insights; Custom Dimensions; Forecast Facts; Forecast versus Actual Analysis.

Sales Agreements are the primary Manufacturing Cloud capability for managing predictable run-rate business. Salesforce describes Sales Agreements as a mechanism for tracking and managing long-term purchasing negotiations with customers, distributors, and suppliers while maintaining visibility into planned and actual commercial performance.

A Sales Agreement creates a time-phased representation of recurring business. Account managers can define expected products, quantities, revenue, prices, and schedule periods and then compare those planned values against actual customer orders. This structure provides manufacturers with substantially greater predictability than repeatedly representing recurring purchases as unrelated Opportunities.

Opportunities remain appropriate for new or uncertain business that is progressing through a sales pipeline. They answer questions about potential deals and sales stages. Run-rate business, however, represents an established continuing commercial relationship where planned-versus-actual performance is the central concern.

Manufacturing Cloud is specifically designed to complement opportunity-driven selling with Sales Agreements for these recurring relationships. Account forecasting can subsequently consume information from Sales Agreements, Opportunities, Orders, and other sources to produce a broader demand forecast.

Study Guide references/topics: Design — Run-Rate Business; Sales Agreements; Long-Term Customer Commitments; Planned versus Actual Business.

The Sales Agreement provides the consolidated view required for long-term run-rate business. Salesforce defines a Sales Agreement as a long-term agreement between a manufacturer and a customer for the continued purchase and sale of products. It gives sales teams visibility into products, prices, quantities, planned revenue, actual revenue, and performance across the agreement period.

The agreement's duration can be divided into schedules, while Sales Agreement Products represent product- or category-level information across the agreement. Sales Agreement Product Schedules contain quantity, revenue, and pricing values for individual schedule periods.

For detailed operational analysis, users access the Agreement Terms tab on the Sales Agreement record. Salesforce states that this table displays revenue and quantity metrics across products and schedules and allows users to compare planned and actual performance. Actual Quantity and Actual Amount are stored at schedule level and aggregated into total actual values at the Sales Agreement Product level.

Contracts represent business terms but do not provide the Manufacturing Cloud Sales Agreement planning grid. Rebate Management, Account Manager Targets, and Account Forecasting serve separate business processes.

Study Guide references/topics: Configure and Build — Sales Agreements; Agreement Terms; Sales Agreement Products; Schedules; Planned versus Actual Performance.

Enabling Service Console for Manufacturing at the organization level does not by itself provide individual service agents with all required functionality. Salesforce requires the appropriate permission sets to be assigned based on the user's role and the components that the user needs to access.

For service agents, the Service Console for Manufacturing permission set provides access to the Manufacturing service console itself. The Industry Service Excellence permission set provides access to the underlying Industry Service Excellence capabilities used by console components. Salesforce explicitly lists these permission sets in its Service Console for Manufacturing access configuration.

This separation follows Salesforce's permission architecture: enabling a feature makes the functionality available within the org, while permission sets determine whether a particular user can use that functionality.

Adding a component to an existing Service Console page does not grant the required object and feature permissions. Likewise, building a new custom permission set is unnecessary when Salesforce supplies the standard functional permission sets intended for this persona.

The correct implementation is therefore to assign both the Service Console for Manufacturing and Industry Service Excellence permission sets to the service agents.

Study Guide references/topics: Configure and Build — User and Permission Setup; Service Console for Manufacturing; Industry Service Excellence; Manufacturing Service Security.

Under current Salesforce permission-set behavior, option A is the valid configuration among the choices provided. Account Forecasting objects require the Manufacturing Account Forecast PSL, which Salesforce identifies as the permission set license providing access to Account Forecasts and related objects.

Salesforce recommends cloning a permission set when additional permissions must be incorporated. A cloned permission set begins with the same license association and enabled permissions as the source, after which the administrator can configure the required field-level access.

For a new custom field, Read access is controlled through field-level security. Current Salesforce documentation explicitly states that field-level security through Object Manager can be set on custom permission sets created for the org. This makes cloning the Manufacturing Account Forecast permission set and extending the clone the appropriate approach.

Options B and D specify the Salesforce license rather than the Manufacturing Account Forecast entitlement. Salesforce states that a permission set associated with a specific license can contain only permissions entitled by that license. Option C does not follow the current custom-permission-set model for extending field-level access.

Therefore, under current Salesforce configuration standards, A is the valid action among the listed options.

Study Guide references/topics: Configure and Build — Account Forecasting; Permission Set Licenses; Manufacturing Account Forecast PSL; Custom Fields; Field-Level Security.

Salesforce explicitly states that changing the Team Member Hierarchy Type for Account Manager Targets causes all existing targets to become read-only. This behavior protects previously distributed target structures from being modified after the hierarchy model used to determine team membership has changed.

Manufacturing Cloud supports two relevant hierarchy models. Forecasts Hierarchy derives team relationships from the forecasting hierarchy configured in Salesforce. Manager Hierarchy instead relies on the Manager field configured on individual User records. When the hierarchy is switched, the organizational relationships used for allocation and target distribution can differ materially. Existing targets therefore cannot simply continue operating under assumptions established by the previous hierarchy.

Salesforce does not delete access to the targets, nor does it return them to Draft status. Historical targets remain available for visibility, reporting, and reference, but Salesforce prevents further modifications by making them read-only.

Administrators should therefore determine the appropriate team hierarchy before large-scale target creation and distribution whenever possible, because changing this setting has a direct effect on all targets already established.

Study Guide references/topics: Configure and Build — Account Manager Targets; Team Member Hierarchy; Manager Hierarchy; Forecasts Hierarchy; Target Administration.