Manufacturing data architecture generally spans multiple enterprise applications. Salesforce can contain and operationalize Accounts, Contacts, and Products, but the complete lifecycle of these entities frequently depends on ERP, Product Lifecycle Management, master-data systems, ecommerce platforms, and other enterprise applications.
Consequently, the consultant should not make a blanket assumption that either Salesforce or the ERP must exclusively own every data domain. Instead, the architecture should establish the appropriate source of truth and lifecycle responsibilities for individual data attributes and processes.
The Agentforce Manufacturing Professional exam guide specifically requires consultants to analyze data governance, system limitations, dependencies, and third-party systems during Discovery.
For example, Salesforce may maintain customer-facing account and contact information, while ERP systems consume those records for billing and fulfillment. Product commercial information may be available in Salesforce while engineering lifecycle information is governed by a PLM system. Synchronization rules must therefore reflect the codependent lifecycle rather than treating one platform as universally authoritative.
Option A is too restrictive because ERP is not inherently the master of every account, contact, and product field. Option B is equally rigid because manufacturing organizations commonly require these records to interact with operational enterprise platforms.
Study Guide references/topics: Discovery — Data Governance; Enterprise Systems; ERP; PLM; Master Data; Systems of Record; Integration Dependencies.
