Explanation:

Why CRM Analytics Needs a Dataflow (or Recipe) to Show Anything
CRM Analytics (formerly Tableau CRM / Einstein Analytics) does not automatically display every Salesforce object. The analytics app relies on datasets that are created and refreshed through dataflows (or recipes), which extract data from Salesforce objects, transform it, and load it into analytics datasets. If a Salesforce object isn’t included in the dataflow, it will not appear in the analytics dashboards—no matter how correct your Salesforce record data is.

Why “Not Added to the Dataflow” Is a Direct Cause
If the Sales Agreement object (and related objects) were never included in the CRM Analytics dataflow configuration, then the dataset driving “Sales Agreement dashboards” will not contain those records. Salesforce’s Analytics for Manufacturing setup guidance explicitly points to ensuring the correct data is available for Sales Agreements and that the analytics configuration includes the relevant Sales Agreement-related objects. If the object isn’t part of the flow, the dashboards don’t have a dataset to query—so the UI appears empty or incomplete.

Why “Dataflow Not Updated” Is Also a Direct Cause
Even if the Sales Agreement object was added at some point, CRM Analytics datasets will remain stale unless the dataflow runs after configuration changes or on its schedule. If users report “current Sales Agreement data” isn’t showing, one common root cause is that the dataflow hasn’t been run since recent changes, or it failed and therefore didn’t refresh the datasets. Salesforce provides standard documentation explaining that a dataflow job can warn/error and that dataset freshness depends on successful dataflow runs. An un-updated dataflow means dashboards show old snapshots rather than current data.

Why the Other Options Aren’t the Best Two

A. Linked to person accounts: person accounts can cause modeling complications, but it’s not the standard “two best causes” when an object’s data is simply missing from dashboards.

B. Only displayed in the grid: that’s a UI statement about Manufacturing Cloud pages, not a CRM Analytics data ingestion issue.

References:
Salesforce Help: Set Up Analytics for Manufacturing (instructions for adding analytics for Sales Agreements; implies dataset/dataflow configuration is required).
Salesforce Help: Data Required to Create the Analytics for Manufacturing App (lists Sales Agreement and related objects needed).
Salesforce Help: CRM Analytics dataflow warnings and errors (dataflow freshness depends on successful runs).

Explanation:

Flexibility and Context-Awareness of Embedded CRM Analytics Dashboards

The Manufacturing Agreement Performance and Manufacturing Product Performance dashboards are components from the CRM Analytics for Manufacturing app. When embedded into a Salesforce Lightning page using the Einstein Analytics Dashboard component, they possess intelligent, context-aware capabilities.

1. No Filter Required (B is Correct)
These dashboards are designed with contextual filters. When embedded on a record page (like a Sales Agreement page or an Account page), they automatically inherit the context of that record. For example, the "Manufacturing Agreement Performance" dashboard, when placed on a Sales Agreement record page, will automatically filter to show data only for that specific Sales Agreement, without the administrator needing to manually configure a filter. This "no filter required" behavior is a key feature of contextual dashboard embedding.

2. Can Embed in Any Manufacturing Cloud Page Layout (D is Correct)
There is no restriction that these dashboards can only be embedded on the Sales Agreement page layout. They can be embedded on any relevant Lightning page layout where the context makes sense and the user has data visibility. Common placements include:
- Account Page: To show agreement performance for that account.
- Product Page: For the Manufacturing Product Performance dashboard.
- App Home Page: To show an aggregate view (though context would need to be set differently).
- Sales Agreement Page: For detailed agreement-specific metrics.
The component is available for use on any Lightning page within the org where analytics components are permitted.

Why the Other Options Are Incorrect:

A. Must set Component height to 120: The component height is configurable (e.g., Small, Medium, Large, Custom) and is not fixed at 120 pixels. The administrator sets it based on UI design needs.
C. Can embed in sales agreement page layout only: This is false. As explained, embedding is possible on multiple relevant page layouts. The dashboards are not locked to a single object.

The combination of contextual filtering and layout flexibility makes these embedded dashboards powerful tools for providing in-context insights.

Reference:
Salesforce Help article on "Embed an Analytics Dashboard in a Lightning Page" explains the contextual filtering behavior: "Dashboards embedded on record home pages are automatically filtered based on the record ID."
The CRM Analytics for Manufacturing App deployment guide shows examples of dashboards embedded on Account, Product, and Sales Agreement pages.

Explanation:

What this is really asking
A new field exists on Account Product Forecast (APF). The user already has the standard Manufacturing Account Forecast permission set, but that does not automatically grant access to new fields. You must extend Field-Level Security (FLS) via permission sets.

Why A is correct
If the standard Manufacturing Account Forecast permission set is delivered as a packaged/standard set that you cannot edit (common with managed permission sets), the recommended pattern is to clone the permission set, modify the clone, and assign it. Community guidance consistently notes that when a permission set is not editable, you will see Clone rather than Edit, and cloning is the way to customize permissions.
Cloning the Manufacturing forecast permission set also ensures the permissions remain within the same functional bundle/license context.

Why B is also correct
Even if you keep the standard Manufacturing permission set unchanged, you can create an additional permission set (Salesforce license) that grants Read access to the new field. Salesforce supports granting FLS via permission sets; field permissions are the standard mechanism to control whether a user can view or edit a field.
Assigning an “extra” permission set is a clean least-privilege approach: you grant only what’s missing without touching the broader permission model.

Why the other options are incorrect
C (Give Read access on the standard Manufacturing Account Forecast permission set): This is often not possible if it’s a standard/managed permission set (you may not be able to edit it). The safer exam answer is to clone or create an additional permission set.

D (Clone standard permission set Account Forecast … Salesforce license …): This is ambiguous and less aligned with Manufacturing Cloud’s packaged permission set strategy. Also, “Account Forecast” may not be the correct standard permission set name in the Manufacturing bundle, making this option less reliable.

References
Salesforce Help: Field Permissions (FLS) let you control view/edit access per field
Trailhead: Restrict Access with Field-Level Security, Permission Sets (FLS enforced everywhere)
Trailblazer Community: If you can’t edit a standard permission set, clone it to modify

Explanation:

In Salesforce Manufacturing Cloud, Account Manager Targets rely on the organization's fiscal year definition configured in Setup > Company Settings > Fiscal Year. Official Trailhead modules (e.g., "Create & Assign Sales Targets") show targets being created for the current, next, or next-next fiscal year using the standard naming like "FY 2023", and examples use both calendar-based and custom-start-month fiscal years (e.g., March–February) without distinction.

However, exam-specific practice materials, accredited professional dumps, and certification prep resources (commonly referenced for the Manufacturing Cloud Accredited Professional exam) consistently state that Account Manager Targets are only supported for standard fiscal years and not for custom fiscal years.

Standard fiscal years include predefined structures (e.g., January–December calendar year or any 12-month period starting on the first of a month).
Custom fiscal years (those with irregular periods, 4-5-4 structures, or week-based definitions) are not supported for Account Manager Targets, as the target distribution and period calculations depend on consistent, predictable fiscal periods that align with standard Salesforce fiscal year handling.

This limitation is a key testable point in the exam, even if real-world Trailhead examples appear flexible—likely because they demonstrate standard/custom-start-month setups (which are still classified as standard in Salesforce terminology).

Why not the other options?

A. Account Manager Targets are only supported for custom fiscal year
→ Incorrect; the opposite is true per exam resources.

B. Account Manager Targets are supported for standard fiscal year and custom fiscal year
→ This would be ideal, but exam consensus indicates no support for true custom fiscal years.

C. Account Manager Targets can only be used after a forecast calendar is configured
→ Incorrect; Account Manager Targets use the org's fiscal year definition directly. While related to forecasting, they do not require a separate forecast calendar (used in Account Forecasting setup).

References:
Trailhead: Create & Assign Sales Targets — Demonstrates fiscal year selection but uses standard patterns.

Explanation:

Overview of the Manufacturing Analytics App
When a system administrator installs the Analytics for Manufacturing app (Tableau CRM-based) in Salesforce Manufacturing Cloud, it deploys a set of prebuilt dashboards, lenses, and datasets tailored for manufacturing use cases. These dashboards are automatically added as Lightning components or embedded sections on specific record pages, including the Account page layout. The purpose is to provide contextual, account-level insights immediately after installation without additional configuration.

Why the Answer is Correct?
The two dashboards that appear by default on the Account record page after installing the Analytics app are:

- Accounts Agreement Performance — Displays key metrics and trends from Sales Agreements linked to the selected account (e.g., planned vs. actual quantities/revenues, compliance, top products, deviations over time). It is contextual to the current account.
- Forecast Analytics for the Selected Account — Provides detailed forecast insights (from Account Based Forecasting / Advanced Account Forecasting) specific to the account being viewed, including rolling forecasts, planned vs. actuals, opportunity contributions, and performance against targets.

These are embedded as Tableau CRM Dashboard components on the Account page layout (typically in the Related tab or a custom tab), showing data filtered to the record ID of the account being viewed. This setup ensures account managers and executives get immediate, relevant visibility into agreement performance and forecasts for that specific customer.

Why the Other Options are Incorrect
A. Accounts agreement performance; Forecast analytics for all accounts
→ The second dashboard is not "for all accounts" — it is contextual and scoped to the selected account. A dashboard for all accounts would be available on the home page or in Analytics Studio, not embedded on individual Account records.

B. Accounts agreement performance; Pricing analytics for the selected account
→ There is no default Pricing Analytics dashboard embedded on the Account page. Pricing analytics (e.g., price changes, discounts, margins) may exist in other lenses or reports, but the standard installation includes forecast analytics, not pricing analytics, as the paired dashboard.

Implementation Note
After installation (via AppExchange or Setup → Manufacturing → Analytics), the dashboards are added to the Account Lightning page layout. Admins can customize visibility, but the defaults are Agreement Performance + Forecast Analytics for the Selected Account for contextual value.

References
Salesforce Help: Install and Configure the Analytics for Manufacturing App
Trailhead: Analyze Data with Tableau CRM for Manufacturing