AP-213 Salesforce Accredited Agentforce Manufacturing Professional Free Practice Exam Questions (2026 Updated)

Salesforce blocks Apex callouts to unapproved external network destinations. Before Apex can call an external URL directly, the endpoint must be registered as an authorized destination through Remote Site Settings, unless the implementation uses another approved endpoint mechanism such as a properly configured Named Credential.

Salesforce documentation explicitly states that before an Apex callout can access an external site, that site must be registered in Remote Site Settings or the call fails. Salesforce's current callout troubleshooting guidance also instructs administrators to verify that the endpoint is enabled as an active Remote Site when diagnosing external web-service failures.

A Connected App serves a different purpose. It defines how an external application integrates with Salesforce through protocols such as OAuth; it does not authorize Salesforce Apex code to make outbound requests to an arbitrary endpoint.

User permissions can affect access to Apex classes, credentials, or Salesforce data, but the specific Unauthorized endpoint exception indicates that Salesforce does not recognize the destination as permitted for the callout.

Therefore, registering the external endpoint URL in Remote Site Settings resolves the endpoint authorization requirement represented by this error.

Study Guide references/topics: Configure and Build — Third-Party Integration; Apex Callouts; Remote Site Settings; Endpoint Security.

A fundamental early configuration activity is to enable the required Manufacturing Cloud features in Setup. Individual capabilities such as Sales Agreements, Partner Visit Management, Service Console for Manufacturing, Warranty Lifecycle Management, Data Pipelines, and other Manufacturing features are controlled through feature settings and must be activated before their detailed configuration can proceed.

Feature enablement establishes the functional foundation of the Manufacturing Cloud implementation. Depending on which capabilities the business design requires, additional prerequisites may then be completed, including permission set licenses, permission sets, underlying objects, forecast settings, integrations, analytics, or industry-specific configuration.

Forecast regeneration settings are specific to forecasting and therefore occur after the relevant forecasting capability has been enabled. User permissions are also essential, but permission assignment alone does not activate the Manufacturing Cloud feature itself. In fact, Salesforce's setup documentation directs administrators to enable the necessary features and then configure the appropriate access model for users.

The implementation sequence should therefore begin by establishing which Manufacturing capabilities are required and activating those features in Setup before proceeding with detailed functional configuration.

Study Guide references/topics: Configure and Build — Manufacturing Cloud Setup; Feature Enablement; Prerequisites; Security and Permissions; Administrative Configuration.

Analytics for Manufacturing is modular. The administrator can configure the analytics application according to the Manufacturing Cloud features actually implemented by the organization rather than being forced to deploy every available analytical area.

Salesforce's Analytics for Manufacturing configuration workflow lets administrators add analytics for functional areas such as Sales Agreements, Account Forecasts, and Account Manager Targets independently. The app-creation wizard similarly allows the administrator to choose applicable forecast, sales-target, rebate, and other analytical datasets based on requirements.

This design is important because not every manufacturer uses every Manufacturing Cloud feature. An organization might initially deploy Sales Agreements and forecasting but postpone Account Manager Targets, or it might adopt targets before implementing rebate analytics.

Requiring all modules would unnecessarily increase data preparation, permissions, application complexity, and deployment dependencies. Conversely, preventing module selection would undermine the configurable nature of the template.

The administrator should therefore select the modules that correspond to the organization's implemented Manufacturing capabilities and business-analysis requirements.

Study Guide references/topics: Configure and Build — Analytics for Manufacturing; CRM Analytics Template; Analytics Modules; Sales Agreements; Account Forecasts; Account Manager Targets.

A global Manufacturing Cloud rollout must account for differences in the organization's existing technical landscape. Large manufacturers frequently operate multiple ERP instances, sometimes involving different ERP products, releases, data models, integration technologies, regional processes, and master-data structures.

The current Agentforce Manufacturing Professional exam guide explicitly requires consultants to analyze existing technical architecture, data governance, system limitations, and dependencies and to develop a comprehensive rollout strategy for multi-country deployments.

ERP variation is especially significant because Manufacturing Cloud implementations commonly depend on external systems for orders, products, inventory, invoicing, and other operational information. A rollout architecture that works with one country's ERP instance cannot automatically be assumed to work unchanged with another region's platform. Integration mappings, authentication, middleware, source-system ownership, process timing, and data-quality rules may all require regional analysis.

Localization, regulatory, and cultural factors are also relevant to global implementations, but among the listed choices, the varying ERP and integration landscape represents a direct Manufacturing Cloud architecture and dependency consideration emphasized by the exam's Discovery objectives.

Option C is incorrect because Manufacturing Cloud does not impose a universal requirement that global deployments must always be phased country by country.

Study Guide references/topics: Discovery — Global Rollout Strategy; Technical Architecture; Third-Party Systems; ERP Integration; Dependencies; Data Governance.

The scalable concern in this scenario is the volume of Sales Agreement updates required across a large multinational portfolio. Salesforce places defined processing limits on Mass Update operations in Sales Agreement Terms. Current Salesforce documentation states that a Mass Update can process a maximum of 100,000 filtered schedules across selected products, and the interactive selection supports up to 350 products or categories in applicable mass-update operations. A large combination of countries, customer tiers, products, currencies, and schedules can therefore require the updates to be broken into controlled subsets.

Option C does not accurately describe current Salesforce currency behavior. Static conversion rates can be edited in a multi-currency organization without enabling Advanced Currency Management. Advanced Currency Management is specifically required when the organization needs dated exchange rates rather than simply updating the current conversion rate.

Option B is also unsupported: Manufacturing Analytics provides account- and product-level pricing and performance analytics, and Advanced Account Forecasting is not inherently limited to 52 forecast updates annually.

The relevant architectural concern is therefore whether UC's large-scale annual repricing and product expansion can be handled within Sales Agreement bulk-processing limits.

Study Guide references/topics: Design — Scalability; Sales Agreement Limits; Mass Update; Multi-Currency; Global Manufacturing Architecture.

The administrator should first confirm that Sales Agreements is enabled in the production organization.

Manufacturing Cloud feature activation is environment-specific. A feature enabled in a development sandbox is not automatically enabled in another org simply because related metadata is deployed. Salesforce's deployment documentation also notes that some metadata components require the corresponding feature to be enabled in the target environment before those components can be deployed successfully.

Current Salesforce guidance for Sales Agreements confirms that the Sales Agreements foundation must be enabled through Manufacturing feature settings before users and metadata can fully access the Sales Agreement object and associated functionality.

Organization-wide defaults determine record-level sharing behavior after an object is available. Changing the OWD between Public Read/Write and Private does not create or activate the Sales Agreement object.

Therefore, when deployment reports that the object does not exist, the first diagnostic step is to verify that Sales Agreements functionality is enabled in the target production org.

Study Guide references/topics: Validate and Deploy — Deployment Prerequisites; Sales Agreements; Target Environment Configuration; Feature Enablement.

Effective end-user testing requires three fundamental components: an isolated test environment, representative test data, and structured test scripts describing the business processes and expected outcomes.

Salesforce explicitly recommends sandboxes for User Acceptance Testing because sandbox operations are isolated from production. Partial Copy sandboxes are designed for quality-assurance activities such as UAT and contain a selected sample of production data, while Full sandboxes are commonly used for final QA, UAT, staging, load, and production-like testing.

Test data is essential because users must validate actual Manufacturing Cloud scenarios—such as Sales Agreements, forecasts, orders, targets, and service operations—against realistic record relationships and values. Process scripts then ensure all testers execute agreed business scenarios consistently and document whether actual results match expected outcomes.

Profiles and user permissions are certainly part of establishing the testers' access, but they do not replace the need for representative data. Communication guidelines can support test management but are likewise not one of the core execution inputs.

Because these users must provide the deployment go/no-go decision, the testing must prove that defined business processes work correctly using representative information in a controlled non-production environment.

Study Guide references/topics: Validate and Deploy — User Acceptance Testing; Sandbox Strategy; Test Data; Test Scripts; Production Readiness.

The Service Console for Manufacturing is specifically designed to give manufacturing customer service representatives a consolidated view of customer, account, asset, warranty, claim, order, case, and engagement information. Rather than forcing an agent to navigate among multiple unrelated record pages, the console brings relevant manufacturing-service information together while preserving the context of the current customer interaction. Salesforce describes it as providing a holistic customer picture and allowing CSRs to manage the service lifecycle from a single interface.

For example, an agent can review order delivery information, asset status, service cases, upcoming engagements, and warranty-related information while working with the customer. Appropriate console components can be configured according to the organization's service processes.

A custom Case Lightning page would improve only the Case experience and would require administrators to reproduce functionality already available in the industry-specific console. The standard Service Console provides general Service Cloud capabilities but does not include the Manufacturing Cloud-specific service components and data context.

Therefore, enabling and configuring Service Console for Manufacturing is the appropriate implementation.

Study Guide references/topics: Configure and Build — Manufacturing Service; Service Console for Manufacturing; Manufacturing Service Experience; Service Agent Productivity.

For direct-order-based Sales Agreement actuals, Salesforce requires the Order to participate in the relationship and calculation criteria used by the automated process. The Order must be Activated, and in the direct-order model it references the applicable Sales Agreement. Salesforce then processes order products against matching products or primary product categories in the agreement.

The date criterion establishes which Sales Agreement schedule receives the Order's actual quantity and revenue. In the standard scenario represented by this question, the qualifying Order has reached its applicable date rather than representing an unqualified future transaction.

Current Salesforce functionality adds an important extension: administrators can configure a Sales Agreement to include a specified number of future schedules in actuals calculations. Salesforce currently permits up to 24 future schedules to be considered. Therefore, future-dated Orders can also participate when the Sales Agreement is explicitly configured for future schedules.

“Category = Activated” is not an Order eligibility criterion. Activation applies to the Order's Status, while product/category matching determines how its Order Products contribute to Sales Agreement schedules.

Study Guide references/topics: Configure and Build — Sales Agreement Actuals; Order Status; Direct Orders; Sales Agreement Relationships; Schedule Processing.

The Accounts Health dashboard is designed to provide an aggregated view of customer-account performance and relationship quality.

Salesforce specifically documents Length of Relationship, Future Length of Relationship, Total Length of Relationship, Customer Lifetime Value, and Average Customer Lifetime Value as KPIs available in the Accounts Health dashboard under the relationship analysis for accounts. Customer Lifetime Value represents revenue already generated together with anticipated future revenue, with anticipated revenue influenced by planned revenue and historical realization.

Revenue realization is another important account-health indicator. It measures actual revenue as a percentage of planned revenue and helps account managers understand whether customers are performing according to their commercial commitments.

The dashboard therefore allows users to evaluate both the financial value of an account and the strength and duration of the underlying commercial relationship. This helps identify strategic customers, accounts whose actual performance is falling behind planned commitments, and customers with significant future value.

Sales Agreement Insights operates primarily at the individual agreement level, while Account Insights provides detailed operational analysis. Whitespace Analysis is oriented toward new product, cross-sell, and upsell opportunities.

Study Guide references/topics: Configure and Build — Analytics for Manufacturing; Accounts Health; Customer Lifetime Value; Revenue Realization; Relationship Analytics.

The requirements map to three complementary Manufacturing capabilities. Account Manager Targets provides the hierarchical target-management framework. Managers can create revenue, quantity, or other targets, allocate portions to immediate team members, and subsequently distribute those assignments by account, product, and period.

Sales Agreements represent long-term or run-rate customer commitments and maintain planned and actual quantities and revenues across agreement schedules. Actual values can be derived from qualifying orders, providing the operational realization information needed when evaluating performance against planned business.

Advanced Account Forecasting addresses the multi-source rolling forecast requirement. Salesforce describes it as a comprehensive forecasting framework capable of using opportunities, orders, sales agreements, historical information, and additional business data, with configurable dimensions, measures, formulas, period groups, and DPE processing.

Together, these capabilities cover organizational target distribution, long-term agreement realization, and extensible multi-source forecasting.

Each feature addresses a different layer of the requirement, so substituting one for another would leave a gap in target management, agreement realization, or rolling forecast generation.

Study Guide references/topics: Design — Mapping Business Requirements; Account Manager Targets; Sales Agreements; Advanced Account Forecasting.

Order Forecasting for Manufacturing provides substantially more than a single predicted quantity or revenue value. The statistical forecasting capability is intended to help planners understand both the expected demand and the uncertainty surrounding that expectation.

Salesforce describes Statistical Order Forecasting as producing predicted order quantity and order revenue values and supporting analysis of forecast accuracy. Salesforce also documents that the statistical forecast output includes a 95% confidence level, enabling planners to understand the likely range around the forecast rather than treating the prediction as an absolute point estimate.

The associated dashboard allows users to review forecast values, analyze trends, evaluate forecast distribution according to dimensions, and measure the accuracy of the predictions. This is particularly valuable for manufacturing planning because uncertainty ranges help operations teams assess safety stock, capacity, and supply requirements.

The functionality is not inherently restricted to a single specified period or exactly three months. Forecast horizons are determined through the forecasting configuration, including period groups and forecast sets.

Therefore, the relevant insights consist of the forecasted value, forecast range or confidence interval, and forecast accuracy.

Study Guide references/topics: Configure and Build — Statistical Order Forecasting; CRM Analytics; Forecast Confidence; Forecast Accuracy; Demand Planning.

The validation must confirm not only that records were migrated, but also that the forecast calculations derived from those records produce the expected business results. Therefore, the administrator should run the Advanced Account Forecast calculations and reconcile the calculated results against the corresponding values from the legacy system.

Advanced Account Forecasting uses DPE definitions and forecast formulas to calculate measures from source information such as Orders, Opportunities, Sales Agreements, and other configured records. Salesforce provides DPE templates specifically for generating, recalculating, regenerating, and rolling over forecast data.

Running those calculations after migration validates several layers simultaneously: migrated source data, forecast-set configuration, dimensional mappings, measure calculations, DPE transformation logic, and resulting Forecast Fact values. A comparison with the legacy platform then provides an objective reconciliation point.

A CSV comparison verifies record movement but cannot prove that Manufacturing Cloud's calculated forecast results are correct. Asking end users to spot-check accounts provides useful UAT feedback but is not sufficient as the primary technical reconciliation mechanism.

The administrator should therefore execute the calculation process and compare equivalent forecast outputs between Manufacturing Cloud and the legacy implementation.

Study Guide references/topics: Validate and Deploy — Data Migration Validation; Advanced Account Forecasting; DPE Calculations; Reconciliation; Forecast Verification.

An administrator who creates and manages Analytics for Manufacturing requires both the general CRM Analytics administration permissions and the Manufacturing-specific analytics administration permissions.

Salesforce currently identifies these as CRM Analytics Plus Admin and Manufacturing Analytics Admin. The product terminology has evolved from Tableau CRM to CRM Analytics, so the Tableau CRM Plus Admin wording in the question corresponds to the analytics administrator permission represented by option B.

The CRM Analytics administration permission supplies the base capabilities required to work with CRM Analytics applications, assets, datasets, and administration. Manufacturing Analytics Admin adds the Manufacturing Cloud-specific access required to create and manage the Analytics for Manufacturing application and its predefined manufacturing analytics assets.

Salesforce separately provides user-level permissions—such as CRM Analytics Plus User and Manufacturing Analytics User—for users who only consume or interact with the dashboards. Those user permissions are not sufficient for an administrator responsible for setting up the application.

Therefore, an administrator implementing the Manufacturing analytics application must be assigned both the general analytics administration permission and the Manufacturing-specific analytics administration permission.

Study Guide references/topics: Configure and Build — Analytics for Manufacturing; CRM Analytics; Manufacturing Analytics Admin; Analytics Permissions.

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.

Sales Agreement custom metrics are implemented through corresponding fields on the Sales Agreement Product and Sales Agreement Product Schedule objects. Salesforce specifies that custom metric fields used in this mapping must use supported quantitative data types. For Sales Agreement Product Schedule, the supported custom field types available for mapping are Number, Currency, and Formula.

The administrator first creates the required field on both objects and then configures the field mapping from Sales Agreement Product to Sales Agreement Product Schedule in Manufacturing setup. If aggregation is required, a Roll-Up Summary field can also be used on Sales Agreement Product to summarize the corresponding Number or Currency values from schedule records. Once mapped, the metric can be added to a metric group so that account managers can work with it directly in the Agreement Terms table.

Percent and “value” are not the supported mapping types identified by Salesforce for this configuration. Formula fields are supported, which is important when the metric must be derived rather than directly entered.

Study Guide references/topics: Configure and Build — Sales Agreements; Custom Metrics; Agreement Terms; Sales Agreement Product and Product Schedule field mappings.

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.

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.

Account Manager Targets support both financial and non-financial performance measures. Salesforce configures these measures through the Measure field on the Account Manager Target object. The predefined Revenue measure is available by default, and administrators can create additional custom measures such as Customer Satisfaction (CSAT), Net Promoter Score, product quantity, or other organization-specific targets.

For CSAT, the administrator navigates to the Account Manager Target object's fields, opens the Measure picklist, and creates a new value with the label CSAT. Salesforce then requires the appropriate Measure Type. Because CSAT is a non-currency measurement, the administrator selects Other, which Salesforce uses for non-currency target measures. Currency is reserved for monetary targets such as revenue or total order amount.

This makes option B technically precise: both the field and object are correct, and the non-currency classification is appropriate.

The Account Manager object itself does not define target measures, and there is no separate CSAT Measure Type required. Once configured, CSAT becomes available when users create Account Manager Target records.

Study Guide references/topics: Configure and Build — Account Manager Targets; Custom Measures; Measure Picklist; Currency and Non-Currency Targets.