Free Salesforce-Accredited-Agentforce-Manufacturing-Professional Practice Test Questions (2026)

Explanation:

Why A is correct:
When an enterprise manages its transactional data (such as orders and contracts) entirely within an external ERP system like SAP rather than natively inside Salesforce, Salesforce orders cannot be automatically tracked to update actuals. Instead, actual quantities and revenues must be synchronized or uploaded from the external system into Manufacturing Cloud via APIs or batch integration tools. Therefore, the Manually using API upload (or Manual/API-based actuals calculation mode) must be selected to accommodate external data feeds.

Why B and C are incorrect:

Automatically from direct orders (C) and Automatically from orders through contracts (B) require orders and/or contracts to be natively created and processed directly within Salesforce so that internal triggers or batch jobs can evaluate actuals against sales agreements automatically.

Since the system of record for orders and contracts is SAP, these native automation modes will not capture the external transactions properly without an integration mechanism feeding data via API.

Reference:
According to Manufacturing Cloud integration architecture guidelines, when core transactional data resides in an external ERP like SAP, actuals calculation modes must rely on external synchronization or API uploads to reflect true performance figures against sales agreements.

Explanation:

The Forecast Analysis-History dashboard in the Analytics for Manufacturing app is used to analyze changes made to forecasts over time, including forecast adjustments. It helps users understand how forecast values have been modified compared with earlier forecast submissions or periods.

Why the other options are incorrect:

A. Forecast Analysis-Accuracy — Incorrect.
This dashboard focuses on forecast accuracy, such as comparing forecasted values with actual results. It is not primarily used to track forecast adjustments.

B. Account Health — Incorrect.
Account Health provides insights into the overall health and performance of customer accounts rather than tracking changes to forecasts.

C. Forecast Analysis-History — Correct.
This dashboard provides historical analysis of forecasts and is the appropriate dashboard for tracking forecast adjustments.

Explanation:

Why The Account Health dashboard focuses on overall account performance, total revenue generation, and health scores rather than deep C is correct:
In the Advanced Account Forecasting Analytics app (CRM Analytics for Manufacturing Cloud), the Forecast Analysis dashboard is specifically designed for deep-dive analysis. It allows business users to evaluate forecast trends, track accuracy (such as MAPE metrics), and break down forecasts and actuals across various filters and custom dimensions (such as region, product category, or custom attributes).

Why A is incorrect:
The Account Health dashboard focuses on overall account performance, total revenue generation, and health scores rather than deep metric breakdowns by custom dimensions.

Why B is incorrect:
The Account Insights dashboard provides high-level summaries and key indicators regarding account behaviors and trends, but it is not the primary deep-dive dashboard built for analyzing granular forecast metrics against custom dimensions.

Reference:
According to Salesforce CRM Analytics documentation for Manufacturing Cloud, the Forecast Analysis dashboard provides the interactive lenses and faceted filters required to inspect forecasted quantities versus actuals sliced by custom dimensions.

Explanation:

In Salesforce Manufacturing Cloud Account Manager Targets, changing the Team Member Hierarchy Type affects how targets are structured and rolled up through the hierarchy.

When the hierarchy type is changed from Forecasts hierarchy to Manager hierarchy, the existing account manager targets are reset to Draft status. This allows the administrator to review and adjust the existing targets according to the new hierarchy structure before they are finalized.

Why the other options are incorrect:

A. Status for all existing targets will become Read-only — Incorrect.
Changing the hierarchy type doesn't make existing targets read-only.
B. All access to existing targets will be deleted — Incorrect.
Existing targets aren't deleted or stripped of access. Their status is changed to accommodate the new hierarchy.
C. Status for all existing targets will become Draft — Correct.
Existing targets are moved back to Draft when the team member hierarchy type is changed.

Key exam point:
Changing Team Member Hierarchy Type → Existing Account Manager Targets become Draft.

Explanation

In the Forecast Formula Builder, each formula is its own record with a Start Period and an End Period. A formula applies only to the period range you set, and you add further formulas for other ranges.

To cover 13 months, you create one formula for periods 1-12 and a second formula for period 13, each with its own period range. Trailhead's setup walkthrough does the same thing, adding another formula after the first one for the remaining periods.

The formulas are applied after the data processing definitions run, so each range gets its own calculation logic.

Why the others are wrong

A: Validation rules enforce data quality rules on records. They don't calculate forecast values.
C: The builder has no "two-part formula" feature. Splitting by period range is done with separate formula records.
D: Approval processes route records for approval and have nothing to do with calculating forecasts.
E: Thirteen separate formulas would work, but it is unnecessary and not the recommended approach, since one formula can cover a whole range of periods.

Reference
Trailhead: Configure a Forecast Set (Forecast Formula section, with Start Period and End Period)
Trailhead: Configure Forecast Metrics and Formulas (Forecast Formula Builder)

Explanation:

In Advanced Account Forecasting, the forecast set is where an administrator defines the dimensions (context) the forecast is calculated against — account, product, and time period. Forecasting at a different granularity, such as the product hierarchy level (product category/family), is a forecast set configuration, not a code or field-level change.

Option C (Correct):
On the Advanced Account Forecasting Setup page, the administrator edits the forecast set to include the Product dimension at the desired hierarchy level (product category instead of individual product, for example). The Data Processing Engine (DPE) then generates forecasts at that level. This is the native, supported way to change forecast granularity.

Option A (Incorrect):
The forecast context isn't a single "forecast context field" that you repoint from Account Id to Product Category. Account and product are both dimensions within the forecast set configuration — you don't swap one for the other.

Option B (Incorrect):
No flow or custom automation is needed. Advanced Account Forecasting is designed to support multiple forecast dimensions out of the box; building a flow would be unnecessary customization and wouldn't integrate with the DPE-based forecast calculation.

Exam tip
For AP-213 Advanced Account Forecasting questions, remember the setup chain: Forecast Set (dimensions) → DPE definition (calculations) → forecast results. Any question about changing what you forecast by (account, product, category, time) points to the forecast set on the setup page. Flows and field edits are distractors.

Reference:
Salesforce Help — Set Up Advanced Account Forecasting and Forecast Sets (configuring forecast dimensions).

Explanation:

Why These Two Permission Sets Are Correct
Setting up Tableau CRM (now CRM Analytics) for Manufacturing requires two distinct types of access: general CRM Analytics administration and Manufacturing-specific analytics administration. These are granted by two separate permission sets.

C. Tableau CRM Plus Admin
This permission set grants the administrator access to the core CRM Analytics platform. It provides system permissions such as Manage Analytics, Create Analytics Apps, and Edit Analytics Dataflows. Without this, the admin cannot enable CRM Analytics or manage the underlying analytics infrastructure.

B. Manufacturing Analytics Admin
This permission set is specific to the Manufacturing Cloud analytics application. Salesforce documentation explicitly states that to set up Analytics for Manufacturing, the administrator needs both CRM Analytics Plus Admin and Analytics for Manufacturing Admin permission sets. This permission set provides the Manufacturing-specific access needed to install and configure the Analytics for Manufacturing app, including dashboards for Sales Agreements, Account Forecasts, and Account Manager Targets.

Why the Other Options Are Incorrect

A. Manufacturing Einstein Admin
This is not a standard permission set name in Salesforce. While Einstein Discovery is part of CRM Analytics, there is no "Manufacturing Einstein Admin" permission set. The correct Manufacturing-specific permission set is Manufacturing Analytics Admin (sometimes referred to as Analytics for Manufacturing Admin).

D. Einstein Analytics Plus User
This is a user-level permission set, not an admin permission set. It provides read-only or limited access to CRM Analytics features, but does not grant the administrative permissions needed to enable or set up the platform.

E. Manage Analytics
This is a system permission, not a permission set. It is one of the permissions included within the Tableau CRM Plus Admin permission set. It cannot be assigned to a user on its own.

Reference
Salesforce's official documentation on setting up Analytics for Manufacturing states: "To set up Analytics for Manufacturing and assign permission sets to users: CRM Analytics Plus Admin and Analytics for Manufacturing Admin."

Explanation

When setting up Advanced Account Forecasting (and related Manufacturing Cloud Intelligence dashboards), administrators configure Field-Level Security (FLS) on key objects such as:

Advanced Account Forecast Partner
Advanced Account Forecast Fact (and related objects like Advanced Account Forecast Set Use)
The primary purpose is to differentiate the forecast data that various users can view.

This allows different user profiles (e.g., account managers vs. regional managers) to have separate levels of visibility or edit access to specific forecast measures, dimensions, and values. For example:

Regional managers might have edit access to quantity and revenue measures.
Account managers might have read-only or no access to certain adjusted forecast fields.

This is a recommended security practice so that sensitive or role-specific forecast information is properly controlled.

Why the other options are incorrect

A — Activity data is unrelated.
FLS here controls forecast measures and dimensions, not activity records.

B — Providing basic access to the records themselves is handled primarily through object permissions and sharing rules.
Field-Level Security specifically controls visibility to the fields (i.e., the forecast data values) within those records.

References
Salesforce Help: Set Field-Level Security for Advanced Account Forecasting ("To differentiate the forecast data that various users can view, configure the field-level security…")
Salesforce Help: Advanced Account Forecasting Setup – Permissions and Security Settings ("Set field-level security to grant users separate levels of access to forecast values.")

Explanation:

When the Manufacturing Cloud Analytics App is installed, the Account record page includes embedded analytics dashboards that provide account-specific insights.

The two standard dashboards available by default are:

Account Agreement Performance
Displays sales agreement performance metrics for the selected account.
Helps users compare planned versus actual performance.

Forecast Analytics for the Selected Account
Provides forecast insights and trends specific to the account currently being viewed.
Supports account-level forecasting analysis and decision-making.

Why the Other Options Are Incorrect

A. Accounts agreement performance; Pricing analytics for the selected account
Pricing Analytics is not one of the default dashboards surfaced on the Account page after Analytics App installation.

C. Accounts agreement performance; Forecast analytics for all accounts
The Account page is contextual and displays analytics for the selected account, not for all accounts across the organization.

Exam Tip
For AP-213, remember that the Analytics App surfaces account-specific insights directly on the Account page:

✅ Account Agreement Performance
✅ Forecast Analytics for the Selected Account

If an option mentions "selected account" rather than "all accounts," it is often the correct choice for Account-page analytics.

Answer: B ✅

Explanation:

In Manufacturing Cloud Account Manager Targets, administrators can configure the measures used to evaluate account managers. If Sales Management wants to measure Customer Satisfaction (CSAT), the administrator should add CSAT as a value for the Measure field on the Account Manager Target object.
Because CSAT isn't one of the standard predefined measure types, its Measure Type should be set to Other.
So the configuration is:
Account Manager Target → Measure = CSAT → Measure Type = Other
This allows CSAT to be used as a target metric for account managers.

Why the other options are incorrect:

A. Incorrect — The relevant configuration is on the Account Manager Target object, and CSAT should be added to the Measure field, not the Measure Type field.
B. Correct — Add CSAT to the Measure picklist and classify its Measure Type as Other on the Account Manager Target object.
C. Incorrect — It refers to the Account Target object and the Type field rather than the Account Manager Target's Measure field.
D. Incorrect — The Measure Type should be Other, because CSAT is a custom/nonstandard measure rather than a predefined Measure Type.

Exam Tip:
For a custom Account Manager Target metric such as CSAT, remember:

Measure = CSAT
Measure Type = Other
Object = Account Manager Target

Answer: B.